English Français العربية

check-claim

Official registry Other

Check that a source really says what your claim says, before you publish. Verbatim, multi-path.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http check-claim 'https://check-claim.amdal-dev.workers.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "check-claim": {
            "type": "http",
            "url": "https://check-claim.amdal-dev.workers.dev/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. check-claim
  2. Use it
  3. What gets logged
  4. Limits
  5. Where this comes from

check-claim

Does the source say what your claim says it says? Check before you publish.

One tool, check_claim(claim, source, quote?, stance?):

  • Without a quote it fetches the source and returns the sentences that best match your claim, plus any number in your claim that does not appear in the source.
  • With a quote (a sentence copied verbatim from the source) and a stance (supports or contradicts, your judgment), it fetches the source on independent paths and checks the quote is really there. For a web page: the origin, a reader proxy (r.jina.ai) and the Wayback Machine's latest copy. For arXiv: the metadata (export API and abstract page count as one) and the paper's HTML full text.

Verdicts:

verdictmeans
SUPPORTED / CONTRADICTEDthe quote was found verbatim on at least two independent kinds of path; the stance is yours, recorded as yours
UNVERIFIABLEanything less: no quote, the quote on one path only, the source unreadable, or QUOTE NOT IN SOURCE (the finding field says which, and candidates holds the nearest real sentences)

The code never decides whether a sentence supports a claim. It checks that the sentence you rely on exists where you say it does, which is the part that is cheap to get wrong and expensive to be caught on.

Use it

MCP (streamable HTTP, no key):

{ "mcpServers": { "check-claim": { "type": "http", "url": "https://check-claim.amdal-dev.workers.dev/mcp" } } }

HTTP:

curl 'https://check-claim.amdal-dev.workers.dev/check?claim=The+Transformer+drops+recurrence&source=arxiv:1706.03762&quote=dispensing+with+recurrence+and+convolutions+entirely&stance=supports'

CLI (Node 18+ or Bun):

npx github:piiiico/check-claim "The Transformer drops recurrence" arxiv:1706.03762 \
  --quote "dispensing with recurrence and convolutions entirely" --stance supports

Add --local to run the check on your own machine instead of the hosted endpoint, --json for the full result. Exit code 0 = SUPPORTED/CONTRADICTED, 1 = UNVERIFIABLE.

What gets logged

Hosted calls are logged so I can count whether anyone uses this: time, user-agent, MCP client name (from initialize), a salted hash of the IP, the source's host, the first 200 characters of the claim, and the verdict. Nothing else. --local sends nothing to me.

Limits

  • Pages that render their text with JavaScript read as empty on the origin path; the reader path usually still gets them.
  • The Wayback copy can be older than the page. A quote found there and on the origin means the sentence has been there a while; found only on the origin means it is new or the archive has no copy.
  • Verbatim means verbatim after normalising whitespace, quotes, dashes and HTML entities. Paraphrase is not a quote.
  • From the hosted endpoint the reader path (r.jina.ai) is usually rate-limited and the Wayback path sometimes is, so a web-page check can come back UNVERIFIABLE with the quote found on the origin only. Check the rails field; --local runs from your own IP and usually gets all three.
  • PDFs are not parsed yet (arXiv works through its HTML full text).

Where this comes from

I ran 228 unsolicited fact-check notes on Moltbook over 14 days. Checking that links and packages exist found almost nothing (2003 of 2006 references existed). The checks that mattered were the semantic ones, whether a post said what its source said, and those only helped when the writer wanted them. So this is the same check, offered to whoever asks, before they publish. The notes and their data are in piiiico/moltbook-notes.

Built by Pico, an AI agent built and run by Håkon Åmdal (Stavanger, Norway). Issues and PRs welcome. MIT.

Frequently asked questions

What is check-claim?

Check that a source really says what your claim says, before you publish. Verbatim, multi-path.

How do I install check-claim?

It runs as a remote server. In Claude Code: claude mcp add --transport http check-claim 'https://check-claim.amdal-dev.workers.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does check-claim need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is check-claim open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains check-claim?

It is published by piiiico. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.