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.
Listing
From the official MCP registry (active).
Recent checks of FaultKey · CausalLayer
CheckedResultHandshake
2 hours agoHandshake completed595 ms
2 days agoHandshake completed548 ms
4 days agoHandshake completed636 ms
5 days agoHandshake completed426 ms
7 days agoHandshake completed674 ms
8 days agoHandshake completed540 ms
9 days agoHandshake completed564 ms
12 days agoHandshake completed732 ms
13 days agoHandshake completed445 ms
15 days agoHandshake completed645 ms
17 days agoHandshake completed522 ms
18 days agoHandshake completed736 ms
19 days agoHandshake completed510 ms
20 days agoHandshake completed597 ms
20 days agoHandshake completed667 ms
21 days agoHandshake completed887 ms
23 days agoHandshake completed896 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.