CiteCheck MCP
Related Servers
Alternatives to CiteCheck MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables verifying citations in reference lists and BibTeX by detecting fabricated or mismatched references and retractions, and returning corrected BibTeX.3MIT
- AlicenseAqualityBmaintenanceEnables AI writing assistants to retrieve citable evidence from local PDFs and verify draft citations against their sources locally, providing verifiable support for claims.21MIT
- AlicenseAqualityBmaintenanceProvides local academic literature search and writing support by querying OpenAlex, arXiv, and Crossref, downloading open-access PDFs, extracting IMRaD sections, and appending BibTeX references.42MIT
- AlicenseAqualityDmaintenancePrevents citation hallucination by verifying academic citations against CrossRef's database of 150+ million publications before they can be mentioned, ensuring every citation includes a valid DOI.315MIT

CiteStamp MCP serverofficial
AlicenseNot gradedqualityBmaintenanceGround citations before your agent emits them by checking references against public scholarly registries and flagging hallucinated or retracted ones.MIT- AlicenseAqualityCmaintenanceEnables pre-submission review of ML papers inside Claude Code or Claude Desktop by checking format and anonymization risks, resolving every reference, finding prior work for each claim, verifying quotes against the PDF, and running methodology and writing checks. It reports findings only, never scores, ratings, or accept/reject verdicts, and never rewrites the author's text.7MIT
TDQS
Scored across 19 tools
Each tool has a clearly distinct role: verify_quote checks, find_evidence ranks, and record_verdict persists, while read_source, open_project, fetch_sources, and attach_pdf all target different resource stages. The rewrite lifecycle (propose_rewrite, propose_insertion, apply_rewrite, revert_rewrite, discard_rewrite, list_rewrites) is also cleanly separated by action.
Every tool follows a consistent verb_noun snake_case pattern (verify_quote, open_project, list_claims, apply_rewrite, etc.). There are no mixed conventions or vague verbs; even the rewrite variants follow a predictable propose/apply/revert/discard/list scheme.
19 tools is on the heavy side of the ideal 3-15 range, but the domain (citation checking of a manuscript) is genuinely multi-stage and each tool earns its place. No redundant tools inflate the count.
The surface covers the full workflow: opening a project, listing/getting claims, verifying and recording verdicts, bibliography checks, source fetching, rewrite proposal through rollback, and report export. Minor gaps like closing/archiving a project or a search-within-bibliography helper exist but are workable.