Lacuna Research MCP
REMOTE · LACUNA.TIPTREESYSTEMS.COM · 2 COMPONENTS
Search Lacuna's ML research graph for papers, directions, authors, venues, and hypotheses.
Available components
Last scanned (2 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2820 tokens (~216/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Tool “get_institution_authors” rewrote its description, which is the text the model reads security
- Tool “get_institution_context” rewrote its description, which is the text the model reads security
- Server version: 0.6.4 → 0.6.9 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://lacuna.tiptreesystems.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tiptreesystems.com | CN=WE1,O=Google Trust Services,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 684d78fb40e62e13f81536dd9d268c |
| SANs: tiptreesystems.com, *.tiptreesystems.com, *.dev.tiptreesystems.com, dev.tiptreesystems.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lacuna.tiptreesystems.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tiptreesystems.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lacuna.tiptreesystems.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://lacuna.tiptreesystems.com/api/mcp | HTTPS enforced | 301 | https://lacuna.tiptreesystems.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_author_context Get Author ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id_or_url | string | yes | – |
| include_neighbors | boolean | – | – |
| view | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_author_directions List Author Directions ~44
Fetch one page of an author's named research directions.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id_or_url | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_author_neighbors List Similar Authors ~46
Fetch one ranked page of neighboring/similar Lacuna authors.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id_or_url | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_author_papers List Author Papers ~48
Fetch one page of an author's papers, ordered from newest to oldest.
| Name | Type | Req | Description |
|---|---|---|---|
| author_id_or_url | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_direction Get Research Direction ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster_id_or_url | – | yes | – |
| view | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_direction_papers List Direction Papers ~149
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.).
| Name | Type | Req | Description |
|---|---|---|---|
| cluster_id_or_url | – | yes | – |
| limit | integer | – | – |
| page | integer | – | – |
| view | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_hypothesis Get Research Proposal ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hypothesis_id_or_url | string | yes | – |
| view | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_institution_authors List Institution Authors ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| institution_key_or_url | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_institution_context Get Institution ~192
Fetch agent-oriented context for a Lacuna institution (a university, lab or company). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| institution_key_or_url | string | yes | – |
| view | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_paper Get Paper ~358
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id_or_url | string | yes | – |
| figure_limit | – | – | – |
| include_resources | boolean | – | – |
| view | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_resource Get Resource ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_id_or_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_venue_context Get Venue ~192
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).
| Name | Type | Req | Description |
|---|---|---|---|
| venue_key_or_url | string | yes | – |
| view | string | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_lacuna Search Lacuna ~703
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 re…
| Name | Type | Req | Description |
|---|---|---|---|
| author_id_or_url | – | – | – |
| date_from | – | – | – |
| date_to | – | – | – |
| fields | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| provider | – | – | – |
| query | string | yes | – |
| ranking_profile | – | – | – |
| resource_kind | – | – | – |
| search_type | string | – | – |
| sort | string | – | – |
| venue | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Lacuna Research MCP server?
Lacuna Research MCP is a hosted endpoint at https://lacuna.tiptreesystems.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lacuna.tiptreesystems.com
claude mcp add --transport http tiptreesystems-lacuna-research-mcp 'https://lacuna.tiptreesystems.com/api/mcp'
What is the Lacuna Research MCP server?
Lacuna Research MCP is listed in the public MCP registry as io.github.tiptreesystems/lacuna-research-mcp. Search Lacuna's ML research graph for papers, directions, authors, venues, and hypotheses. This page covers its hosted endpoint (https://lacuna.tiptreesystems.com/api/mcp).
Is the Lacuna Research MCP server safe to use?
Lacuna Research MCP scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lacuna Research MCP server expose?
Lacuna Research MCP exposes 13 tools: search_lacuna, get_hypothesis, get_direction, get_direction_papers, get_paper, and 8 more. Their descriptions and schemas cost roughly 2,581 tokens of context every time the server is loaded.
Does the Lacuna Research MCP server require authentication?
No. We connected to Lacuna Research MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lacuna Research MCP server still maintained?
Lacuna Research MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.