Search / io.github.tiptreesystems/lacuna-research-mcp
protogridR0· no sign-inSearch Lacuna's ML research graph for papers, directions, authors, venues, and hypotheses.
v0.6.5 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"lacuna-research-mcp": {
"type": "http",
"url": "https://lacuna.tiptreesystems.com/api/mcp"
}
}
}claude mcp add --transport http lacuna-research-mcp https://lacuna.tiptreesystems.com/api/mcp[mcp_servers.lacuna-research-mcp]
url = "https://lacuna.tiptreesystems.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lacuna-research-mcp": {
"type": "remote",
"url": "https://lacuna.tiptreesystems.com/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"lacuna-research-mcp": {
"type": "http",
"url": "https://lacuna.tiptreesystems.com/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=lacuna-research-mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbGFjdW5hLnRpcHRyZWVzeXN0ZW1zLmNvbS9hcGkvbWNwIn0%3D"
}{
"servers": {
"lacuna-research-mcp": {
"type": "http",
"url": "https://lacuna.tiptreesystems.com/api/mcp"
}
}
}{
"mcpServers": {
"lacuna-research-mcp": {
"httpUrl": "https://lacuna.tiptreesystems.com/api/mcp"
}
}
}extensions:
"lacuna-research-mcp":
enabled: true
name: "lacuna-research-mcp"
type: streamable_http
uri: "https://lacuna.tiptreesystems.com/api/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length2 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations13 of 13 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 3,940 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes13 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulnsno known advisory in 32 resolved packagesdeps.mcp_sdk_versionmcp 2.3.0, no known advisorydeps.resolvable[email protected] resolved: 32 packagesget_institution_authorschangedannotationsget_institution_contextchangedannotationsget_venue_contextchangedannotationsget_author_neighborschangedannotationsget_author_contextchangedannotationsget_author_directionschangedannotationsget_author_paperschangedannotationsget_resourcechangedannotationsget_paperchangedannotationsget_direction_paperschangedannotationsShowing the latest 10. Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-97% +updated-3d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
[email protected] PyPI31 dependencies, resolved · MCP SDK mcp 2.3.0 · advisories checked 2026-10-19
No known advisory affects this dependency graph.
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://lacuna.tiptreesystems.com/api/mcp streamable-http | none | yes | 97% | 255 ms | 2026-07-28 | 2026-10-20 |
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
lacuna-research-mcp | pypi | 0.6.5 | – |
get_author_contextread-only | Fetch agent-oriented context for a Lacuna author. Author profiles describe research output (papers, directions, impact). A free-text `affiliation` field may be present but can be incomplete or outdated and may not represent current employment; the corpus has no biography or employment history, so do not infer those from this data. view selects the response shape: - "context" (default, recommended): Lacuna's compact author context — capped readable papers and an `impact_directions` list (named research directions) in place of the raw numeric `impact_clusters` telemetry, with the duplicated nested author record dropped server-side. - "full": the bounded full-shape author context (raw `impact_clusters`, nested author record; server collections are capped at 100). Set include_neighbors=True to include similar authors as named, linkable records. Neighbor computation may add significant server latency. |
get_author_directionsread-only | Fetch one page of an author's named research directions. |
get_author_neighborsread-only | Fetch one ranked page of neighboring/similar Lacuna authors. |
get_author_papersread-only | Fetch one page of an author's papers, ordered from newest to oldest. |
get_directionread-only | Fetch a Lacuna research direction/cluster. Use a numeric cluster ID (for example 25005) or a direction URL ending in that number. view selects the response shape (`context` typically contains the fields `full` provides plus the agent-oriented summary content): - "context" (default, recommended): compact agent-oriented summary with summary_markdown, capped papers/authors/related_directions, and truncation markers. - "full": raw upstream cluster record only. Cheaper than context when you only need basic cluster metadata. |
get_direction_papersread-only | Fetch paginated papers associated with a Lacuna research direction/cluster. view selects the per-paper shape: - "compact" (default, recommended): citation-ready rows (id, url, title, year, venue, a few authors, abstract snippet). Drops the raw upstream info blob and levels.cluster internals that otherwise dominate the payload. - "full": the complete upstream paper records. Much larger; use only when you need the raw metadata (openalex/dblp/arxiv ids, etc.). |
get_hypothesisread-only | Fetch a generated novel ML/AI research proposal from Lacuna. Use after search_lacuna(search_type="hypothesis") to inspect a proposal. view selects the response shape: - "context" (default, recommended): compact single-fetch proposal context — summary_markdown, abstract, and linked directions, with the raw upstream record (whose markdown duplicates summary_markdown) dropped server-side. - "full": the server's version record, including version history and signal counts. Proposal bodies are in versions[].markdown. Use only when you need versions or signals. |
get_institution_authorsread-only | Fetch one page of authors affiliated with a Lacuna institution. Results are ordered by paper count. Use authors_total, authors_returned, authors_offset, and authors_truncated to page through the complete list. |
get_institution_contextread-only | Fetch agent-oriented context for a Lacuna institution. view selects the response shape: - "context" (default, recommended): compact institution context — capped top authors with the duplicated institution block dropped server-side. - "full": the complete institution context shape (duplicated institution record and a bounded author list with explicit truncation metadata). Use get_institution_authors to page through the complete author list. |
get_paperread-only | Fetch a Lacuna paper by artifact id or paper URL. include_resources adds linked resources (code repositories, datasets, models, and demos) in context and full views by default. Pass False to omit them; other views ignore this option. Pass a resource entry's id to get_resource for further details. view selects the response shape. `context` requests Lacuna's compact agent-oriented context by default, while the four single-field views (blog/figures/concepts/neighbors) return isolated sub-resources: - "context" (default, recommended): agent-oriented summary with summary_markdown, authors, and a small figure preview. Start here for almost everything. Available versions are included when present; to read another version, use its artifact ID from the returned version list. - "full": raw upstream paper record. Cheaper than context when you only need basic metadata. - "preview": compact card with unique fields `excerpt`, `excerpt_kind`, `bookmarked`. Use for citation-style display. - "blog": just the summary_markdown content, without the rest of the context envelope. - "figures": just the figures list. - "concepts": just the concepts list. - "neighbors": just the related-papers list. figure_limit (context view only) caps the figure preview (server default 3). Pass 0 to suppress figure previews while keeping a `figures_truncated` signal. |
get_resourceread-only | Fetch a Lacuna research resource (code repository, dataset, model, or demo). Accepts a resource artifact ID (art_...) or a Lacuna resource URL containing that ID (/resource/<slug>/art_...). The response includes the external url, a summary, facets (tasks, modalities, size, license, access), provider metrics, a README/card excerpt, `publications` (linked papers with paper_id, title, venue, year, and relationship such as dataset_for or code_for), related research directions, and other resources mentioned by this one. Pass a publication's paper_id to get_paper to read the paper and its reported results. |
get_venue_contextread-only | Fetch agent-oriented context for a Lacuna venue, optionally scoped to a year. Venue keys are opaque hashes (e.g. "d7bf22905bd6"), never human-readable names like "icml". Find the key first via search_lacuna(search_type="venue") or pass a /venue/... page URL. view selects the response shape: - "context" (default, recommended): compact venue context — capped top authors, non-placeholder top clusters, and a recent-activity slice (the requested `year` is always included), with the duplicated venue block and full year histogram dropped server-side. - "full": the complete venue context (full year histogram, all top authors/ clusters, duplicated venue record). |
search_lacunaread-only | Search Lacuna's ML/AI corpus for papers, research directions, authors, venues, institutions, novel research hypotheses, and research resources (code repositories, datasets, models, and demos linked to papers). For novel ML/AI research ideas, use search_type="hypothesis", then get_hypothesis on promising results. search_type accepts all, cluster, paper, author, institution, venue, hypothesis, or resource. Use paper for literature and get_paper to read a result. Use other sources for biographies, news, and non-research web content. Resources: search_type="resource" searches GitHub repositories, Hugging Face datasets/models, and Zenodo records that Lacuna has linked to at least one paper. To find benchmark or evaluation datasets, use search_type="resource" with resource_kind="dataset" (for example query "image classification benchmark" or a dataset name like "ImageNet"). resource_kind accepts codebase, dataset, model, or demo (one value or a list); provider accepts github, huggingface, or zenodo. Both filters require search_type "resource" or "all" (with either filter set, only resources are returned). Each result has an external `url`, a Lacuna `context_url`, and `linked_paper_count`; call get_resource on its id to list the linked papers (with their relationship to the resource), then get_paper on those papers for reported results and numbers. Resource search does not support date_from/date_to, venue, year sorting, or semantic ranking. ranking_profile accepts: - default / lexical (default): production ranking; relevance-sorted paper searches combine lexical and semantic retrieval when fields is unset. - semantic: conceptual paper retrieval; supported for paper and all. - bm25_title_abstract / bm25: lexical paper matching over those fields. sort accepts relevance (default), year_desc, or year_asc. Semantic ranking cannot use year sorting; constrain recency with date_from/date_to instead. date_from and date_to are inclusive YYYY, YYYY-MM, or YYYY-MM-DD bounds. author_id_or_url constrains a paper search to one author. Pass an author ID or Lacuna author page URL; it requires search_type="paper". fields optionally restricts and weights lexical fields, for example "title^4,abstract". Supported names are title, abstract, summary, concepts, name, top_names, and venue, plus description, topics, provider_key, and paper_titles for resources (a resource's title already includes its description, topics, README text, and linked paper titles). Fields must exist on the selected search_type, weights must be within 0 < weight <= 100, and fields cannot be combined with semantic ranking. |
Schemas: list_tools.
{
"name": "io.github.tiptreesystems/lacuna-research-mcp",
"title": "Lacuna Research MCP",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://lacuna.tiptreesystems.com/api/mcp",
"type": "streamable-http"
}
],
"version": "0.6.5",
"packages": [
{
"version": "0.6.5",
"transport": {
"type": "stdio"
},
"identifier": "lacuna-research-mcp",
"registryType": "pypi"
}
],
"repository": {
"id": "1306004280",
"url": "https://github.com/tiptreesystems/lacuna-research-mcp",
"source": "github"
},
"websiteUrl": "https://lacuna.tiptreesystems.com",
"description": "Search Lacuna's ML research graph for papers, directions, authors, venues, and hypotheses."
}