Remote MCP · Endpoint
Kaal Corpus: Verifiable Claim Layer MCP server
No. Kaal Corpus: Verifiable Claim Layer answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://corpus.openstanding.org/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.wulfkaal/corpus
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 170 ms
- Tools exposed
- 18 tools
- Uptime, last 30 days
- 92.9% from 14 checks
- Described by its publisher as
- Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF
- Website
- https://wulfkaal.github.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 170 ms |
| 9 days ago | Handshake completed | 192 ms |
| 10 days ago | Handshake completed | 215 ms |
| 11 days ago | Handshake completed | 151 ms |
| 12 days ago | Handshake completed | 195 ms |
| 14 days ago | Handshake completed | 229 ms |
| 14 days ago | Handshake completed | 159 ms |
| 15 days ago | Handshake completed | 167 ms |
| 17 days ago | Handshake completed | 220 ms |
| 19 days ago | Handshake completed | 182 ms |
| 21 days ago | Handshake completed | 202 ms |
| 24 days ago | Handshake completed | 233 ms |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 28 days ago | Handshake completed | 228 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 31.
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.