Skip to main content
Glama

Lacuna Research MCP

Lacuna, built by Tiptree Systems, is a research map of machine learning: a heterogeneous knowledge graph linking papers, research directions, authors, venues, institutions, and generated research proposals, with a source trail from every derived object back to the exact paper and page that produced it.

Lacuna Research MCP gives AI researchers' coding agents:

  • Generated research proposals. Explore research ideas generated with The Alien Space of Science.

  • Research directions. Navigate concept clusters with linked papers, authors, and proposals.

  • Agent-ready literature. Search recent papers in markdown with source links.

  • Researcher intelligence. Trace authors, publications, directions, impact, and related researchers.

  • Landscape mapping. Compare venues, institutions, leading researchers, and publication activity.

For example, trace an implementation to its recorded paper relationships:

Find the paper behind Dao-AILab/flash-attention. Show the recorded connection to the repository and link the original paper.

This example follows repository → recorded paper relationship → paper and sources. Lacuna returns the official_code_for relationship to FlashAttention, with links to the repository and original paper. Inspect those sources to verify the connection. Run the example or work through the notebook.

Install · Research skills · First use · Tools · API reference · Configuration

Install

Agent plugin for Cursor

This repository also packages the hosted MCP connection and the two research skills as an Agent Plugin. Cursor supports this format.

To test it locally, copy this repository to ~/.cursor/plugins/local/lacuna-research-mcp, reload Cursor, and open Customize to check the two skills and the MCP connection. The plugin connects to https://lacuna.tiptreesystems.com/api/mcp; no local Python installation or Lacuna account is required. Enable either this connection or a manually configured Lacuna server to avoid duplicate tools.

Cursor and VS Code

Use the hosted server with no local Python installation or Lacuna account:

Add to Cursor Add to VS Code

The buttons open your editor's MCP installation flow. Review the server URL and confirm installation. After connecting, ask the FlashAttention question above; your agent should use search_lacuna, get_resource, and get_paper.

In Cursor, merge this entry into mcpServers in .cursor/mcp.json:

{
  "mcpServers": {
    "lacuna-research": {"url": "https://lacuna.tiptreesystems.com/api/mcp"}
  }
}

In VS Code, merge this entry into servers in .vscode/mcp.json:

{
  "servers": {
    "lacuna-research": {"type": "http", "url": "https://lacuna.tiptreesystems.com/api/mcp"}
  }
}

Keep any existing server entries. Open your editor's MCP settings to verify the connection and enable Lacuna's tools for the conversation.

Hosted MCP server (Claude connector)

Use Lacuna's hosted MCP server with any client that supports Streamable HTTP. No local installation is required.

https://lacuna.tiptreesystems.com/api/mcp

In Claude, open Customize → Connectors → + Add → Add custom connector. Name it Lacuna Research, paste the URL above, and select No sign in if prompted for authentication. Finish adding it, then enable it from + → Connectors in your conversation.

For Team and Enterprise workspaces, the connector must first be added under Organization settings → Connectors. See Claude's custom connector setup for details.

Local installation

The easiest way to install Lacuna Research MCP is to ask your coding agent, such as Codex or Claude Code:

Install and configure the lacuna-research-mcp package from PyPI for this client.

For manual setup, the instructions below use uvx to run the latest tagged release from PyPI. Install uv first; Lacuna Research MCP requires Python 3.11 or newer.

Codex

Add the server with the Codex CLI:

codex mcp add lacuna-research -- uvx lacuna-research-mcp

Alternatively, add the following to ~/.codex/config.toml (or to .codex/config.toml in a trusted project for project-only setup):

[mcp_servers.lacuna-research]
command = "uvx"
args = ["lacuna-research-mcp"]

Run codex mcp list to verify the server is configured. The Codex app, CLI, and IDE extension share this configuration on the same machine.

Claude Code

Add the server for all of your projects with the Claude Code CLI:

claude mcp add --scope user lacuna-research -- uvx lacuna-research-mcp

Omit --scope user to add it only to the current project. Alternatively, add the following under the top-level mcpServers object in ~/.claude.json:

{
  "mcpServers": {
    "lacuna-research": {
      "type": "stdio",
      "command": "uvx",
      "args": ["lacuna-research-mcp"]
    }
  }
}

Run claude mcp get lacuna-research to verify the server is configured.

Claude Desktop

Open Settings → Developer → Edit Config, then add the server under mcpServers in claude_desktop_config.json:

{
  "mcpServers": {
    "lacuna-research": {
      "command": "uvx",
      "args": ["lacuna-research-mcp"]
    }
  }
}

Restart Claude Desktop after saving the file.

Other MCP clients

For any client that supports local stdio MCP servers, use this standard configuration:

{
  "mcpServers": {
    "lacuna-research": {
      "command": "uvx",
      "args": ["lacuna-research-mcp"]
    }
  }
}

Standalone command

Install the MCP server as a persistent command:

uv tool install lacuna-research-mcp
lacuna-research-mcp

Run it without installing a persistent command:

uvx lacuna-research-mcp

If this exits with a prerelease error (for example, "Python 3.14.0rc2 is a prerelease..."), your uv is using an early Python 3.14 prerelease that the MCP SDK does not support. Update uv (uv self update), install a released Python (uv python install 3.14), or run uvx --python 3.13 lacuna-research-mcp.

Self-hosted HTTP server

To serve remote MCP clients over Streamable HTTP instead of stdio:

uvx lacuna-research-mcp --transport streamable-http --host 0.0.0.0 --port 8000

The endpoint is /mcp. The server is stateless and answers with JSON, so it can run behind a load balancer without session affinity. With the default --host 127.0.0.1, the server accepts only localhost Host headers, so bind a non-loopback address when a reverse proxy forwards a public hostname.

Latest development version

PyPI contains tagged releases. To try the latest code from the main branch instead:

uvx --from git+https://github.com/tiptreesystems/lacuna-research-mcp.git lacuna-research-mcp

Local development

With uv:

git clone https://github.com/tiptreesystems/lacuna-research-mcp.git
cd lacuna-research-mcp
uv sync --extra dev
uv run lacuna-research-mcp

With pip:

cd <path-to-lacuna-research-mcp>
python3 -m venv .venv
. .venv/bin/activate
python -m pip install -U pip
python -m pip install -e .

Related MCP server: scholar-memory

Research skills

The MCP server provides tools. These optional skills teach your agent how to use them for two research tasks:

Skill

Example request

Check prior work

Before I implement token merging for a vision transformer, find the closest work and a baseline to include.

Trace code to papers

Which paper does Dao-AILab/flash-attention implement? Show the recorded relationship and sources.

Connect the MCP server first. Then, with Node.js 22.20+ installed, run the skills CLI from your project:

npx skills add tiptreesystems/lacuna-research-mcp

Choose the skills and agent you use. To install only the code-to-paper workflow:

npx skills add tiptreesystems/lacuna-research-mcp --skill lacuna-code-to-paper

Skills install to the current project by default. They don't install or configure the MCP server. Start a new agent session after installation if your client needs one to discover new skills.

First use

Ask one of the questions above in your connected agent, or try a reading-list question:

My list has FlashAttention and FlashAttention-2. What baselines or limitations should I read about for long-context attention?

For a reproducible example with no model API key, clone this repository and run:

uv run examples/code_to_paper.py

The notebook explains each step and compares the source trail with a single paper search. For direct tool use, the same flow is:

  1. search_lacuna(query="FlashAttention", search_type="resource", resource_kind="codebase", limit=5)

  2. Check the repository identity, then pass its returned ID to get_resource(resource_id_or_url=...).

  3. Follow a returned publications[].paper_id with get_paper(artifact_id_or_url=..., view="context", figure_limit=0).

For literature search, use search_lacuna(query="methods for detecting prompt injection attacks", search_type="paper", limit=5). For generated proposals, use search_lacuna(query="LLM jailbreak defense", search_type="hypothesis", limit=5) and follow a returned ID with get_hypothesis. Generated proposals are ideas to investigate, not evidence of published findings.

About Lacuna

Lacuna's pipeline reconciles scholarly records from OpenAlex, OpenReview, DBLP, and arXiv; extracts concept elements from paper text and clusters them into research directions (Lacuna paper); and samples novel research proposals from those directions with The Alien Space of Science. The map spans more than 2.29 million papers, 215,000+ author profiles, 28,000+ research directions, 25,000+ research proposals, and 5,300+ venues — and it grows continuously as new arXiv and other AI papers are ingested.

Scope

The corpus covers machine learning and AI research: papers, research directions, authors' research output, venues, institutions, generated research hypotheses, and research resources (GitHub repositories, Hugging Face datasets and models, Zenodo records) linked to papers. It does not contain biographies, news, or non-research web content. Agents should answer questions outside that scope from other sources.

What it exposes

  • search_lacuna Uses Lacuna's public /api/v1/search endpoint for directions, papers, authors, venues, institutions, hypotheses, and resources. Explicit paper searches (search_type="paper") use the server's production lexical+semantic ranker when the other ranking arguments remain at their defaults. Pass search_type="hypothesis" for hypothesis search. Pass search_type="resource" for code repositories, datasets, models, and demos linked to papers, optionally filtered with resource_kind (codebase, dataset, model, demo) and provider (github, huggingface, zenodo); for example, resource_kind="dataset" finds benchmark datasets. Resource search rejects date_from/date_to, venue, year sorts, and semantic ranking (resources carry no dates, venues, or embeddings).

  • get_hypothesis(hypothesis_id_or_url, view="context") Hypothesis/proposal. view="context" (default) is a compact single-fetch proposal context (summary, abstract, linked directions); view="full" returns the server's version record with version history and signal counts. Proposal bodies are in versions[].markdown.

  • get_direction(cluster_id_or_url, view="context") Research direction/cluster. view="context" (default) requests the compact agent-oriented summary; view="full" returns the raw cluster record.

  • get_direction_papers(cluster_id_or_url, page, limit, view="compact") Paginated papers attached to a direction. view="compact" (default) returns citation-ready rows (id, url, title, year, venue, a few authors, abstract snippet); view="full" returns the raw upstream paper records.

  • get_paper(artifact_id_or_url, view="context", figure_limit=None, include_resources=True, offset=0, max_chars=None) Paper lookup with available versions; use a version’s artifact ID to read it. Linked resources (code repositories, datasets, models, and demos) are included by default in context and full views; pass include_resources=False to omit them. Other views ignore this option. view="context" (default) requests the compact agent-oriented context; other views are "full", "preview", "blog", "figures", "concepts", "neighbors", or "fulltext" (arXiv LaTeX source where Lacuna has it, otherwise text extracted from the PDF; paged with max_chars and offset). In context view, figure_limit caps the figure preview (server default 3; pass 0 to suppress previews while keeping a figures_truncated signal).

  • get_resource(resource_id_or_url) Resource lookup by id (from resource search or get_paper's resources list) or Lacuna /resource/... URL: external URL, summary, facets (tasks, modalities, size, license), provider metrics, README/card excerpt, linked papers under publications (with paper_id and relationship such as dataset_for), related directions, and mentioned resources.

  • Author tools: get_author_context(…, view="context"), get_author_papers, get_author_directions, and get_author_neighbors. Start with get_author_context, which defaults to the compact agent-oriented view (capped papers plus a readable impact_directions list instead of raw impact_clusters telemetry). Use the dedicated papers, directions, and neighbors tools to page through those collections without repeating the author context. view="full" returns the server-bounded full-shape context (collections remain capped at 100). Pass include_neighbors=true to explicitly include similar authors; this may add significant server latency.

  • Venue and institution tools: get_venue_context(…, view="context"), get_institution_context(…, view="context"), get_institution_authors. Context tools default to compact (capped lists, duplicated blocks dropped; venue keeps a recent-activity slice that always includes the requested year). Use get_institution_authors to page through an institution's complete author list.

Wrapped APIs

MCP tool

Lacuna API endpoint

search_lacuna(query, search_type, limit, offset, author_id_or_url, date_from, date_to, venue, sort, ranking_profile, fields, resource_kind, provider)

GET /api/v1/search (resource_kind and provider are sent as repeated kind and provider query params and require search_type="resource" or "all". author_id_or_url constrains search_type="paper" to one author, accepting a raw author ID or Lacuna author page URL. fields restricts/weights the text fields used for lexical ranking, e.g. title^4,abstract, and selects the experimental lexical ranker; for a default relevance-sorted paper search, this bypasses the production lexical+semantic ranker. Allowed fields are title, abstract, summary, concepts, name, top_names, venue, description, topics, provider_key, paper_titles, each valid only for the types that carry it — title: paper/cluster/venue/hypothesis/resource; description/topics/provider_key/paper_titles: resource; abstract/summary/concepts: paper; name: author/institution/venue; top_names: cluster/hypothesis; venue: paper/venue (search_type="all" spans all). Weights must satisfy 0 < weight <= 100. Unknown fields, out-of-range weights, type-incompatible fields, and fields combined with ranking_profile="semantic" are rejected, since the server would otherwise silently drop, cap, or ignore them.)

get_hypothesis(hypothesis_id_or_url, view="context")

view="context" → GET /api/v1/context/hypothesis/{hypothesis_id}?view=compact; view="full" → GET /api/v1/hypotheses/{hypothesis_id}

get_direction(cluster_id_or_url, view="context")

view="context" → GET /api/v1/context/direction/{cluster_id}?view=compact; view="full" → GET /api/v1/clusters/{cluster_id}

get_direction_papers(cluster_id_or_url, page, limit, view="compact")

GET /api/v1/clusters/{cluster_id}/papers?view=compact (default) or ?view=complete

get_paper(artifact_id_or_url, view="context", figure_limit=None, include_resources=True, offset=0, max_chars=None)

view="context" → GET /api/v1/context/paper/{artifact_id}?view=compact (&figure_limit=N when set); view="full" → GET /api/v1/papers/{artifact_id}; view="preview" → …/preview; view="blog" → …/blog; view="figures" → …/figures; view="concepts" → …/concepts; view="neighbors" → …/neighbors; view="fulltext" → …/fulltext?offset=&max_chars=; context and full send include_resources. A Work page URL (/work/<name>, /work/<slug>/wrk_…) or bare wrk_… id is read through GET /api/v1/context/work/{work_id_or_name} first

get_resource(resource_id_or_url)

GET /api/v1/resources/{resource_id}

get_author_papers(author_id_or_url, limit=50, offset=0)

GET /api/v1/authors/{author_id}/papers

get_author_directions(author_id_or_url, limit=50, offset=0)

GET /api/v1/authors/{author_id}/directions

get_author_context(author_id_or_url, view="context", include_neighbors=false)

view="context" → GET /api/v1/context/author/{author_id}?view=compact; view="full" → GET /api/v1/context/author/{author_id} (include_neighbors=true explicitly requests similar authors)

get_author_neighbors(author_id_or_url, limit=8, offset=0)

GET /api/v1/authors/{author_id}/neighbors

get_venue_context(venue_key_or_url, year, view="context")

view="context" → GET /api/v1/context/venue/{vkey}[/{year}]?view=compact; view="full" → same route without view

get_institution_context(institution_key_or_url, view="context")

view="context" → GET /api/v1/context/institution/{ikey}?view=compact; view="full" → same route without view

get_institution_authors(institution_key_or_url, limit=50, offset=0)

GET /api/v1/institutions/{ikey}/authors

For id-or-URL arguments, pass either the raw id returned by search_lacuna or the corresponding Lacuna page URL. The MCP normalizes Lacuna-relative url and *_url fields to absolute URLs, and it also absolutifies Lacuna links (including /resource/... pages) inside fields named summary_markdown, article_markdown, markdown, content, or description.

get_author_context is bounded server-side in both views. The default compact view returns a curated briefing; view="full" returns the larger complete shape with embedded collections capped at 100. Use get_author_papers and get_author_directions rather than trying to page embedded context collections.

Search requests are capped at 50 results per call, and direction-paper page requests are capped at 100 results per call. In search_lacuna, date_from and date_to are inclusive publication-date bounds. Accepted formats are YYYY, YYYY-MM, and YYYY-MM-DD; for example, date_from="2020", date_to="2022-03" includes papers from January 1, 2020 through March 31, 2022.

search_lacuna exposes these ranking profiles:

  • default / lexical The default profile for all searches. With search_type="paper", sort="relevance", and fields unset, it uses the server's production lexical+semantic ranker with graceful fallback. The MCP's default search_type="all" uses the server's default lexical ranking instead.

  • semantic Use for embedding-based paper retrieval. The semantic query omits the normal lexical ranking leg, but the server can still overlay exact-title lexical matches. Only supported for paper and all searches (only papers have semantic embeddings), and not with resource_kind/provider filters.

  • bm25_title_abstract / bm25 Use for lexical matching constrained to title and abstract. Rejected for author and institution searches (those records have no title or abstract fields).

All searches use the server default unless ranking_profile is provided. The MCP rejects unsupported profile/type combinations because the server would otherwise fall back to substring search and silently ignore the requested ranking profile.

sort accepts relevance (default), year_desc, and year_asc. Year sorts cannot be combined with ranking_profile="semantic" — the server would silently ignore the sort — so the MCP rejects that combination; for recent-and-relevant queries, keep semantic ranking and constrain recency with date_from/date_to instead.

Environment variables

  • LACUNA_SITE_URL Defaults to https://lacuna.tiptreesystems.com

  • LACUNA_MCP_TIMEOUT Defaults to 30

  • LACUNA_MCP_MAX_RETRIES Defaults to 2; applies to timeouts, transport errors, and HTTP 429, 502, 503, and 504 responses.

  • LACUNA_MCP_USER_AGENT Defaults to lacuna-research-mcp/{package_version}

  • LACUNA_MCP_BEARER_TOKEN Optional bearer token sent as Authorization: Bearer ... for private Lacuna deployments.

  • LACUNA_MCP_CLIENT_TOKEN Optional token sent as X-Lacuna-Client-Token to identify a hosted MCP server to Lacuna for its own search rate limit.

  • LACUNA_MCP_LOG_LEVEL Defaults to WARNING (one of DEBUG, INFO, WARNING, ERROR, CRITICAL). The default keeps normal operation quiet; lower it only for debugging, since INFO/DEBUG let the HTTP client log full request URLs — including the search query string — to stderr, which some MCP hosts retain.

Environment variables are read once when the MCP server is created, or on the first direct tool/API call if the module is imported without calling create_mcp().

Implementation layout

The server is a thin MCP adapter over Lacuna's HTTP API. The implementation is split by responsibility:

  • lacuna_research_mcp/server.py MCPServer app creation, tool registration, lifespan cleanup, and the lacuna-research-mcp CLI entrypoint.

  • lacuna_research_mcp/tools.py MCP tool functions. Each tool normalizes its inputs, calls the matching Lacuna API endpoint through the shared client helpers, and returns JSON-compatible data.

  • lacuna_research_mcp/client.py Runtime HTTP access to Lacuna: the event-loop-bound httpx.AsyncClient, retry handling, error wrapping, JSON parsing, URL normalization on responses, and api_get/api_object/api_payload.

  • lacuna_research_mcp/config.py Runtime constants, RuntimeConfig, package user-agent construction, and environment parsing.

  • lacuna_research_mcp/ids.py Helpers that accept either raw ids or Lacuna page URLs and extract safe API path segments.

  • lacuna_research_mcp/normalize.py Response post-processing for relative Lacuna URLs and markdown links.

  • lacuna_research_mcp/errors.py User-facing exception type for Lacuna API access failures.

Notes

  • get_paper and get_direction default to view="context". These context views request Lacuna's compact agent-oriented payloads by default to keep MCP responses small. Paper context includes summary_markdown when available (otherwise abstract), authors, and figures; direction context includes summary_markdown, capped papers/authors/related directions, and truncation markers. Use view="full" when you need the raw metadata, and the other paper views (preview, blog, figures, concepts, neighbors) when you want one isolated sub-resource.

  • An explicit relevance-sorted paper search with no custom fields defaults to the server's production lexical+semantic ranker. Set ranking_profile="semantic" for embedding-based retrieval (with a possible exact-title overlay) or "bm25_title_abstract" for title-and-abstract lexical matching.

  • Most detail tools accept either the id returned by search or the corresponding Lacuna URL.

  • Relative Lacuna URLs in url/*_url response fields and fields named summary_markdown, article_markdown, markdown, content, or description are normalized to absolute URLs.

  • Venue and institution keys are opaque hashes (for example d7bf22905bd6), never human-readable names like icml. Find the key with search_lacuna(search_type="venue") first, or pass a /venue/... page URL.

Citation

If you find our work helpful, feel free to cite the papers behind Lacuna's research-proposal generation and research map.

Research-proposal generation — The Alien Space of Science

@inproceedings{artiles2026alien,
  title     = {The Alien Space of Science: Sampling Coherent but Cognitively Unavailable Research Directions},
  author    = {Artiles, Alejandro H. and Weiss, Martin and Brinkmann, Levin and Rahwan, Iyad and Sch{\"o}lkopf, Bernhard and Pal, Christopher and Larochelle, Hugo and Goyal, Anirudh and Rahaman, Nasim},
  booktitle = {Advances in Neural Information Processing Systems},
  year      = {2026},
  eprint    = {2603.01092},
  archivePrefix = {arXiv},
  url       = {https://arxiv.org/abs/2603.01092}
}

Research map — Lacuna

@misc{weiss2026lacunaresearchmapmachine,
  title         = {Lacuna: A Research Map for Machine Learning},
  author        = {Martin Weiss and Miles Q. Li and Alejandro H. Artiles and Yacine Mkhinini and Chris Pal and Hugo Larochelle and Nasim Rahaman},
  year          = {2026},
  eprint        = {2606.26246},
  archivePrefix = {arXiv},
  primaryClass  = {cs.DL},
  url           = {https://arxiv.org/abs/2606.26246}
}

License

MIT. See LICENSE.

Available Tools

13 tools
get_author_contextGet AuthorA
Read-onlyIdempotent
Inspect

Profile one researcher: their main papers and the directions they shaped.

Use for "who is X in research terms" or "what is X known for".

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.

Inputs: author_id_or_url (required), view, include_neighbors. Returns: object

get_author_directionsList Author DirectionsA
Read-onlyIdempotent
Inspect

List the research directions one author publishes in, one page at a time.

Use for "what areas does X work in" or to check whether a person is active in a given direction. Pass an author id or URL.

Inputs: author_id_or_url (required), limit, offset. Returns: object

get_author_neighborsList Similar AuthorsA
Read-onlyIdempotent
Inspect

List researchers whose work is closest to one author's, ranked.

Use for "who else works on what X works on": finding possible collaborators, reviewers or related groups. Pass an author id or URL.

Inputs: author_id_or_url (required), limit, offset. Returns: object

get_author_papersList Author PapersA
Read-onlyIdempotent
Inspect

List what one author has published, newest first, one page at a time.

Use for "what has X worked on recently". Pass an author id or URL from search_lacuna(search_type="author") or from any paper's author list.

Inputs: author_id_or_url (required), limit, offset. Returns: object

get_directionGet Research DirectionA
Read-onlyIdempotent
Inspect

Describe one research direction: what it is, who leads it, what is nearby.

Use for "who works on X", "what is the state of X" and "what is adjacent to X", after search_lacuna(search_type="cluster") finds the direction. The context names the direction's leading authors, key papers and related directions.

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.

Inputs: cluster_id_or_url (required), view. Returns: object

get_direction_papersList Direction PapersA
Read-onlyIdempotent
Inspect

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.).

Inputs: cluster_id_or_url (required), page, view, limit. Returns: object

get_hypothesisGet Research ProposalA
Read-onlyIdempotent
Inspect

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.

Inputs: hypothesis_id_or_url (required), view. Returns: object

get_institution_authorsList Institution AuthorsA
Read-onlyIdempotent
Inspect

Fetch one page of authors who list a Lacuna institution on their papers.

Each author appears because published papers list this institution as one of their affiliations. This is a record of research output, not a staff directory: it may be incomplete or out of date and does not show current employment. Each entry has the author's name, Lacuna page and paper count; there are no contact details or other personal data.

Results are ordered by paper count. Use authors_total, authors_returned, authors_offset, and authors_truncated to page through the complete list.

Inputs: institution_key_or_url (required), limit, offset. Returns: object

get_institution_contextGet InstitutionA
Read-onlyIdempotent
Inspect

Describe the research output of a university, lab or company.

Use for "what does X publish" or "who are the most active authors at X".

The context summarizes the institution's research output: its paper and author counts and the authors who publish most often under it. Affiliations come from the author affiliations listed on published papers, not from staff directories, and may be incomplete or out of date. The response has no contact details, biographies or employment records.

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.

Inputs: institution_key_or_url (required), view. Returns: object

get_paperGet PaperA
Read-onlyIdempotent
Inspect

Fetch one paper: its summary, authors, venue, figures, linked resources, or full text.

Accepts a Lacuna artifact ID or paper URL from search_lacuna, or an outside identifier for the same paper: an arXiv ID (2310.06825), a DOI, or an arXiv, DOI or OpenReview URL. Use this when the user names a specific paper or after a search. For an outside identifier that is not in Lacuna's ML/AI corpus, the result is found: false with a note saying so. The default view is a summary; ask for the full text only when the summary does not answer the question.

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.

  • "fulltext": the paper itself, max_chars at a time (default 40,000, at most 100,000) from offset; pass the returned next_offset to keep reading. format says what you got: "latex" is the arXiv LaTeX source without its bibliography (citations appear as \cite keys); "pdf_text" is text extracted from the PDF, where equations and tables can be garbled. A scanned paper has no text.

figure_limit (context view only) caps the figure preview (server default 3). Pass 0 to suppress figure previews while keeping a figures_truncated signal.

Inputs: artifact_id_or_url (required), view, offset, max_chars, +2 more. Returns: object

get_resourceGet ResourceA
Read-onlyIdempotent
Inspect

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//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.

Inputs: resource_id_or_url (required). Returns: object

get_venue_contextGet VenueA
Read-onlyIdempotent
Inspect

Describe a conference or journal: its top authors and directions, by year.

Use for "what did NeurIPS 2025 focus on" or "who publishes most at X".

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).

Inputs: venue_key_or_url (required), view, year. Returns: object

search_lacunaSearch LacunaA
Read-onlyIdempotent
Inspect

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).

Start here for any question without an ID. Set search_type to what the question is about: paper for literature; cluster for a research direction ("who works on X", "what is the state of X"); author, institution or venue for a person, a lab or a conference; hypothesis for open research ideas; resource for code, datasets and models. Then pass a result's id or url to the matching detail tool.

A query that is an arXiv ID, a DOI, or an arXiv, DOI or OpenReview URL returns that exact paper. Paper results carry identifiers (arXiv ID, DOI, OpenReview URL where known), which other research tools accept.

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.

Inputs: query (required), sort, limit, venue, +9 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 13 tools

    Disambiguation4/5

    Each tool maps to a distinct entity+action (paper, direction, author, venue, institution, resource, hypothesis), and the four author tools are separated by explicit use cases (papers, directions, profile, neighbors). There is mild overlap where get_author_context bundles main papers and directions that get_author_papers/get_author_directions return in full, and where get_institution_context's capped author list overlaps get_institution_authors, but the descriptions make the compact-vs-paginated distinction clear.

    Naming Consistency4/5

    Names follow a predictable get_<entity>[_<subresource>] pattern throughout (get_paper, get_direction_papers, get_author_neighbors, get_institution_authors). The only deviation is search_lacuna, which breaks the get_ verb style, though as the single entry-point search tool it is still easy to place.

    Tool Count5/5

    Thirteen tools is well within the ideal band and each one earns its place by covering a distinct entity type in a multi-entity research corpus. The search mega-tool absorbs query-side variation instead of spawning a dozen narrow search endpoints.

    Completeness4/5

    Coverage is broad and mostly symmetric: paper, direction, author, venue, institution, resource, and hypothesis all have retrieval paths, and pagination exists for direction papers and institution authors. Minor gaps remain, notably no paginated venue-paper listing (parallel to get_direction_papers) and no explicit citation/reference traversal beyond the 'neighbors' related-papers view.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    • Knowledge Network for AI Agents and creators: Search, rate, and review programming guides via MCP

      https://mcp.prometheus.sv/
    • Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP

      https://api.lorg.ai/mcp
    • Stateless agentic tools over MCP: concept extraction, long-context, knowledge graph, planning.

      https://api.wauldo.com/mcp
    • Rivul is a free, read-only remote MCP server for searching scholarly literature. It runs semantic search over more than 300 million paper records from a dated OpenAlex snapshot, so an agent can find papers by meaning rather than exact keywords, then open the full record for any result. Tools: - search_papers: semantic search with optional filters for publication year range, minimum citation count, open access only, topic and field. Sort by relevance, most cited, newest or oldest. - get_paper_details: the full record for one work by its OpenAlex ID: title, every author, venue, work type, topic, field, publication date, citation count, DOI and open-access links. - usage_status: the workspace's MCP usage for the current day. Results come only from the index, never from a model. Each result carries a stable OpenAlex ID so the source can be checked, and every response states the snapshot date. Useful for literature reviews, scoping reviews, finding highly cited or open-access papers on a topic, citation chasing, and checking that a cited paper exists. Free for every account, with no plans or payment. Sign in with Google through OAuth 2.1 (PKCE, dynamic client registration), or use an MCP key from rivul.ai. Endpoint: https://rivul.ai/mcp (Streamable HTTP). Setup and docs: https://rivul.ai/features/atlas

      https://rivul.ai/mcp

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search code by meaning, explore codebase structure, store and query knowledge with temporal facts, and read source code through a set of MCP tools.
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables scientific literature research through multi-agent search, analysis, and semantic memory, exposing 9 MCP tools for querying, storing, and retrieving research findings.
      15 PyPI
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search and retrieve academic papers, author profiles, and citation data from the Scopus database via MCP tools.
      12
      28 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to explore a repository map via MCP, with tools for briefs, scoping, symbol lookup, module details, and freshness checks.
      6 npm
      MIT