Stipple — Reference Verification MCP Server

by stipple Your server? Claim it

answering

Stipple — Reference Verification is answering right now. Last checked 14 min ago. It exposes 1 tools.

Fact-check citations: resolve, match, support claims. Arithmetic rechecked. Free to start.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1241 ms

Response time

average over 24h

open, no key

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add openwarrant-verify --transport http https://www.stipple.sh/mcp-verify

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "openwarrant-verify": {
      "url": "https://www.stipple.sh/mcp-verify"
    }
  }
}

~/.codex/config.toml

[mcp_servers.openwarrant-verify]
url = "https://www.stipple.sh/mcp-verify"

.cursor/mcp.json

{
  "mcpServers": {
    "openwarrant-verify": {
      "url": "https://www.stipple.sh/mcp-verify"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "openwarrant-verify": {
      "url": "https://www.stipple.sh/mcp-verify"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

verify_references

Fact-check a document's REFERENCES and CLAIMS — built for AI-generated reports whose citations must be checked before they're trusted. USE THIS WHEN someone shares a report, article, whitepaper, or deep-research export (or a link to one) and asks: is this accurate / legit? are these citations real? fact-check this. did the AI make this up? Also use it proactively before relying on any AI-written document. Provide the document ONE way: `url` (a public http(s) link to a PDF or web page — fetched server-side, the cheapest call: no need to download or encode anything), `text` (pasted markdown/plain prose), OR `bytes_b64` (a base64 PDF; URLs are read from the PDF's link annotations, so they're exact). Default (fast): provenance (is it a ChatGPT deep-research export?), citation resolution (live / archived / dead, papers matched against arXiv/Crossref to catch 'real ID, wrong paper'), and internal MATH (recompute the doc's own arithmetic). Set `deep=true` to also fetch each cited source and judge whether it SUPPORTS or CONTRADICTS the claim (slower, ~a minute). Returns a trust summary, per-item tables, and a shareable `permalink` to the public fact-check record. HONEST BOUNDARY: this reports verification COVERAGE, not truth — 'supported' means evidence-backed (not necessarily true) and 'unsupported' means no evidence found (not necessarily false). It tells a reviewer WHERE to look; it does not bless the document, and it never affects the fraud risk band.

Endpoints

URL	Transport	State	Latency	Checked
https://www.stipple.sh/mcp-verify	streamable-http	answering	1609 ms	14 min ago

Alternatives to Stipple — Reference Verification

same job, measured the same way

Citeguard

by xiaweiyi713

Falsification-first citation auditor: existence, metadata, and claim-support checks via MCP.

63 installs/wk local only

CN Evidence

by workers-mikeyang7789-cn-evidence-mcp-public

Chinese supplier verification via Remote MCP; free resolve, paid Basic/Full evidence via x402.

3 tools answering

402oracle

by 402oracle

Signed verification attestations for agent decisions: business, price, freshness, claim checks.

4 tools answering

Atlas MCP

by atlasverified

AI-powered organic supply chain verification: certification, OFAC, FDA import checks.

answering

UCP Checker

by ucpchecker

Check any domain for UCP support and resolve verified UCP storefronts. Read-only, keyless.

8 tools answering

DocQA MCP

by agentsconsultants-api

AI document verification: catch hallucinations, arithmetic errors, and field mismatches.

38 installs/wk local only

VerifyAPI — fact-check with signed receipts

by kythekitty

Fact-check any claim with live web sources. Ed25519-signed receipts. Catches hallucinations.

307 installs/wk local only

refcheck

by benchoi93

Verify academic citations against real databases. Catches hallucinated references, exports BibTeX.

52 installs/wk local only

Stipple — Reference Verification — questions

Answers built from our own checks of this server.

What can Stipple — Reference Verification do?

It exposes 1 tools, read directly from the server on our last check. Among them: verify_references. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Stipple — Reference Verification working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1241 ms. The bar chart above shows every period we have measured.

Is Stipple — Reference Verification still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Stipple — Reference Verification?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Stipple — Reference Verification need an API key?

No. Stipple — Reference Verification completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Stipple — Reference Verification?

It answers our handshake in 1241 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.