FaultKey · CausalLayer

Name: FaultKey · CausalLayer
Author: smq9sn5jck-cloud

MCP serverMCP

Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split.

Until 2026-09-26 this record combined several servers published from one repository. The others now have records of their own: CausalLayer MCP. Checks from before that date include them.

by smq9sn5jck-cloudrepository ↗homepage ↗v0.2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"faultkey-causallayer","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability165/165 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	472 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
12 h ago	mcp initialize	ok	200	1032 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
18 h ago	mcp initialize	ok	200	669 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
24 h ago	mcp initialize	ok	200	676 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
30 h ago	mcp initialize	ok	200	732 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	733 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	747 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	624 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	639 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools
3 d ago	mcp initialize	ok	200	670 ms	server causallayer-mcp 0.4.1 · protocol 2025-06-18 · 10 tools

Tools observed via MCP handshake

submit_incident — Submit an AI incident for deterministic causal liability attribution. Returns a signed CausalCertificate, per-agent liability allocation, evidence-chain complet
verify_certificate — Independently verify a CausalCertificate end-to-end (signature, Merkle integrity, issuer status against the registry). Cost: 1 credit. In production env, certif
verify_certificate_recompute — Independently re-derive a CausalCertificate from its canonical input and compare byte-for-byte against the claimed certificate. This is the strongest verificati
submit_otel_trace — Convert an OpenTelemetry OTLP JSON trace into a FaultKey incident and return the same deterministic CausalCertificate as submit_incident. Each span becomes an e
simulate_remediation — Counterfactual remediation simulator. Given a certificate's verdict + fourFactorScoring + agents and a list of remediation IDs from the FK-METHOD-2026-003 catal
query_jurisdiction_overlay — Multi-jurisdiction overlay (FK-METHOD-2026-004). Given a canonical attributable apportionment (party-id -> share), the union of all jurisdiction role tags on ea
evaluate_prospective_response — Deterministic prospective-evaluation gate (FK-METHOD-2026-006). Pass a ProposedAction BEFORE the agent delivers a response; receive one of three verdicts: 'allo
get_anchor_status — Return the index of all CausalLayer Tessera anchor batches, or one batch's full JSON (signed Merkle root, leaves, OpenTimestamps proof reference). FREE.
query_issuer_registry — Return the CausalLayer issuer registry, or one issuer record. The registry lists all trusted public-key fingerprints, key algorithms, validity windows, and the
extract_incident — Claude-powered structured extractor. Parses unstructured text (news articles, court filings, emails, PDFs, incident reports, logs) into the typed JSON schema re

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.smq9sn5jck-cloud/causallayer-mcp

first seen 1 mo ago · fetched 2 d agoopen ↗

Field history (12 recent events)

14 d ago · declared · name → "FaultKey · CausalLayer"
14 d ago · declared · version → "0.2.0"
14 d ago · declared · publisherName → "smq9sn5jck-cloud"
14 d ago · declared · description → "Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split."
14 d ago · declared · summary → "Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split."
1 mo ago · declared · publisherName → "smq9sn5jck-coder"
1 mo ago · declared · description → "Deterministic AI liability attribution with Bitcoin-anchored proof certificates."
1 mo ago · declared · version → "0.4.0"
1 mo ago · declared · name → "CausalLayer MCP"
1 mo ago · declared · summary → "Deterministic AI liability attribution with Bitcoin-anchored proof certificates."
1 mo ago · declared · description → "Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split."
1 mo ago · declared · summary → "Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split."

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from