Skip to content

CausalLayer MCP

by smq9sn5jck-coder · remote · local (npm) · no sign-in to list tools · v0.4.0 · published by GitHub user smq9sn5jck-coder

Deterministic AI liability attribution with Bitcoin-anchored proof certificates.

Changes · 7
CompareRegistry entry

10 tools: 7 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http causallayer https://mcp.faultkey.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

10 tools

Changes things 7Claude Code: ask
  • evaluate_prospective_responseDeterministic prospective-evaluation gate (FK-METHOD-2026-006).No findings

    Why it is in this group

    • The name "evaluate_prospective_response" says "evaluate": a word for a change.
    Description, as the server wrote it
    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.
  • extract_incidentClaude-powered structured extractor.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • simulate_remediationCounterfactual remediation simulator.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • submit_incidentSubmit an AI incident for deterministic causal liability attribution.No findings

    Why it is in this group

    • The name "submit_incident" says "submit": a word for a change.
    Description, as the server wrote it
    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.
  • submit_otel_traceConvert an OpenTelemetry OTLP JSON trace into a FaultKey incident and return the same deterministic CausalCertificate as submit_incident.No findings

    Why it is in this group

    • The name "submit_otel_trace" says "submit": a word for a change.
    Description, as the server wrote it
    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).
  • verify_certificateIndependently verify a CausalCertificate end-to-end (signature, Merkle integrity, issuer status against the registry).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_certificate_recomputeIndependently re-derive a CausalCertificate from its canonical input and compare byte-for-byte against the claimed certificate.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 3Claude Code: allow
  • get_anchor_statusReturn the index of all CausalLayer Tessera anchor batches, or one batch's full JSON (signed Merkle root, leaves, OpenTimestamps proof reference).No findings

    Why it is in this group

    • The name "get_anchor_status" says "get": a word for reading.
    Description, as the server wrote it
    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_registryReturn the CausalLayer issuer registry, or one issuer record.No findings

    Why it is in this group

    • The name "query_issuer_registry" says "query": a word for reading.
    Description, as the server wrote it
    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.
  • query_jurisdiction_overlayMulti-jurisdiction overlay (FK-METHOD-2026-004).No findings

    Why it is in this group

    • The name "query_jurisdiction_overlay" says "query": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http causallayer https://mcp.faultkey.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__causallayer__query_jurisdiction_overlay",
      "mcp__causallayer__get_anchor_status",
      "mcp__causallayer__query_issuer_registry"
    ],
    "ask": [
      "mcp__causallayer__submit_incident",
      "mcp__causallayer__verify_certificate",
      "mcp__causallayer__verify_certificate_recompute",
      "mcp__causallayer__submit_otel_trace",
      "mcp__causallayer__simulate_remediation",
      "mcp__causallayer__evaluate_prospective_response",
      "mcp__causallayer__extract_incident"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as causallayer. Review it before you use it.