check-claim is answering right now. Last checked 13 min ago. It exposes 1 tools. Last commit 10 Oct 2026.
Check that a source really says what your claim says, before you publish. Verbatim, multi-path.
Today is the operative word: we check check-claim every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
claude mcp add check-claim --transport http https://check-claim.amdal-dev.workers.dev/mcp
{
"mcpServers": {
"check-claim": {
"url": "https://check-claim.amdal-dev.workers.dev/mcp"
}
}
}
[mcp_servers.check-claim]
url = "https://check-claim.amdal-dev.workers.dev/mcp"
{
"mcpServers": {
"check-claim": {
"url": "https://check-claim.amdal-dev.workers.dev/mcp"
}
}
}
{
"mcpServers": {
"check-claim": {
"url": "https://check-claim.amdal-dev.workers.dev/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
check_claim
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://check-claim.amdal-dev.workers.dev/mcp | streamable-http | answering | 151 ms | 13 min ago |
Flag marketing claims your evidence cannot substantiate, before you publish.
Check the bank behind an IBAN before you pay: bank-code check, BIC with source, bank-level sanctions
Who launched it, what exit really costs, is the pool what it claims. Facts only, no advice.
Does a cited URL exist, and does the source name what your claim names? Two answers.
Before your agent pays an x402 API, check if vet402 bought it with its own money and what came back.
Publish a site your AI built to paid hosting, then read it back, change a page or restore a version.
Check whether an email address is real and will accept mail before you send to it.
Check the danger grade of any public MCP server before you connect.
Answers built from our own checks of this server.