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://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
- 228 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
- Website
- https://wulfkaal.github.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 228 ms |
| 2 days ago | Handshake completed | 196 ms |
| 4 days ago | Handshake completed | 176 ms |
| 6 days ago | Handshake completed | 189 ms |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Handshake completed | 274 ms |
| 10 days ago | Handshake completed | 155 ms |
| 11 days ago | Handshake completed | 206 ms |
| 14 days ago | Handshake completed | 149 ms |
| 15 days ago | Handshake completed | 163 ms |
| 17 days ago | Handshake completed | 214 ms |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Handshake completed | 186 ms |
| 21 days ago | Handshake completed | 164 ms |
| 22 days ago | Handshake completed | 224 ms |
| 22 days ago | Handshake completed | 148 ms |
| 23 days ago | Handshake completed | 170 ms |
| 25 days ago | Handshake completed | 165 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.