MCP server health, State of MCP census
CausalLayer MCP
io.github.smq9sn5jck-coder/causallayer
Deterministic AI liability attribution with Bitcoin-anchored proof certificates.
Checks
The exact rows akashi check io.github.smq9sn5jck-coder/causallayer prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | warn | probe error: http2: response body closed |
| package npm | pass | published (0.4.0) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 10 tools: submit_incident, verify_certificate, verify_certificate_recompute, submit_otel_trace, simulate_remediation, query_jurisdiction_overlay, evaluate_prospective_response, get_anchor_status, ... |
| at least one live entrypoint | pass | 2 alive |
Evidence
Packages
- npm causallayer-mcp · published(0.4.0)
Remote endpoints
- https://mcp.faultkey.com/mcp
streamable-http · reachable· HTTP 200· initialize_ok
10 tools: submit_incident, verify_certificate, verify_certificate_recompute, submit_otel_trace, simulate_remediation, query_jurisdiction_overlay, evaluate_prospective_response, get_anchor_status, ...
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check io.github.smq9sn5jck-coder/causallayerInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check io.github.smq9sn5jck-coder/causallayer --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.