mcpbeat

Citation Safe Verifier MCP Server

com.citationsafe/verifier
answering

Citation Safe Verifier is answering right now. Last checked 6 min ago. It exposes 8 tools.

Verifies legal citations vs primary sources: existence, quote match, proposition support.

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

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
73.6%
Uptime 24h
67 of 91 checks
8
Tools
read from the server
332 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add verifier --transport http https://citationsafe.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verifier": {
      "url": "https://citationsafe.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verifier]
url = "https://citationsafe.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verifier": {
      "url": "https://citationsafe.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verifier": {
      "url": "https://citationsafe.com/api/mcp"
    }
  }
}

Available tools 8

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

verify
verify_brief
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.
verify_citation
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.
verify_document
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.
batch
batch_verify_citations
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.
phantoms
search_phantoms
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.
sanctions
search_sanctions
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.
this
is_this_case_real
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 [email protected] to request one).
verification
get_verification
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.

Endpoints

URLTransportStateLatencyChecked
https://citationsafe.com/api/mcp streamable-http answering 362 ms 6 min ago

Citation Safe Verifier — questions

Answers built from our own checks of this server.

What can Citation Safe Verifier do?
It exposes 8 tools, read directly from the server on our last check. Among them: batch_verify_citations, get_verification, is_this_case_real, search_phantoms, search_sanctions, verify_brief and 2 more. 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 Citation Safe Verifier working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 67 of 91 checks got a reply (73.6%), average response time 332 ms. The bar chart above shows every period we have measured.
Is Citation Safe Verifier 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 Citation Safe Verifier?
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 Citation Safe Verifier need an API key?
No. Citation Safe Verifier completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Citation Safe Verifier?
It answers our handshake in 332 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.