Citation Safe Verifier
REMOTE · CITATIONSAFE.COM
Verifies legal citations vs primary sources: existence, quote match, proposition support.
Available components
Last scanned (12 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 17 Oct 2026.
Category Education and Research
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.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.
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.
- 24 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Oct 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 17 Oct 26 −64
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 24 Oct 2026 · Probed https://citationsafe.com/api/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of citationsafe.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| citationsafe.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://citationsafe.com/api/mcp | Unreachable | ||
| http (plaintext) | http://citationsafe.com/api/mcp | HTTPS enforced |
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 →
batch_verify_citations Verify legal citations across multiple texts (batch) ~138
Runs the same 3-layer citation verification as verify_citation across multiple texts in a single call. Each item is billed against your CitationSafe usage exactly like an individual verify_citation call — batching never bypasses your plan's monthly limit. Max 10 items per batch, 64,000 characters per item. Requires a signed-in CitationSafe account (Authorization: Bearer <access_token>) — anonymous batch calls are not supported, use verify_citation for anonymous single-text checks.
| Name | Type | Req | Description |
|---|---|---|---|
| texts | array | yes | Array of texts to verify, each processed as a separate verification (max 10 items, 64,000 chars each) |
No output schema declared.
No examples provided.
get_verification Get a past CitationSafe verification report by ID ~61
Retrieves a previously run CitationSafe verification (by the verificationId returned from verify_citation/verify_document, or from a citationsafe.com/v/{id} share link) and returns its full per-citation results.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Verification ID |
No output schema declared.
No examples provided.
is_this_case_real Check whether a single case citation is real ~154
Deterministic existence check (Layer 1 only, no LLM) for one legal citation against CourtListener's primary-source database. Answers the single question "is this case real" for one citation — for multi-citation quote-checked verdicts across a whole brief, use verify_brief instead. Free tier: 5 checks/day per IP, no key required. For unlimited access, pass an API key as "Authorization: Bearer <key>" (contact support@citationsafe.com to request one).
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | A single citation, e.g. "410 U.S. 113" or "Roe v. Wade, 410 U.S. 113 (1973)" |
No output schema declared.
No examples provided.
search_phantoms Search known AI-hallucinated (phantom) case citations ~98
Searches CitationSafe's phantom-citation registry — fabricated case names/citations that have shown up in real, sanctioned AI-hallucination incidents — by case name or the AI system that produced them. Read-only, public data. Returns an empty array (not an error) if nothing matches or the registry has no entries yet.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text match against the phantom case name or the AI system that generated it |
No output schema declared.
No examples provided.
search_sanctions Search the AI-hallucination court sanctions database ~102
Searches CitationSafe's database of real court sanctions/orders arising from AI-hallucinated legal citations, by court name, party/case name keyword, or free-text keyword. Read-only, public data — same dataset backing citationsafe.com/sanctions-database.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | Filter by court name (partial match, e.g. "S.D.N.Y.") |
| query | string | – | Free-text keyword to match against the case name |
No output schema declared.
No examples provided.
verify_brief Verify every citation in a brief or excerpt ~153
Runs existence (Layer 1) and quote-match (Layer 2) checks — both deterministic, no LLM — on every citation found in the given text and returns one verdict per citation. The multi-citation counterpart to is_this_case_real. Proposition support (Layer 3) is not included on this free/API-key surface; sign in at citationsafe.com for full 3-layer verification via verify_citation. Free tier: 5 checks/day per IP (one verify_brief call = one check, regardless of how many citations the text contains); an API key bypasses the daily cap.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Raw text (brief excerpt, motion, memo) containing one or more legal citations |
No output schema declared.
No examples provided.
verify_citation Verify legal citations in text ~134
Checks every legal citation in the given text against primary sources: does the cited case exist (Layer 1, CourtListener database lookup — deterministic, no LLM), does a quoted passage appear in the source opinion (Layer 2), and — on paid CitationSafe tiers — does the case support the proposition it's cited for (Layer 3). Returns VERIFIED / UNCONFIRMED / UNCONFIRMED — OUTSIDE COVERAGE / SOURCE UNAVAILABLE per citation, never a bare true/false, with source links. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Raw text containing one or more legal citations to verify |
No output schema declared.
No examples provided.
verify_document Verify legal citations in a document URL ~76
Fetches a document (PDF, DOCX, or plain text) from a URL and runs the same 3-layer citation verification as verify_citation. Use this when you have a link to a brief rather than pasted text.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of the PDF, DOCX, or text document to fetch and verify |
No output schema declared.
No examples provided.
How do I install the Citation Safe Verifier MCP server?
Citation Safe Verifier is a hosted endpoint at https://citationsafe.com/api/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 · citationsafe.com
claude mcp add --transport http com-citationsafe-verifier 'https://citationsafe.com/api/mcp'
What is the Citation Safe Verifier MCP server?
Citation Safe Verifier is an MCP server listed in the public MCP registry as com.citationsafe/verifier. Verifies legal citations vs primary sources: existence, quote match, proposition support. This page covers its hosted endpoint (https://citationsafe.com/api/mcp).
Is the Citation Safe Verifier MCP server safe to use?
Citation Safe Verifier scores 0 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 Safe Verifier MCP server expose?
Citation Safe Verifier exposes 8 tools: verify_citation, verify_document, get_verification, batch_verify_citations, search_sanctions, and 3 more. Their descriptions and schemas cost roughly 916 tokens of context every time the server is loaded.
Does the Citation Safe Verifier MCP server require authentication?
Its publisher declares no required credentials for Citation Safe Verifier. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Citation Safe Verifier MCP server still maintained?
Citation Safe Verifier has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.