Citation Check
REMOTE · CHECK.HOLOWEAVE.ORG · SCANNED SEP 22
Free mechanical checks for AI text: unnamed counts, dangling references, bad arithmetic, misquotes.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Trade dormant under § 93 Abs 2 GewO 1994 from 2026-08-28; endpoint answers 410.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Citation Check MCP server?
Citation Check is a hosted endpoint at https://check.holoweave.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · check.holoweave.org
claude mcp add --transport http ninefiveonefive-citation-check 'https://check.holoweave.org/mcp'
{
"mcpServers": {
"ninefiveonefive-citation-check": {
"url": "https://check.holoweave.org/mcp"
}
}
} {
"servers": {
"ninefiveonefive-citation-check": {
"type": "http",
"url": "https://check.holoweave.org/mcp"
}
}
} [mcp_servers.ninefiveonefive-citation-check] url = "https://check.holoweave.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ninefiveonefive-citation-check": {
"type": "remote",
"url": "https://check.holoweave.org/mcp",
"enabled": true
}
}
} openclaw mcp add ninefiveonefive-citation-check --url 'https://check.holoweave.org/mcp' --transport streamable-http
mcp_servers:
ninefiveonefive-citation-check:
url: "https://check.holoweave.org/mcp" {
"McpServers": {
"ninefiveonefive-citation-check": {
"Transport": "http",
"Url": "https://check.holoweave.org/mcp"
}
}
} assistant mcp add ninefiveonefive-citation-check -t streamable-http -u 'https://check.holoweave.org/mcp'
{
"mcpServers": {
"ninefiveonefive-citation-check": {
"type": "http",
"url": "https://check.holoweave.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Aug 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Aug 26 0
- Tool “citation_check” rewrote its description, which is the text the model reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 0
- Schema quality: 692 → 180 ▲ functional
- The server now declares the “resources” capability functional
- New resource “a recorded grounding run” functional
- New resource “declared expected answers” functional
- New resource “the example document” functional
- New resource “the self-audit, unabridged” functional
- “citation_check” added an optional parameter “url” cosmetic
- 15 Aug 26 0
- Tool “citation_check” rewrote its description, which is the text the model reads security
- Schema quality: 563 → 692 ▼ functional
- “citation_check” reworded the description of “ground” cosmetic
- 14 Aug 26 0
- Tool “citation_check” rewrote its description, which is the text the model reads security
- 13 Aug 26 0
- Tool “citation_check” rewrote its description, which is the text the model reads security
- Schema quality: 349 → 548 ▼ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “check-document” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://check.holoweave.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=check.holoweave.org | CN=YR1,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | RSA 2048 | SHA256-RSA | 656832954b9405cb66037f39bd6037bb8f6 |
| SANs: check.holoweave.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of check.holoweave.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| holoweave.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 410 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://check.holoweave.org/mcp | HTTP error | 410 | |
| http (plaintext) | http://check.holoweave.org/mcp | HTTPS enforced | 301 | https://check.holoweave.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
citation_check ~776
Check a document against the claims it makes about ITSELF — miscounts, pointers to things that are not there, totals that do not add up. CALL IT WITH NO ARGUMENTS for a complete worked verdict on our example document: nothing to prepare, no key, no signup, and it says plainly that the document was ours. Then send your own text the same way. 7 checks run on every call, each answering one question no other answers: Enumeration and manifest (a document against the counts and listings it makes about ITSELF); Internal reference (a pointer inside the document against the thing it points at); Arithmetic (a stated total against the figures standing beside it); Count against list (a count introducing a list against the items actually in that list); Declared bound and form (an instruction the document gave ITSELF against what it then produced); Ordinal sequence (a named sequence against its own order); The document against its own principles (a rule the document stated against what the document later does with it). Returns convictions with line locations. Every answer also states what did NOT apply and what was never examined, because silence from a checker is otherwise unreadable. Verdicts are 3: conviction, clean, refusal — a refusal is neither guilt nor innocence, and there are 5 forms of it. The full catalogue, machine-readable, is at https://check.holoweave.org/api/checks. Pure parsing — no model reads the text. The demonstration runs on our example document; a document of your own is examined by the same fixed rules, within the free allowance, and is not retained. Runs in CI on changed markdown via the citation-check-action GitHub Action. Free tier: 3 calls/day, no key. Max 200 KB. With a prepaid key sent as an Authorization: Bearer header there is no daily limit, and arguments.ground=true additionally fetches each cited source and compares the claim against what it actually says. Beyond the free tier: prepaid packs, identical checks — prices are quoted when a ceiling…
| Name | Type | Req | Description |
|---|---|---|---|
| ground | boolean | – | Also fetch each cited source and compare the claim against what it actually says. Requires a key: the free tier is mechanical only and no model reads your text. WHAT THIS SENDS: when ground is true,… |
| reach | boolean | – | FREE. Report which of the document's cited sources an automated reader can actually retrieve, and why not where not: readable, unreachable, not-text, thin (answered but carried no document), or skipp… |
| text | string | – | The document to check (markdown or plain text). OPTIONAL: omit it and the tool runs on our own example document instead and says so — a one-call demonstration that needs nothing prepared. Your docume… |
| url | string | – | OPTIONAL alternative to text: a public https address of the document to check — the tool fetches it (200 KB cap, 3 url-borne documents a day on their own counter) and runs the same checks. The answer… |
No output schema declared.
No examples provided.
What is the Citation Check MCP server?
Citation Check is an MCP server listed in the public MCP registry as io.github.ninefiveonefive/citation-check. Free mechanical checks for AI text: unnamed counts, dangling references, bad arithmetic, misquotes. This page covers its hosted endpoint (https://check.holoweave.org/mcp).
Is the Citation Check MCP server safe to use?
Citation Check scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Citation Check MCP server expose?
Citation Check exposes 1 tool: citation_check. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.
Does the Citation Check MCP server require authentication?
No. We connected to Citation Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Citation Check MCP server still maintained?
Citation Check is marked deprecated in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.