Lacuna Research MCP
Related Servers
Alternatives to Lacuna Research MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to retrieve compact, cited repository maps through MCP tools such as search, symbol inspection, flow investigation, and deep context loading.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables scientific literature research through multi-agent search, analysis, and semantic memory, exposing 9 MCP tools for querying, storing, and retrieving research findings.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search 580,000+ open-access papers, standards, textbooks, and legal documents, resolve identifiers such as RFCs, DOIs, and legal citations, download PDFs, and retrieve citations and metadata through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to explore a repository map via MCP, with tools for briefs, scoping, symbol lookup, module details, and freshness checks.8 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to search and retrieve academic papers, author profiles, and citation data from the Scopus database via MCP tools.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.310 npm7MIT
TDQS
Scored across 13 tools
Most tools target clearly distinct entity+facet combinations, and descriptions explicitly distinguish context views from dedicated paginated fetches. However, get_author_context's include_neighbors option overlaps with get_author_neighbors, and context views include capped papers/authors that dedicated tools like get_author_papers and get_direction_papers also provide, creating minor boundary blur.
All tools follow a consistent snake_case verb_noun pattern: search_lacuna for search, and get_<entity>_<facet> or get_<entity>_context for fetches. There is no mixing of camelCase, different verb styles, or irregular naming.
13 tools map cleanly to the seven main entity types (paper, author, direction, venue, institution, resource, hypothesis) plus pagination and search needs. The set is neither bloated nor thin for a read-only research corpus.
Search covers all entity types, and dedicated fetch tools exist for papers, directions, authors, venues, institutions, resources, and hypotheses, with pagination where needed. Minor gaps remain, such as no non-context get_author or get_venue, no batch paper retrieval, but agents can work around these via search and context tools.