Local MCP capabilities provider for Expo
Nothing to run from here
FaultKey · CausalLayer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
5
downloads a day
remote
at its publisher
198
downloads in 30d
What it does
Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http faultkey-causallayer-mcp https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp
# 2 — ask your agent for something these tools do
# submit_incident, verify_certificate, verify_certificate_recompute and 7 more
FaultKey · CausalLayer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SCAll 1 server
smq9sn5jck-cloud1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http faultkey-causallayer-mcp https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| description | string | no | — |
| category | string | no | — |
| severity | string | no | — |
| jurisdiction | string | no | — |
| financial_impact_cents | no | — | |
| currency | string | no | — |
| agents | array | yes | — |
| events | array | yes | — |
| deterministic_only | boolean | yes | G2: Must be true. Acknowledges CausalLayer is deterministic and not LLM-based. |
| pii_acknowledged | boolean | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| certificate | object | yes | CausalCertificateV1 object as returned by submit_incident.certificate |
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, devia
| Parameter | Type | Required | Notes |
|---|---|---|---|
| certificate | object | yes | The CausalCertificate object claimed by the issuer. |
| canonicalInput | object | yes | The original incident body that produced the certificate — the same JSON originally posted to submit_incident or 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 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| otlp | object | yes | OTLP JSON payload with resourceSpans[]. See https://opentelemetry.io/docs/specs/otlp/#json-protobuf-encoding |
| category | string | no | — |
| jurisdiction | string | no | — |
| financial_impact_cents | no | — | |
| currency | string | no | — |
| deterministic_only | boolean | yes | G2: Must be true. Acknowledges CausalLayer is deterministic. |
| pii_acknowledged | boolean | no | G1: Set to true ONLY if PII handling is permitted by your data agreement. OTLP traces frequently leak user/session ids in attributes. |
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. C
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verdict | object | yes | The verdict block from the CausalCertificate. |
| fourFactorScoring | object | yes | The fourFactorScoring block from the CausalCertificate. |
| agents | array | yes | Agent registry (id + type) so the simulator can map remediation targetType to specific party ids. |
| 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attributable | object | yes | Canonical pre-overlay apportionment as { party_id: share }. Sum should approximate 1.0; the function renormalises within tolerance. |
| actors | array | yes | All actors with the union of jurisdiction-specific role tags. EU and AU tags coexist on the same actor record. |
| 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 | no | Optional subset to compute. Defaults to all five. |
| primaryJurisdiction | string | no | Engine-level jurisdiction string (e.g. 'EU', 'DE', 'AU'). Used by the EU gate to decide engagement. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | object | yes | The structured ProposedAction to evaluate. |
| overrides | object | no | Optional per-call threshold override. Rationale REQUIRED for audit. |
Return the index of all CausalLayer Tessera anchor batches, or one batch's full JSON (signed Merkle root, leaves, OpenTimestamps proof reference). FREE.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Optional anchor version, e.g. '2026-05-16-v1.6.4-simulation-calibration'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issuer_id | string | no | Optional issuer id, e.g. 'causallayer-prod-2026-q2'. If omitted, returns the full registry. |
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 rema
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| context_hint | string | no | Optional hint about the source type (e.g., 'court filing', 'news article', 'internal incident report') to improve extraction accuracy. |
| jurisdiction_hint | string | no | Optional ISO country code hint if the jurisdiction is known (e.g., 'AU', 'US', 'EU'). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FaultKey · CausalLayer or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.4.0 · scanned 6 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest6dbd4716f41b105d117450a4e796797d5655b584f10e1802c84990d6032c8a33
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6dbd4716f41b105d
Scanned2026-10-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
0.4.0
30 May 2026
latestNo release note was published with this version.
0.2.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish FaultKey · CausalLayer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.