CausalLayer MCP
REMOTE · MCP.FAULTKEY.COM · 2 COMPONENTS · SCANNED SEP 20
Deterministic AI liability attribution with Bitcoin-anchored proof certificates.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1769 tokens (~176/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CausalLayer MCP server?
CausalLayer MCP is a hosted endpoint at https://mcp.faultkey.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.faultkey.com
claude mcp add --transport http smq9sn5jck-coder-causallayer 'https://mcp.faultkey.com/mcp'
{
"mcpServers": {
"smq9sn5jck-coder-causallayer": {
"url": "https://mcp.faultkey.com/mcp"
}
}
} {
"servers": {
"smq9sn5jck-coder-causallayer": {
"type": "http",
"url": "https://mcp.faultkey.com/mcp"
}
}
} [mcp_servers.smq9sn5jck-coder-causallayer] url = "https://mcp.faultkey.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"smq9sn5jck-coder-causallayer": {
"type": "remote",
"url": "https://mcp.faultkey.com/mcp",
"enabled": true
}
}
} openclaw mcp add smq9sn5jck-coder-causallayer --url 'https://mcp.faultkey.com/mcp' --transport streamable-http
mcp_servers:
smq9sn5jck-coder-causallayer:
url: "https://mcp.faultkey.com/mcp" {
"McpServers": {
"smq9sn5jck-coder-causallayer": {
"Transport": "http",
"Url": "https://mcp.faultkey.com/mcp"
}
}
} assistant mcp add smq9sn5jck-coder-causallayer -t streamable-http -u 'https://mcp.faultkey.com/mcp'
{
"mcpServers": {
"smq9sn5jck-coder-causallayer": {
"type": "http",
"url": "https://mcp.faultkey.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.faultkey.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=faultkey.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f6e5acedf7ac414d0ebb9dc35221932e |
| SANs: faultkey.com, mcp.faultkey.com, *.mcp.faultkey.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.faultkey.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| faultkey.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.faultkey.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.faultkey.com/mcp | HTTPS enforced | 301 | https://mcp.faultkey.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
evaluate_prospective_response ~198
Deterministic prospective-evaluation gate (FK-METHOD-2026-006). Pass a ProposedAction BEFORE the agent delivers a response; receive one of three verdicts: 'allow', 'require_revision' (with specific factor-keyed directives), or 'block'. Uses the same four-factor engine that issues post-hoc certificates, so a single incident chains: prospective_pre_image -> response -> certificate -> anchor. This is a policy gate on structured action metadata, NOT a content safety classifier on raw prose. Thresholds are per-jurisdiction (EU strictest, US most permissive); read via GET /api/v2/gate/thresholds. Overrides are allowed but REQUIRE a governance rationale so the audit trail is complete. Cost: 1 credit. Pure deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | The structured ProposedAction to evaluate. |
| overrides | object | – | Optional per-call threshold override. Rationale REQUIRED for audit. |
No output schema declared.
No examples provided.
extract_incident ~198
Claude-powered structured extractor. Parses unstructured text (news articles, court filings, emails, PDFs, incident reports, logs) into the typed JSON schema required by submit_incident. Returns a ready-to-submit incident object with extracted agents, events, severity, jurisdiction, and financial impact. NOTE: This is a pre-processing convenience tool — the deterministic scoring engine itself remains LLM-free. Cost: 10 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| context_hint | string | – | Optional hint about the source type (e.g., 'court filing', 'news article', 'internal incident report') to improve extraction accuracy. |
| jurisdiction_hint | string | – | Optional ISO country code hint if the jurisdiction is known (e.g., 'AU', 'US', 'EU'). |
| text | string | yes | Unstructured text to extract from. Can be a news article, court filing, incident report, email, PDF text, log output, or any description of an AI incident. |
No output schema declared.
No examples provided.
get_anchor_status ~75
Return the index of all CausalLayer Tessera anchor batches, or one batch's full JSON (signed Merkle root, leaves, OpenTimestamps proof reference). FREE.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | – | Optional anchor version, e.g. '2026-05-16-v1.6.4-simulation-calibration'. |
No output schema declared.
No examples provided.
query_issuer_registry ~89
Return the CausalLayer issuer registry, or one issuer record. The registry lists all trusted public-key fingerprints, key algorithms, validity windows, and the anchor-log repo for each active issuer. FREE — no API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer_id | string | – | Optional issuer id, e.g. 'causallayer-prod-2026-q2'. If omitted, returns the full registry. |
No output schema declared.
No examples provided.
query_jurisdiction_overlay ~303
Multi-jurisdiction overlay (FK-METHOD-2026-004). Given a canonical attributable apportionment (party-id -> share), the union of all jurisdiction role tags on each actor, and the union of jurisdiction-specific flags, return side-by-side post-overlay shares for AU, EU, US, UK, CA (or a chosen subset) with the specific rules that fired in each, citation URLs, and a parties × jurisdictions matrix. v1 ships full implementations for AU and EU; US/UK/CA are research stubs marked `is_stub: true`. Use GET /api/v2/jurisdiction/catalog to discover support and stub status. Cost: 1 credit. Pure deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| actors | array | yes | All actors with the union of jurisdiction-specific role tags. EU and AU tags coexist on the same actor record. |
| attributable | object | yes | Canonical pre-overlay apportionment as { party_id: share }. Sum should approximate 1.0; the function renormalises within tolerance. |
| flags | object | yes | Union of jurisdiction-specific flags. AI Act / PLD flags drive the EU overlay; ACL / CPS 230 / VAISS flags drive the AU overlay. |
| jurisdictions | array | – | Optional subset to compute. Defaults to all five. |
| primaryJurisdiction | string | – | Engine-level jurisdiction string (e.g. 'EU', 'DE', 'AU'). Used by the EU gate to decide engagement. |
No output schema declared.
No examples provided.
simulate_remediation ~223
Counterfactual remediation simulator. Given a certificate's verdict + fourFactorScoring + agents and a list of remediation IDs from the FK-METHOD-2026-003 catalog, return the apportioned shares each remediation would have produced (in isolation) and the composite shares if they all stack. Every remediation cites a specific statute or standard. GET /api/v2/remediation/catalog for the list of IDs. Cost: 1 credit (same price as verify_certificate). Pure deterministic; same inputs produce a byte-identical result.
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | Agent registry (id + type) so the simulator can map remediation targetType to specific party ids. |
| fourFactorScoring | object | yes | The fourFactorScoring block from the CausalCertificate. |
| remediations | array | yes | List of remediation IDs from the catalog (e.g. vendor_adversarial_eval_suite, deployer_human_in_loop). Each may optionally pin appliedToParty to a specific agent id. |
| verdict | object | yes | The verdict block from the CausalCertificate. |
No output schema declared.
No examples provided.
submit_incident ~209
Submit an AI incident for deterministic causal liability attribution. Returns a signed CausalCertificate, per-agent liability allocation, evidence-chain completeness, regulatory mapping, and (where keys are configured) a Bitcoin-anchored proof. Cost: 50 credits. Three guardrails apply: PII scan, deterministic-only acknowledgement, and minimum evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | – |
| category | string | – | – |
| currency | string | – | – |
| description | string | – | – |
| deterministic_only | boolean | yes | G2: Must be true. Acknowledges CausalLayer is deterministic and not LLM-based. |
| events | array | yes | – |
| financial_impact_cents | – | – | – |
| jurisdiction | string | – | – |
| pii_acknowledged | boolean | – | G1: Set to true ONLY if caller has confirmed PII handling is permitted by their data agreement. False payloads with detected PII will be rejected. |
| severity | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
submit_otel_trace ~244
Convert an OpenTelemetry OTLP JSON trace into a FaultKey incident and return the same deterministic CausalCertificate as submit_incident. Each span becomes an event; service.name groups spans into agents; W3C trace_id and span_id propagate as evidence pointers on the causal graph edges. Cost: 50 credits (same as submit_incident). Three guardrails apply: PII scan, deterministic-only acknowledgement, and minimum evidence (auto-satisfied when the trace has at least 1 span).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| currency | string | – | – |
| deterministic_only | boolean | yes | G2: Must be true. Acknowledges CausalLayer is deterministic. |
| financial_impact_cents | – | – | – |
| jurisdiction | string | – | – |
| otlp | object | yes | OTLP JSON payload with resourceSpans[]. See https://opentelemetry.io/docs/specs/otlp/#json-protobuf-encoding |
| pii_acknowledged | boolean | – | G1: Set to true ONLY if PII handling is permitted by your data agreement. OTLP traces frequently leak user/session ids in attributes. |
| title | string | yes | – |
No output schema declared.
No examples provided.
verify_certificate ~71
Independently verify a CausalCertificate end-to-end (signature, Merkle integrity, issuer status against the registry). Cost: 1 credit. In production env, certificates from non-active issuers are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate | object | yes | CausalCertificateV1 object as returned by submit_incident.certificate |
No output schema declared.
No examples provided.
verify_certificate_recompute ~159
Independently re-derive a CausalCertificate from its canonical input and compare byte-for-byte against the claimed certificate. This is the strongest verification path: it requires no trust in the issuer or signing key. Cost: 1 credit (same price as verify_certificate). Returns PASS only if every checked field (certificateId, request_hash, merkleRoot, verdict, causalGraph, fourFactorScoring, deviationTaxonomy, euRuleOverlay, cascadeAttenuation, damages, underwriting) matches identically.
| Name | Type | Req | Description |
|---|---|---|---|
| canonicalInput | object | yes | The original incident body that produced the certificate — the same JSON originally posted to submit_incident or submit_otel_trace. |
| certificate | object | yes | The CausalCertificate object claimed by the issuer. |
No output schema declared.
No examples provided.
What is the CausalLayer MCP server?
CausalLayer MCP is listed in the public MCP registry as io.github.smq9sn5jck-coder/causallayer. Deterministic AI liability attribution with Bitcoin-anchored proof certificates. This page covers its hosted endpoint (https://mcp.faultkey.com/mcp).
Is the CausalLayer MCP server safe to use?
CausalLayer MCP scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CausalLayer MCP server expose?
CausalLayer MCP exposes 10 tools: submit_incident, verify_certificate, verify_certificate_recompute, submit_otel_trace, simulate_remediation, and 5 more. Their descriptions and schemas cost roughly 1,769 tokens of context every time the server is loaded.
Does the CausalLayer MCP server require authentication?
No. We connected to CausalLayer MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CausalLayer MCP server still maintained?
CausalLayer MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.