Remote MCP · Endpoint

Kaal Corpus: Verifiable Claim Layer MCP server

No. Kaal Corpus: Verifiable Claim Layer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://openstanding.org/corpus/mcp

The last check completed an MCP handshake.

Registry name
io.github.wulfkaal/corpus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
190 ms
Tools exposed
18 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF
Listing
From the official MCP registry (active).
Recent checks of Kaal Corpus: Verifiable Claim Layer
CheckedResultHandshake
1 hour agoHandshake completed190 ms
2 days agoHandshake completed187 ms
4 days agoHandshake completed159 ms
6 days agoHandshake completed176 ms
7 days agoFailed - the server returned an HTTP error—
9 days agoHandshake completed249 ms
10 days agoHandshake completed195 ms
11 days agoHandshake completed215 ms
14 days agoHandshake completed156 ms
15 days agoHandshake completed143 ms
17 days agoHandshake completed185 ms
19 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed179 ms
21 days agoHandshake completed168 ms
22 days agoHandshake completed186 ms
22 days agoHandshake completed165 ms
23 days agoHandshake completed268 ms
25 days agoHandshake completed155 ms

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

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 Kaal Corpus: Verifiable Claim Layer and makes no claim about it beyond what these checks measured.