Lacuna Research MCP server
io.github.tiptreesystems/lacuna-research-mcptiptreesystemsstreamable-httpv0.6.15Scanned
Search Lacuna's ML research graph for papers, directions, authors, venues, and hypotheses.
13 tools: 13 only read.
- Reads private data · 1
- Reads text others write · 13
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Lacuna Research MCP server can do
The Lacuna Research MCP server is published by the GitHub account tiptreesystems. It has 13 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (get_resource); 13 tools bring in text other people can write (search_lacuna, get_hypothesis, get_direction and 10 more).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.6.15.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Only reads 13Show 13 read-only tools
get_author_contextProfile one researcher: their main papers and the directions they shaped.Reads text others writeNo findings
Why it is in this group
- The name "get_author_context" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Author
get_author_directionsList the research directions one author publishes in, one page at a time.Reads text others writeNo findings
Why it is in this group
- The name "get_author_directions" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Author Directions
get_author_neighborsList researchers whose work is closest to one author's, ranked.Reads text others writeNo findings
Why it is in this group
- The name "get_author_neighbors" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Similar Authors
get_author_papersList what one author has published, newest first, one page at a time.Reads text others writeNo findings
Why it is in this group
- The name "get_author_papers" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Author Papers
get_directionDescribe one research direction: what it is, who leads it, what is nearby.Reads text others writeNo findings
Why it is in this group
- The name "get_direction" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Research Direction
get_direction_papersFetch paginated papers associated with a Lacuna research direction/cluster.Reads text others writeNo findings
Why it is in this group
- The name "get_direction_papers" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Direction Papers
get_hypothesisFetch a generated novel ML/AI research proposal from Lacuna.Reads text others writeNo findings
Why it is in this group
- The name "get_hypothesis" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Research Proposal
get_institution_authorsFetch one page of authors who list a Lacuna institution on their papers.Reads text others writeNo findings
Why it is in this group
- The name "get_institution_authors" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Institution Authors
get_institution_contextDescribe the research output of a university, lab or company.Reads text others writeNo findings
Why it is in this group
- The name "get_institution_context" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Institution
get_paperFetch one paper: its summary, authors, venue, figures, linked resources, or full text.Reads text others write1 finding
Why it is in this group
- The name "get_paper" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,412 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ss 0 to suppress figure previews while keeping a `figures_truncated` signal."
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Paper
get_resourceFetch a Lacuna research resource (code repository, dataset, model, or demo).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_resource" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "repository": it reads repositories.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Resource
get_venue_contextDescribe a conference or journal: its top authors and directions, by year.Reads text others writeNo findings
Why it is in this group
- The name "get_venue_context" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Venue
search_lacunaSearch Lacuna's ML/AI corpus for papers, research directions, authors, venues, institutions, novel research hypotheses, and research resources (code repositories, datasets, models,…Reads text others write1 finding
Why it is in this group
- The name "search_lacuna" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 3,419 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...0 < weight <= 100, and fields cannot be combined with semantic ranking."
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Search Lacuna
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write13
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
- Infosearch_lacuna
The description is 3,419 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...0 < weight <= 100, and fields cannot be combined with semantic ranking."
- Infoget_paper
The description is 2,412 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ss 0 to suppress figure previews while keeping a `figures_truncated` signal."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools10 changed.~10 changedView diff
- Changed:get_author_contextOnly readsdescription
- Changed:get_author_directionsOnly readsdescription
- Changed:get_author_neighborsOnly readsdescription
- Changed:get_author_papersOnly readsdescription
- Changed:get_directionOnly readsdescription
- Changed:get_institution_authorsOnly readsdescription
- Changed:get_institution_contextOnly readsdescription
- Changed:get_paperOnly readsdescriptioninputSchema
- Changed:get_venue_contextOnly readsdescription
- Changed:search_lacunaOnly readsdescription
Install
Pinned to version 0.6.15. Values in angle brackets are yours to fill in.
claude mcp add --transport http lacuna-research https://lacuna.tiptreesystems.com/api/mcpclaude mcp add --transport http lacuna-research https://lacuna.tiptreesystems.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lacuna-research__search_lacuna",
"mcp__lacuna-research__get_hypothesis",
"mcp__lacuna-research__get_direction",
"mcp__lacuna-research__get_direction_papers",
"mcp__lacuna-research__get_paper",
"mcp__lacuna-research__get_resource",
"mcp__lacuna-research__get_author_papers",
"mcp__lacuna-research__get_author_directions",
"mcp__lacuna-research__get_author_context",
"mcp__lacuna-research__get_author_neighbors",
"mcp__lacuna-research__get_venue_context",
"mcp__lacuna-research__get_institution_context",
"mcp__lacuna-research__get_institution_authors"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lacuna-research. Review it before you use it.
Capability tags behind 13 rules
- mcp__lacuna-research__search_lacuna untrusted-input
- mcp__lacuna-research__get_hypothesis untrusted-input
- mcp__lacuna-research__get_direction untrusted-input
- mcp__lacuna-research__get_direction_papers untrusted-input
- mcp__lacuna-research__get_paper untrusted-input
- mcp__lacuna-research__get_resource private-data, untrusted-input
- mcp__lacuna-research__get_author_papers untrusted-input
- mcp__lacuna-research__get_author_directions untrusted-input
- mcp__lacuna-research__get_author_context untrusted-input
- mcp__lacuna-research__get_author_neighbors untrusted-input
- mcp__lacuna-research__get_venue_context untrusted-input
- mcp__lacuna-research__get_institution_context untrusted-input
- mcp__lacuna-research__get_institution_authors untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tiptreesystems/lacuna-research-mcp/verify?hash=ce9623b35c249c78cd69ba7920f4160fe398baa8581917c3930e345bd060524a" | jq -e '.changed == false'Pinned hash ce9623b35c24, from Nov 19, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.tiptreesystems/lacuna-research-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.tiptreesystems/lacuna-research-mcp)Source: MCP Registry · repository. Synced Nov 19, 2026, 14:18 UTC.
Lacuna Research MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lacuna Research MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Lacuna Research MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Lacuna Research MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lacuna Research MCP server have?
- 13 tools: 13 read. search_lacuna, get_hypothesis, get_direction, get_direction_papers, get_paper, get_resource, get_author_papers, get_author_directions and 5 more.
Does the Lacuna Research MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Lacuna Research MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lacuna Research MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.