Remote MCP · Endpoint

check-claim MCP server

No. check-claim answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://check-claim.amdal-dev.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.piiiico/check-claim
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
353 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Check that a source really says what your claim says, before you publish. Verbatim, multi-path.
Listing
From the official MCP registry (active).
Recent checks of check-claim
CheckedResultHandshake
2 hours agoHandshake completed353 ms
1 day agoHandshake completed254 ms
3 days agoHandshake completed351 ms
3 days agoHandshake completed249 ms
4 days agoHandshake completed336 ms
5 days agoHandshake completed403 ms
7 days agoHandshake completed243 ms
10 days agoHandshake completed318 ms
12 days agoHandshake completed338 ms
15 days agoHandshake completed361 ms
17 days agoHandshake completed423 ms
19 days agoHandshake completed598 ms
21 days agoHandshake completed363 ms
23 days agoHandshake completed302 ms
25 days agoHandshake completed332 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with check-claim and makes no claim about it beyond what these checks measured.