Skip to content
External endpointresponds

Citation Check

Does a cited URL exist, and does the source name what your claim names? Two answers.

Endpoint URL
https://exmachina-ai.fly.dev/verify
Current status
responds
Last checked
Aug 17, 2026, 05:09 AM UTC
Check
MCP initialize · 8s limit
Latency
174 ms
Response record
1 of 1 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.SecondStageTurbine/citation-check

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
exmachina-citation-check
Version
1.0.0
Capability keys
tools
Tool names
check_citation, verdict_meanings
Instructions excerpt

A citation checker, on its own. No account, no registration, nothing stored about you. Call check_citation with a url and the claim it is meant to support. You get back two separate answers, and the distinction is the whole point: status - does the URL exist? resolved / restricted (gated against bots) / broken. relevance - does the source name the same entity as your claim? corroborates / mismatch / unknown. A 200 answers the first question and tells you nothing about the second. An agent cited two real ClinVar records, for MYO3A and ERCC4, under a claim about BRCA1, plus two gnomAD variants on chromosome 7 for a gene that sits on 17. All of them returned 200. Existence is not support. Honest limit: relevance can only be judged against sources carrying structured metadata (ClinVar, gnomAD, PubMed, DOI). A paper with no gene annotation comes back unknown, so a claim naming no entity cannot be checked at all. unknown never counts against you; it means we could not tell. This is the

Reported Aug 17, 2026, 05:09 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 174ms