Remote MCP · Endpoint
CausalLayer MCP MCP server
No. CausalLayer MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.faultkey.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.smq9sn5jck-coder/causallayer
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 695 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Deterministic AI liability attribution with Bitcoin-anchored proof certificates.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 695 ms |
| 1 day ago | Handshake completed | 739 ms |
| 2 days ago | Handshake completed | 468 ms |
| 3 days ago | Handshake completed | 687 ms |
| 4 days ago | Handshake completed | 593 ms |
| 5 days ago | Handshake completed | 568 ms |
| 6 days ago | Handshake completed | 842 ms |
| 9 days ago | Handshake completed | 538 ms |
| 11 days ago | Handshake completed | 1.38 s |
| 14 days ago | Handshake completed | 790 ms |
| 16 days ago | Handshake completed | 1.68 s |
| 18 days ago | Handshake completed | 460 ms |
| 20 days ago | Handshake completed | 614 ms |
| 22 days ago | Handshake completed | 715 ms |
| 24 days ago | Handshake completed | 786 ms |
| 26 days ago | Handshake completed | 442 ms |
| 27 days ago | Handshake completed | 449 ms |
| 29 days ago | Handshake completed | 697 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 CausalLayer MCP and makes no claim about it beyond what these checks measured.