Skip to main content
Glama

Server Details

Search Lacuna's ML research graph for papers, directions, authors, venues, and hypotheses.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
tiptreesystems/lacuna-research-mcp
GitHub Stars
74
Server Listing
Lacuna Research MCP
ChatGPT
–
Claude
Lacuna Research

TDQS

A4.1/5.0

Scored across 13 tools

Disambiguation4/5

Most tools map cleanly to one entity type (paper, author, direction, institution, venue, resource, hypothesis), and descriptions steer between them well. However, get_author_context overlaps with get_author_directions and get_author_papers (it returns capped papers and an impact_directions list), and get_direction's context also embeds key papers, so an agent may fetch a heavier tool when a lighter one would do.

Naming Consistency5/5

Every tool follows a predictable get_<entity>[_subresource] pattern (get_author_papers, get_direction_papers, get_institution_authors, get_venue_context) with a single, clearly named search entry point. No camelCase/snake_case mixing or vague verbs.

Tool Count5/5

13 tools is well within the sweet spot and each one covers a distinct entity or sub-resource in the research corpus. Nothing feels padded or missing from the count alone.

Completeness4/5

The surface spans search plus detail for papers, authors, directions, institutions, venues, resources, and hypotheses, with paging and view shapes—strong read-only coverage of the domain. Gaps are minor: no dedicated citation/reference traversal (only paper 'neighbors') and no comparison or trend tools, but agents can work around these.

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 Lacuna direction URL.

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;
  1,000 to 100,000, other values are moved into that range) from
  `offset`; pass the returned `next_offset` to keep reading.
  `total_chars` is the length of the whole text, and an `offset` past it
  returns empty text. `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. Lacuna holds text for most arXiv papers and for
  fewer papers known only by DOI; a paper without text returns
  `available: false`.

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

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…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables discovery and analysis of research ecosystems by extracting metadata from paper URLs, GitHub repositories, and research names. Automatically finds related papers, code repositories, models, datasets, and authors across platforms like arXiv, HuggingFace, and GitHub.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables researchers to search ArXiv papers, extract key insights (problems, methods, results) from abstracts, and perform ML-powered analysis including topic modeling, trend visualization, and author collaboration networks.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.