Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

FaultKey · CausalLayer

REMOTE · CAUSALLAYER-MCP-DEMO.ZYKM9QKK7J.WORKERS.DEV · SCANNED AUG 3

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

+3 this week 57 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability55
  • 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · causallayer-mcp-demo.zykm9qkk7j.workers.dev

# add to Claude Code
claude mcp add --transport http smq9sn5jck-cloud-causallayer-mcp https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp
# ~/.codex/config.toml
[mcp_servers.smq9sn5jck-cloud-causallayer-mcp]
url = "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smq9sn5jck-cloud-causallayer-mcp": {
      "type": "remote",
      "url": "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add smq9sn5jck-cloud-causallayer-mcp --url https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  smq9sn5jck-cloud-causallayer-mcp:
    url: "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "smq9sn5jck-cloud-causallayer-mcp": {
      "type": "http",
      "url": "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 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 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 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
  • 26 Jul 26 53

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zykm9qkk7j.workers.dev CN=YE2,O=Let's Encrypt,C=US 13 Jul 2026 11 Oct 2026 ECDSA 256 ECDSA-SHA384 557f1b4487ceb2b20791a4e8a794ee2cf0d
SANs: *.zykm9qkk7j.workers.dev, zykm9qkk7j.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of causallayer-mcp-demo.zykm9qkk7j.workers.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. 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
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp Verified 200
http (plaintext) http://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp Inconclusive 406
MCP tools — 10 exposed · ~1,769 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
actionobjectyesThe structured ProposedAction to evaluate.
overridesobjectOptional 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.

NameTypeReqDescription
context_hintstringOptional hint about the source type (e.g., 'court filing', 'news article', 'internal incident report') to improve extraction accuracy.
jurisdiction_hintstringOptional ISO country code hint if the jurisdiction is known (e.g., 'AU', 'US', 'EU').
textstringyesUnstructured 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.

NameTypeReqDescription
versionstringOptional 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.

NameTypeReqDescription
issuer_idstringOptional 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.

NameTypeReqDescription
actorsarrayyesAll actors with the union of jurisdiction-specific role tags. EU and AU tags coexist on the same actor record.
attributableobjectyesCanonical pre-overlay apportionment as { party_id: share }. Sum should approximate 1.0; the function renormalises within tolerance.
flagsobjectyesUnion of jurisdiction-specific flags. AI Act / PLD flags drive the EU overlay; ACL / CPS 230 / VAISS flags drive the AU overlay.
jurisdictionsarrayOptional subset to compute. Defaults to all five.
primaryJurisdictionstringEngine-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.

NameTypeReqDescription
agentsarrayyesAgent registry (id + type) so the simulator can map remediation targetType to specific party ids.
fourFactorScoringobjectyesThe fourFactorScoring block from the CausalCertificate.
remediationsarrayyesList 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.
verdictobjectyesThe 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.

NameTypeReqDescription
agentsarrayyes
categorystring
currencystring
descriptionstring
deterministic_onlybooleanyesG2: Must be true. Acknowledges CausalLayer is deterministic and not LLM-based.
eventsarrayyes
financial_impact_cents
jurisdictionstring
pii_acknowledgedbooleanG1: Set to true ONLY if caller has confirmed PII handling is permitted by their data agreement. False payloads with detected PII will be rejected.
severitystring
titlestringyes

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).

NameTypeReqDescription
categorystring
currencystring
deterministic_onlybooleanyesG2: Must be true. Acknowledges CausalLayer is deterministic.
financial_impact_cents
jurisdictionstring
otlpobjectyesOTLP JSON payload with resourceSpans[]. See https://opentelemetry.io/docs/specs/otlp/#json-protobuf-encoding
pii_acknowledgedbooleanG1: Set to true ONLY if PII handling is permitted by your data agreement. OTLP traces frequently leak user/session ids in attributes.
titlestringyes

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.

NameTypeReqDescription
certificateobjectyesCausalCertificateV1 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.

NameTypeReqDescription
canonicalInputobjectyesThe original incident body that produced the certificate — the same JSON originally posted to submit_incident or submit_otel_trace.
certificateobjectyesThe CausalCertificate object claimed by the issuer.

No output schema declared.

No examples provided.