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.1Apache 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.15 PyPI2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search 1m+ 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.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to explore a repository map via MCP, with tools for briefs, scoping, symbol lookup, module details, and freshness checks.6 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to search and retrieve academic papers, author profiles, and citation data from the Scopus database via MCP tools.1228 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.7MIT
TDQS
Scored across 13 tools
Each tool maps to a distinct entity+action (paper, direction, author, venue, institution, resource, hypothesis), and the four author tools are separated by explicit use cases (papers, directions, profile, neighbors). There is mild overlap where get_author_context bundles main papers and directions that get_author_papers/get_author_directions return in full, and where get_institution_context's capped author list overlaps get_institution_authors, but the descriptions make the compact-vs-paginated distinction clear.
Names follow a predictable get_<entity>[_<subresource>] pattern throughout (get_paper, get_direction_papers, get_author_neighbors, get_institution_authors). The only deviation is search_lacuna, which breaks the get_ verb style, though as the single entry-point search tool it is still easy to place.
Thirteen tools is well within the ideal band and each one earns its place by covering a distinct entity type in a multi-entity research corpus. The search mega-tool absorbs query-side variation instead of spawning a dozen narrow search endpoints.
Coverage is broad and mostly symmetric: paper, direction, author, venue, institution, resource, and hypothesis all have retrieval paths, and pagination exists for direction papers and institution authors. Minor gaps remain, notably no paginated venue-paper listing (parallel to get_direction_papers) and no explicit citation/reference traversal beyond the 'neighbors' related-papers view.