Model Context Protocol server for CausalLayer — deterministic AI liability attribution with Bitcoin-anchored, signed certificates. Runs on Cloudflare
Most cloud and infrastructure work still happens through a UI a human drives. Causallayer MCP MCP server moves it into the conversation instead. Model Context Protocol server for CausalLayer — deterministic AI liability attribution with Bitcoin-anchored, signed certificates. Runs on Cloudflare Workers or locally via npx.
This is the official Model Context Protocol (MCP) server for the CausalLayer engine, packaged as a Cloudflare Worker. It lets AI agents (Claude Desktop, Cursor, Cline, Continue, Windsurf) call the four core liability-attribution tools without writing a single line of integration code.
The server publishes 5 tools. What each one is for:
submit_incident — Submit an AI incident for deterministic liability attribution. Returns a signed CausalCertificateV1 with per-agent fault allocation, evidence-chainverify_certificate — Independently verify a certificate (signature, Merkle integrity, issuer status) without calling FaultKeyget_anchor_status — Return the index of all Tessera anchor batches or one batch's full JSON (signed Merkle root, OpenTimestamps proof reference)query_issuer_registry — List all trusted CausalLayer issuer public-key fingerprints, status, and validity windowsCursor — The Cursor tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Causallayer MCP's toolset — submit_incident, verify_certificate, get_anchor_status and 2 more — is a fair guide to whether it matches your workflow. It is maintained by smq9sn5jck-coder; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| submit_incident | Submit an AI incident for deterministic liability attribution. Returns a signed CausalCertificateV1 with per-agent fault allocation, evidence-chain completeness, and Bitcoin-anchored proof. |
| verify_certificate | Independently verify a certificate (signature, Merkle integrity, issuer status) without calling FaultKey. |
| get_anchor_status | Return the index of all Tessera anchor batches or one batch's full JSON (signed Merkle root, OpenTimestamps proof reference). |
| query_issuer_registry | List all trusted CausalLayer issuer public-key fingerprints, status, and validity windows. |
| Cursor | The Cursor tool exposed by this server. |
{
"mcpServers": {
"faultkey": {
"command": "npx",
"args": ["-y", "causallayer-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.