Remote MCP · Endpoint
FaultKey · CausalLayer MCP server
No. FaultKey · CausalLayer answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.smq9sn5jck-cloud/causallayer-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 595 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split.
- Website
- https://faultkey.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 595 ms |
| 2 days ago | Handshake completed | 548 ms |
| 4 days ago | Handshake completed | 636 ms |
| 5 days ago | Handshake completed | 426 ms |
| 7 days ago | Handshake completed | 674 ms |
| 8 days ago | Handshake completed | 540 ms |
| 9 days ago | Handshake completed | 564 ms |
| 12 days ago | Handshake completed | 732 ms |
| 13 days ago | Handshake completed | 445 ms |
| 15 days ago | Handshake completed | 645 ms |
| 17 days ago | Handshake completed | 522 ms |
| 18 days ago | Handshake completed | 736 ms |
| 19 days ago | Handshake completed | 510 ms |
| 20 days ago | Handshake completed | 597 ms |
| 20 days ago | Handshake completed | 667 ms |
| 21 days ago | Handshake completed | 887 ms |
| 23 days ago | Handshake completed | 896 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 FaultKey · CausalLayer and makes no claim about it beyond what these checks measured.