
quotecheck
io.github.feenmilePublished by GitHub account feenmilev0.1.1Updated Oct 31, 2026
Check that a quoted passage appears word for word in its cited source (URL, DOI or PubMed ID).
Overview
Checks whether a quoted passage appears word for word in its cited source (URL, DOI or PubMed ID) and reports where, via one MCP tool.
- What you can do
- Verify a quote against a source given as an http/https URL, a doi: identifier or a pmid: identifier
- Return a verdict of EXACT, NEAR, NOT_FOUND or SOURCE_UNAVAILABLE with a similarity score and reason
- Report character offsets and the source's actual wording as a snippet when a near match is found
- Fetch the extracted plain text of a source so the assistant can inspect it directly
- When to use it
- Useful when an assistant drafts text with direct quotations or citations and you want to confirm the wording really appears in the cited source before publishing. It catches real references paired with misstated wording, but it does not judge whether the claim is true.
- Requirements
- Runs locally over stdio as a Python package (quotecheck-mcp, command quotecheck-mcp) requiring Python 3.10 or newer; the MCP server needs the optional mcp SDK. No accounts, API keys or environment variables are declared. Network access is needed to fetch sources.
Installation
In SourceWeft
- Open quotecheck in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
quotecheck
Does the quoted passage actually appear in the source?
AI agents (and people) often cite real sources but misstate what those sources
say: real references, wrong claims. quotecheck fetches the cited source and
checks that the quoted text is really there, word for word, and tells you where.
Built by Feenmile.
Verdicts
char_start / char_end are Python string indices (end exclusive) into the
plain text quotecheck extracted from the source, which you can get with
quotecheck.fetch_source(source).text.
Read NEAR carefully. A NEAR result means the wording differs. A changed
number ("43,548" vs "43,549") or a dropped "not" can still score above 0.90.
Use the returned snippet as the quotation, or rephrase as a paraphrase.
Sources
https://...orhttp://...URLsdoi:10.xxxx/...(resolved through https://doi.org, following the publisher redirect)pmid:12345(the PubMed abstract, via NCBI E-utilitiesefetch, plain text)
Install
The PyPI distribution is named quotecheck-mcp; the import package and the
command are still quotecheck.
Python 3.10 or newer.
Quick start: CLI
Output is always JSON on stdout. Exit status is 0 when a verdict was printed
(1 with --strict unless EXACT) and 2 for usage errors such as an empty quote.
Quick start: library
The core library uses only the Python standard library.
Quick start: MCP server
The server speaks MCP over stdio and exposes one tool, check_quote(quote, source).
If the script is not on your PATH, use "command": "python", "args": ["-m", "quotecheck.mcp_server"].
The tool description tells the agent to call it before presenting text as a direct quotation, and how to act on each verdict.
Safe fetching
quotecheck fetches URLs that came from model output, so it treats them as untrusted:
- only
httpandhttps; URLs with embedded credentials are refused; - the host is resolved and every resolved address must be public: private, loopback, link-local, multicast, reserved and unspecified addresses (including IPv4-mapped IPv6 forms) are refused; the connection then goes to the checked address, so a second DNS answer cannot swap in an internal one;
- the same checks run again on every redirect, with at most 5 redirects;
- one 15 second deadline covers the whole fetch, and the body is capped at 5 MB (declared, streamed and after decompression);
- requests identify as
quotecheck/0.1 (+https://feenmile.com); - proxy environment variables are not used.
Limits (v0.1)
- EXACT means the text appears, not that the claim is true. quotecheck does not judge context, meaning, or whether the source is reliable. A quote can be verbatim and still be used to support something the source does not say.
- No PDFs. PDF responses return
SOURCE_UNAVAILABLEwith the reasonpdf not supported in v0.1. Many DOIs resolve to a landing page whose abstract is HTML; the full text may only be in a PDF. - No JavaScript rendering. Pages that build their text in the browser come
back empty (
SOURCE_UNAVAILABLE) or incomplete (NOT_FOUND). - Paywalls, logins, cookie walls and bot blocks. quotecheck sees what an
anonymous client sees. Text behind them reads as
NOT_FOUNDorSOURCE_UNAVAILABLE, which does not mean the quote is wrong. - PubMed is abstract-only.
pmid:checks the abstract text, not the full paper. - Ellipses are literal. A quote that skips words with "..." will not match exactly; check each fragment separately.
- HTML extraction is simple. Text is taken from the standard-library HTML parser with script, style and template removed. Navigation, footers and hidden elements are included; text split across unusual markup may not join the way it reads on screen.
- Unicode. Characters are NFKC-normalized one at a time; the same accented letter written in composed and decomposed forms will not match exactly.
- Fuzzy search is anchored on words shared with the quote. Quotes longer than 20,000 characters are checked for exact matches only.
- Pages larger than 5 MB are refused rather than truncated.
Development
The tests are offline. They run a local http.server fixture. Because the
SSRF guard blocks loopback, tests exempt specific fixture (ip, port) pairs
with quotecheck._testing.allow_loopback_endpoints, a test-only switch that is
off unless a test turns it on. A second fixture server is never exempted, so
the tests can prove that a redirect into loopback is refused.
scripts/mutation_check.py copies the project to a temporary directory,
disables the address check, and confirms the suite fails.
License
MIT. See LICENSE.
Source: README.md at commit 8569f6e
Tools
0Version history
1- v0.1.1LatestOct 31, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts