Literature Evidence MCP
Related Servers
Alternatives to Literature Evidence MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables scientists and their AI agents to check quoted passages against pinned open-access PubMed Central full texts, look up retraction status from PMC and Crossref, and run recorded literature searches. Every quote check, search and annotation is written to an append-only, hash-chained log that can be verified, giving a dated record of what was searched and found.7MIT
- AlicenseAqualityCmaintenanceEnables keyless, read-only literature research by searching OpenAlex, Crossref, Europe PMC, PubMed and arXiv at once, merging and ranking results, following citations, retrieving open-access full text, looking up clinical trials, verifying citations, and exporting BibTeX, RIS or CSL-JSON without any accounts or API keys.102MIT
- FlicenseNot gradedqualityAmaintenanceEnables researchers and AI assistants to verify bibliographic existence and metadata consistency, resolve DOI, PMID, PMCID, and arXiv identifiers, and perform explainable multi-source matching without destructive edits.-
- AlicenseNot gradedqualityCmaintenanceEnables traceable scholarly literature reviews using free APIs, generating reports where every claim links to evidence IDs.MIT
- AlicenseAqualityDmaintenanceEnables searching scholarly literature across CrossRef, ERIC, Semantic Scholar, and OpenAlex, and retrieving open-access PDFs via Unpaywall.9MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants and researchers to verify bibliographic existence and metadata consistency, convert DOI, PMID, PMCID, or arXiv identifiers into BibTeX, and review explainable multi-source matches without destructive edits.-
TDQS
Scored across 35 tools
The set has many closely related tools whose boundaries require careful reading: search_literature vs search_literature_extended vs log_review_search, verify_citation vs verify_claim vs verify_source_quote vs rust_locate_quote, and assess_methodology vs audit_methodology vs audit_pmc_methodology. Descriptions do help distinguish them, but the sheer number of near-overlapping verification and methodology tools creates real misselection risk.
Most names follow a snake_case verb_noun or noun_action pattern, making the set broadly readable. There are minor deviations such as language-prefixed tools (rust_, go_, cpp_, nli_, bm25_) and noun-first names like prisma_dual_screen and propagation_alerts, but conventions are not chaotic.
At 35 tools, the surface is heavy for a single evidence-workflow server, and several tools appear to be optional language-specific or experimental variants rather than essential operations. The count exceeds the reasonable 3-15 range and introduces redundancy that makes the set harder to navigate.
The server covers a broad systematic-review lifecycle: literature search, metadata retrieval, full-text access, screening, risk-of-bias/GRADE recording, citation checking, statistical checks, bibliography export, and ledger verification. Some stages are explicitly incomplete or non-inferential, such as missing full-text PRISMA stages and deliberately non-validated methodology screening, but most core workflows have corresponding tools.