SERVER

FaultKey · CausalLayer

Rank #78,989

io.github.smq9sn5jck-cloud/causallayer-mcp

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

1 version

3 GitHub stars

by smq9sn5jck-coder (3 servers)View repository ↗

Listed & last published

May 16, 2026

PURPOSE

What you can do with FaultKey · CausalLayer

FaultKey · CausalLayer is a Model Context Protocol (MCP) server published by smq9sn5jck-coder. It ranks #78,989 of 168,415 active servers on MCP Toplist, and its repository has 3 GitHub stars. FaultKey · CausalLayer is listed across 3 registries — Official MCP, PulseMCP and Glama, with 1 tracked version. It was first listed on May 16, 2026 and most recently updated on May 16, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.

CAPABILITIES AND LIMITATIONS

What FaultKey · CausalLayer can and cannot do

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.

REQUIREMENTS

What you need before using FaultKey · CausalLayer

DeclaredNo credentialsNo credentials declared

The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.

MCP Toplist probed the public endpoint on Oct 25, 2026 and could not complete the MCP handshake (jsonrpc error). Requirements remain unverified.

Declared by the Official MCP Registry, last synced Nov 4, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

Hosted endpoint declared as public.

INSTALLATION AND FIRST TASK

Connect FaultKey · CausalLayer and confirm it works

Remote · HTTP

claude mcp add --transport http causallayer-mcp https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp

Remote · HTTP

[mcp_servers.causallayer-mcp]
url = "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"

Add to ~/.codex/config.toml.

Remote · HTTP

https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp

Settings → Connectors → “Add custom connector”, then paste this URL.

Remote · HTTP

{
  "mcpServers": {
    "causallayer-mcp": {
      "url": "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).

Remote · HTTP

{
  "servers": {
    "causallayer-mcp": {
      "type": "http",
      "url": "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
    }
  }
}

Save as .vscode/mcp.json in your workspace.

Remote · HTTP

{
  "mcpServers": {
    "causallayer-mcp": {
      "serverUrl": "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

Remote · HTTP

{
  "mcpServers": {
    "causallayer-mcp": {
      "url": "https://causallayer-mcp-demo.zykm9qkk7j.workers.dev/mcp"
    }
  }
}

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: May 16, 2026
Latest version published: May 16, 2026
Version history: 1 version tracked (below)
Requirements evidence: MCP Toplist probed the public endpoint on Oct 25, 2026 and could not complete the MCP handshake (jsonrpc error). Requirements remain unverified.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Aug 31, 2026

Registry sightings

Official MCP ↗listed since May 16, 2026 · still listed
PulseMCP ↗listed since Jun 4, 2026 · delisted, last seen Jun 4, 2026
Glama ↗listed since Jun 4, 2026 · delisted, last seen Jun 4, 2026

Do you maintain FaultKey · CausalLayer? to correct or enrich this profile.

VERSIONS

Available versions (1)

Version	Published
0.2.0	May 16, 2026

STANDING

#78,989of 168,415 active serversTop 50%

Ranks ahead of 89,426 of 168,415 servers on MCP Toplist.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.smq9sn5jck-cloud%2Fcausallayer-mcp.svg)](https://mcptoplist.com/server/io.github.smq9sn5jck-cloud%2Fcausallayer-mcp)

HTML

<a href="https://mcptoplist.com/server/io.github.smq9sn5jck-cloud%2Fcausallayer-mcp"><img src="https://mcptoplist.com/badge/io.github.smq9sn5jck-cloud%2Fcausallayer-mcp.svg" alt="MCP Toplist: Top 50% of 168,415" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Who maintains FaultKey · CausalLayer?: FaultKey · CausalLayer is maintained by smq9sn5jck-coder, which publishes 3 MCP servers (2 total versions) tracked on MCP Toplist.
Is FaultKey · CausalLayer listed on the Official MCP Registry?: Yes — FaultKey · CausalLayer is listed on the Official MCP Registry, alongside PulseMCP and Glama.
How many versions does FaultKey · CausalLayer have?: MCP Toplist tracks 1 version of FaultKey · CausalLayer, most recently published on May 16, 2026.
Where can I find the source code for FaultKey · CausalLayer?: The source code for FaultKey · CausalLayer is hosted at github.com/smq9sn5jck-coder/causallayer-mcp.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers