lacuna-research-search
https://lacuna.tiptreesystems.com
Registry code: 5be52bfb569efa1e
Lacuna is a read-only knowledge graph of machine learning and AI research: papers, research directions (clusters), authors, venues, institutions, generated hypotheses, and paper-linked resources (code, datasets, models). It does not cover biographies, news, or non-research web content; answer questions outside that scope from other sources rather than guessing. Workflow: if you have no ID or URL, call search_lacuna first, then pass the IDs or URLs it returns to the detail tools to fetch entity details. When a Lacuna entity materially informs an answer, cite its canonical Lacuna URL so the…
- endpoint
- https://lacuna.tiptreesystems.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is lacuna-research-search live?
- Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.
- Is lacuna-research-search free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does lacuna-research-search have?
- 13 tools: get_author_directions, search_lacuna, get_direction, get_direction_papers, get_author_neighbors, get_institution_authors, get_hypothesis, get_paper, ….
- Is lacuna-research-search safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 13 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_author_directions unknown 41m ago
Fetch one page of an author's named research directions.
{ "type": "object", "title": "get_author_directionsArguments", "required": [ "author_id_or_url" ], "properties": { "limit": { "type": "integer", "title": "Limit", "default": 50 }, "offset": { "type": "integer", "title": "Offset", "default": 0 }, "author_id_or_url": { "type": "string", "title": "Author Id Or Url" } } }arguments 23 linessearch_lacuna unknown never probed
Search Lacuna's ML/AI corpus for papers, research directions, authors, venues, institutions, novel research hypotheses, and research resources (code repositories, datasets, models, and demos linked to papers). For novel ML/AI research ideas, use search_type="hypothesis", then get_hypothesis on promising results. search_type accepts all, cluster, paper, author, institution, venue, hypothesis, or resource. Use paper for literature and get_paper to read a result. Use other sources for biographies, news, and non-research web content. Resources: search_type="resource" searches GitHub repositories, Hugging Face datasets/models, and Zenodo records that Lacuna has linked to at least one paper. To find benchmark or evaluation datasets, use search_type="resource" with resource_kind="dataset" (for example query "image classification benchmark" or a dataset name like "ImageNet"). resource_kind accepts codebase, dataset, model, or demo (one value or a list); provider accepts github, huggingface, or zenodo. Both filters require search_type "resource" or "all" (with either filter set, only resources are returned). Each result has an external `url`, a Lacuna `context_url`, and `linked_paper_count`; call get_resource on its id to list the linked papers (with their relationship to the resource), then get_paper on those papers for reported results and numbers. Resource search does not support date_from/date_to, venue, year sorting, or semantic ranking. ranking_profile accepts: - default / lexical (default): production ranking; relevance-sorted paper searches combine lexical and semantic retrieval when fields is unset. - semantic: conceptual paper retrieval; supported for paper and all. - bm25_title_abstract / bm25: lexical paper matching over those fields. sort accepts relevance (default), year_desc, or year_asc. Semantic ranking cannot use year sorting; constrain recency with date_from/date_to instead. date_from and date_to are inclusive YYYY, YYYY-MM, or YYYY-MM-DD bounds. author_id_or_url constrains a paper search to one author. Pass an author ID or Lacuna author page URL; it requires search_type="paper". fields optionally restricts and weights lexical fields, for example "title^4,abstract". Supported names are title, abstract, summary, concepts, name, top_names, and venue, plus description, topics, provider_key, and paper_titles for resources (a resource's title already includes its description, topics, README text, and linked paper titles). Fields must exist on the selected search_type, weights must be within 0 < weight <= 100, and fields cannot be combined with semantic ranking.
{ "type": "object", "title": "search_lacunaArguments", "required": [ "query" ], "properties": { "sort": { "type": "string", "title": "Sort", "default": "relevance" }, "limit": { "type": "integer", "title": "Limit", "default": 10 }, "query": { "type": "string", "title": "Query" }, "venue": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Venue", "default": null }, "fields": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Fields", "default": null }, "offset": { "type": "integer", "title": "Offset", "default": 0 }, "date_to": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Date To", "default": null }, "provider": { "anyOf": [ { "type": "string" }, { "type": "array", "items": { "type": "string" } }, { "type": "null" } ], "title": "Provider", "default": null }, "date_from": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Date From", "default": null }, "search_type": { "type": "string", "title": "Search Type", "default": "all" }, "resource_kind": { "anyOf": [ { "type": "string" }, { "type": "array", "items": { "type": "string" } }, { "type": "null" } ], "title": "Resource Kind", "default": null }, "ranking_profile": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Ranking Profile", "default": null }, "author_id_or_url": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Author Id Or Url", "default": null } } }arguments 141 linesget_direction unknown never probed
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.
{ "type": "object", "title": "get_directionArguments", "required": [ "cluster_id_or_url" ], "properties": { "view": { "enum": [ "context", "full" ], "type": "string", "title": "View", "default": "context" }, "cluster_id_or_url": { "anyOf": [ { "type": "string" }, { "type": "integer" } ], "title": "Cluster Id Or Url" } } }arguments 29 linesget_direction_papers unknown never probed
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.).
{ "type": "object", "title": "get_direction_papersArguments", "required": [ "cluster_id_or_url" ], "properties": { "page": { "type": "integer", "title": "Page", "default": 1 }, "view": { "enum": [ "compact", "full" ], "type": "string", "title": "View", "default": "compact" }, "limit": { "type": "integer", "title": "Limit", "default": 24 }, "cluster_id_or_url": { "anyOf": [ { "type": "string" }, { "type": "integer" } ], "title": "Cluster Id Or Url" } } }arguments 39 linesget_author_neighbors unknown 41m ago
Fetch one ranked page of neighboring/similar Lacuna authors.
{ "type": "object", "title": "get_author_neighborsArguments", "required": [ "author_id_or_url" ], "properties": { "limit": { "type": "integer", "title": "Limit", "default": 8 }, "offset": { "type": "integer", "title": "Offset", "default": 0 }, "author_id_or_url": { "type": "string", "title": "Author Id Or Url" } } }arguments 23 linesget_institution_authors unknown never probed
Fetch one page of authors affiliated with a Lacuna institution. Results are ordered by paper count. Use authors_total, authors_returned, authors_offset, and authors_truncated to page through the complete list.
{ "type": "object", "title": "get_institution_authorsArguments", "required": [ "institution_key_or_url" ], "properties": { "limit": { "type": "integer", "title": "Limit", "default": 50 }, "offset": { "type": "integer", "title": "Offset", "default": 0 }, "institution_key_or_url": { "type": "string", "title": "Institution Key Or Url" } } }arguments 23 linesget_hypothesis unknown never probed
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.
{ "type": "object", "title": "get_hypothesisArguments", "required": [ "hypothesis_id_or_url" ], "properties": { "view": { "enum": [ "context", "full" ], "type": "string", "title": "View", "default": "context" }, "hypothesis_id_or_url": { "type": "string", "title": "Hypothesis Id Or Url" } } }arguments 22 linesget_paper unknown never probed
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.
{ "type": "object", "title": "get_paperArguments", "required": [ "artifact_id_or_url" ], "properties": { "view": { "enum": [ "context", "full", "preview", "blog", "figures", "concepts", "neighbors" ], "type": "string", "title": "View", "default": "context" }, "figure_limit": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "title": "Figure Limit", "default": null }, "include_resources": { "type": "boolean", "title": "Include Resources", "default": true }, "artifact_id_or_url": { "type": "string", "title": "Artifact Id Or Url" } } }arguments 44 linesget_resource unknown never probed
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.
{ "type": "object", "title": "get_resourceArguments", "required": [ "resource_id_or_url" ], "properties": { "resource_id_or_url": { "type": "string", "title": "Resource Id Or Url" } } }arguments 13 linesget_author_papers unknown never probed
Fetch one page of an author's papers, ordered from newest to oldest.
{ "type": "object", "title": "get_author_papersArguments", "required": [ "author_id_or_url" ], "properties": { "limit": { "type": "integer", "title": "Limit", "default": 50 }, "offset": { "type": "integer", "title": "Offset", "default": 0 }, "author_id_or_url": { "type": "string", "title": "Author Id Or Url" } } }arguments 23 linesget_author_context unknown 41m ago
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.
{ "type": "object", "title": "get_author_contextArguments", "required": [ "author_id_or_url" ], "properties": { "view": { "enum": [ "context", "full" ], "type": "string", "title": "View", "default": "context" }, "author_id_or_url": { "type": "string", "title": "Author Id Or Url" }, "include_neighbors": { "type": "boolean", "title": "Include Neighbors", "default": false } } }arguments 27 linesget_venue_context unknown never probed
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).
{ "type": "object", "title": "get_venue_contextArguments", "required": [ "venue_key_or_url" ], "properties": { "view": { "enum": [ "context", "full" ], "type": "string", "title": "View", "default": "context" }, "year": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "title": "Year", "default": null }, "venue_key_or_url": { "type": "string", "title": "Venue Key Or Url" } } }arguments 34 linesget_institution_context unknown never probed
Fetch agent-oriented context for a Lacuna institution. view selects the response shape: - "context" (default, recommended): compact institution context — capped top authors with the duplicated institution block dropped server-side. - "full": the complete institution context shape (duplicated institution record and a bounded author list with explicit truncation metadata). Use get_institution_authors to page through the complete author list.
{ "type": "object", "title": "get_institution_contextArguments", "required": [ "institution_key_or_url" ], "properties": { "view": { "enum": [ "context", "full" ], "type": "string", "title": "View", "default": "context" }, "institution_key_or_url": { "type": "string", "title": "Institution Key Or Url" } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5be52bfb569efa1e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5be52bfb569efa1e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5be52bfb569efa1e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.