check-claim
REMOTE · CHECK-CLAIM.AMDAL-DEV.WORKERS.DEV
Check that a source really says what your claim says, before you publish. Verbatim, multi-path.
Available components
Last scanned (8 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Education and Research
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 282 tokens (~282/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 63
First indexed and scored.
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 18 Oct 2026 · Probed https://check-claim.amdal-dev.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=amdal-dev.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5f5d0755ada35c8c767bff82e0584da3d75 |
| SANs: *.amdal-dev.workers.dev, amdal-dev.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of check-claim.amdal-dev.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://check-claim.amdal-dev.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://check-claim.amdal-dev.workers.dev/mcp | Inconclusive | 405 |
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 →
check_claim Check a claim against its source ~260
Check whether a source really says what a claim says it says, before you publish the claim. Give the claim and the source (an http(s) URL or arxiv:<id>). Without a quote you get back the source sentences that best match the claim. With quote (a sentence copied verbatim from the source) and stance (supports|contradicts, your judgment), the tool fetches the source on independent paths (origin, reader, web archive; for arXiv: metadata and full text) and returns SUPPORTED or CONTRADICTED only if the quote is found verbatim on at least two of them, else UNVERIFIABLE. A quote that is not in the source is reported as QUOTE NOT IN SOURCE, with the nearest real sentences. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The sentence you want to check, as you would publish it. |
| quote | string | – | Optional. The sentence from the source, copied verbatim, that bears on the claim. |
| source | string | yes | The source the claim rests on: an http(s) URL, or arxiv:<id>. |
| stance | string | – | Optional, with quote. Whether that sentence supports or contradicts the claim (default supports). |
No output schema declared.
No examples provided.
How do I install the check-claim MCP server?
check-claim is a hosted endpoint at https://check-claim.amdal-dev.workers.dev/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-claim.amdal-dev.workers.dev
claude mcp add --transport http piiiico-check-claim 'https://check-claim.amdal-dev.workers.dev/mcp'
What is the check-claim MCP server?
check-claim is an MCP server listed in the public MCP registry as io.github.piiiico/check-claim. Check that a source really says what your claim says, before you publish. Verbatim, multi-path. This page covers its hosted endpoint (https://check-claim.amdal-dev.workers.dev/mcp).
Is the check-claim MCP server safe to use?
check-claim scores 66 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 check-claim MCP server expose?
check-claim exposes 1 tool: check_claim. Their descriptions and schemas cost roughly 260 tokens of context every time the server is loaded.
Does the check-claim MCP server require authentication?
No. We connected to check-claim without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the check-claim MCP server still maintained?
check-claim is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.