DarkMatter MCP Server
OfficialThe DarkMatter MCP Server lets you create and manage tamper-evident, verifiable audit trails of AI agent decisions and actions using Context Passport records.
darkmatter_commit— Record an agent's input, output, and metadata (role, model, provider, agent identity, trace ID, event type, etc.), creating a hash-chained, tamper-evident Context Passport.darkmatter_verify— Check the integrity of a session's hash chain, either in full or up to a specific passport ID, to detect tampering.darkmatter_replay— Walk through all committed records for a session in chronological order, retrieving full payloads.darkmatter_export— Produce a self-contained JSON bundle of an entire session's chain for third-party verification without external dependencies.darkmatter_list_sessions— List all session IDs that have at least one Context Passport stored locally.
Records are stored locally by default, with an option to forward them asynchronously to a DarkMatter receiving server. The server integrates with MCP-compatible clients (e.g., Claude Code, Cursor, ChatGPT Desktop) and supports auto-capture adapters for recording every tool call and turn boundary automatically.
Planned auto-capture integration for OpenAI Codex to record all agent decisions and actions as Context Passport records.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DarkMatter MCP ServerRecord approval for refund order #1247"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DarkMatter MCP Server
Universal MCP server that emits Context Passport records for AI agent decisions and actions. Drop into any MCP-compatible client (Claude Code, Cursor, Cline, Continue, ChatGPT Desktop, Zed, Goose, and others) to give your agent a commit / verify / replay / export toolset for verifiable, tamper-evident records.
Built by DarkMatter. Implements Context Passport v2.0, an open CC0 standard. Records emitted by this server use RFC 8785 (JCS) canonicalization and are byte-equivalent across the Python and TypeScript reference SDKs.
Install
In your MCP client's config (claude_desktop_config.json, Cursor's mcp.json, etc.):
{
"mcpServers": {
"darkmatter": {
"command": "npx",
"args": ["-y", "@darkmatterhub/mcp-server"]
}
}
}Restart the client. Five tools become available to your agent:
darkmatter_commit— record an agent decision or actiondarkmatter_verify— check that the chain has not been tampered withdarkmatter_replay— walk the full chain in orderdarkmatter_export— produce a portable proof bundledarkmatter_list_sessions— see what sessions exist locally
Related MCP server: @citizenofthecloud/mcp-server
What gets captured
Whatever the agent (or user) explicitly invokes via darkmatter_commit. Auto-capture of every tool call without explicit invocation is a separate component (see Auto-capture below).
Example agent flow:
User: Approve the refund for order #1247 and record the decision.
Agent: Calls refund_order(1247).
Agent: Calls darkmatter_commit({
input: "Approve refund for order #1247",
output: "Approved. $84.00 refunded to original payment method.",
role: "compliance",
event_type: "commit"
})
Result: { ok: true, passport: {...}, verify_url: "https://darkmatterhub.ai/r/ctx_..." }The passport is signed (if a key is configured), hash-chained to the previous commit in the session, and stored locally at ~/.darkmatter/mcp/<session_id>/chain.jsonl.
Storage
Default: local-only. Passports never leave the machine.
~/.darkmatter/mcp/
├── default/
│ ├── chain.jsonl # append-only stream of all commits
│ └── latest.json # most recent passport (used as parent for the next)
└── <other-session-id>/
└── ...To forward each passport to a DarkMatter receiving server in addition to local storage, set:
export DARKMATTER_API_KEY="dm_sk_..."The forwarding is best-effort and never blocks the agent's tool call. Local storage remains the source of truth.
Auto-capture
The MCP server captures only what the agent explicitly invokes. To auto-capture every tool call and turn boundary in a specific dev tool (without the agent having to remember to call darkmatter_commit), install one of the dev-tool-specific adapters:
darkmatter-hub/claude-code — auto-capture for Claude Code (Anthropic)
Cursor adapter — planned
OpenAI Codex adapter — planned
Aider adapter — community-built welcome
Each adapter hooks into its specific dev tool's event lifecycle and routes events through this MCP server's darkmatter_commit tool. One canonical endpoint, many capture surfaces.
Verification
Records are valid Context Passport v2.0 artifacts. Verify with any conformant implementation:
pip install context-passport context-passport-conformance
context-passport-conformance --level signed # 9/9 vectors, no --vectors-dir neededThe conformance package ships its vectors inside the wheel, so this is a one-line check against the public reference suite.
Or use the offline reference verifier directly on the JSONL file:
import json
from context_passport import verify_chain
with open("~/.darkmatter/mcp/default/chain.jsonl") as f:
chain = [json.loads(line) for line in f]
print(verify_chain(chain)) # True if intact, False if tamperedWhy MCP
MCP (Model Context Protocol) is becoming the universal interop layer for AI tools. Writing this server once means it works in every MCP-compatible client without per-client integration code. See the Context Passport for MCP proposal for the broader architectural rationale.
License
Apache-2.0. See LICENSE.
The Context Passport schema this server implements is released separately under CC0 1.0 at github.com/contextpassport/spec.
Related repositories
github.com/contextpassport/spec — the open standard
github.com/contextpassport/python — Python reference SDK
github.com/contextpassport/typescript — TypeScript reference SDK
github.com/darkmatter-hub/claude-code — auto-capture for Claude Code
github.com/darkmatter-hub/darkmatter — DarkMatter receiving server
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/darkmatter-hub/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server