med-lit-mcp
Related Servers
Alternatives to med-lit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables traceable scholarly literature reviews using free APIs, generating reports where every claim links to evidence IDs.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM-assisted biomedical literature screening and structured extraction from PubMed alerts, PMIDs, DOIs, and GEO accessions, with full-text retrieval and multi-provider LLM support.55 PyPI2MIT
- AlicenseBqualityCmaintenanceEnables locally-first literature research through an MCP host by collecting sources, parsing documents, retrieving evidence, validating citations, and exporting research records in multiple formats.38MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run reproducible, high-recall literature search across seven source families with RRF fusion, fetch open-access full texts (falling back to abstracts), expand citations, export BibTeX/RIS, and audit reference coverage — all without any LLM API key, leaving query planning and writing to the agent. Multiple agent clients share one accumulating literature pool and background search jobs that keep running after sessions close.MIT
- AlicenseBqualityAmaintenanceAI-operable research workspace integrating Zotero, Obsidian, and NotebookLM. Search papers (arXiv/Semantic Scholar/PubMed/CrossRef), ingest into Zotero, sync per-paper notes to Obsidian, verify NotebookLM briefs. All three external tools optional.7666 PyPI64MIT
- AlicenseBqualityBmaintenanceEnables read-only cognitive retrospect over Obsidian notes, surfacing stance changes, verifying claims with citable evidence, and avoiding unfounded causal stories via hybrid retrieval and eight read-only MCP tools.910MIT
TDQS
Scored across 33 tools
Descriptions are detailed and mostly stage-scoped, clearly separating triage, screening, fetching, extraction, wiki, synthesis, and duplicate resolution. Some boundaries blur between record_screening_decisions and review_article, and between the manual next_*/record_* workflow and the bot_start/bot_next/bot_finish orchestration.
All tool names use snake_case, which keeps the set readable and predictable at a high level. However, it mixes verb_noun forms like start_search and record_extraction with noun/prefixed forms like guide, project_settings, next_synthesis, and bot_start.
33 tools is heavy, though the broad literature-review lifecycle gives some justification for a large surface. There is likely redundancy between the bot orchestration tools and the many manual next_*/record_* stage tools.
The surface covers project setup, question validation, search, triage, screening, fetching, extraction, wiki/synthesis, duplicate resolution, export, and bot runs, leaving few dead ends. Minor gaps remain, such as no explicit delete/archive project or remove-article operation.