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

DarkMatter

NPM · @DARKMATTERHUB/MCP-SERVER · SCANNED SEP 20

Tamper-evident records of AI agent decisions. Verify offline, or publish a proof link.

0 this week 82 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 469 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the DarkMatter MCP server?

DarkMatter runs locally as an npm package, launched with npx -y @darkmatterhub/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @darkmatterhub/mcp-server

# add to Claude Code
claude mcp add darkmatter-hub-mcp-server -- npx -y @darkmatterhub/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "darkmatter-hub-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@darkmatterhub/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "darkmatter-hub-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@darkmatterhub/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add darkmatter-hub-mcp-server -- npx -y @darkmatterhub/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "darkmatter-hub-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@darkmatterhub/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add darkmatter-hub-mcp-server --command npx --arg -y --arg @darkmatterhub/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  darkmatter-hub-mcp-server:
    command: "npx"
    args: ["-y", "@darkmatterhub/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "darkmatter-hub-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@darkmatterhub/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add darkmatter-hub-mcp-server -t stdio -c npx -a -y @darkmatterhub/mcp-server
// mcp.json
{
  "mcpServers": {
    "darkmatter-hub-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@darkmatterhub/mcp-server"
      ]
    }
  }
}
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.

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

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

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 20 Sept 2026 · Analysed npm/@darkmatterhub/mcp-server@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~469 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
darkmatter_commit ~261

Commit a Context Passport record of an agent decision or action. Returns a verifiable record id and verify_url. Use this when the agent makes a decision worth recording for later audit or verification.

NameTypeReqDescription
agent_idstringOptional. Identifier for the calling agent.
agent_namestringOptional. Human-readable agent name.
event_typestringOptional. One of: commit, fork, checkpoint, spawn, retry, timeout, error, override, consent, escalate, redact, audit. Defaults to 'commit'.
inputWhat the agent received (string or object).
memoryobjectOptional. Persistent state / tool results.
modelstringOptional. Model name.
outputWhat the agent produced (string or object).
providerstringOptional. LLM provider (anthropic, openai, mistral, etc).
rolestringOptional. Semantic role (researcher, writer, reviewer, etc).
session_idstringOptional. Groups passports into a chain. Defaults to 'default'.
trace_idstringOptional. Groups commits into a pipeline run.
variablesobjectOptional. Named values for downstream agents.

No output schema declared.

No examples provided.

darkmatter_export ~54

Export a portable JSON bundle of the entire chain for a session. The bundle is self-contained and can be verified by any third party without contacting DarkMatter.

NameTypeReqDescription
session_idstringOptional. Defaults to 'default'.

No output schema declared.

No examples provided.

darkmatter_list_sessions ~26

List all session ids that have at least one committed Context Passport in local storage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

darkmatter_replay ~60

Walk the Context Passport chain for a session and return the full payload at each step in chronological order.

NameTypeReqDescription
idstringOptional. Replay up to this passport id only.
session_idstringOptional. Defaults to 'default'.

No output schema declared.

No examples provided.

darkmatter_verify ~68

Verify the integrity of the Context Passport chain for a session. Returns true if the hash chain is intact and no records have been tampered with.

NameTypeReqDescription
idstringOptional. Verify up to this passport id only.
session_idstringOptional. Defaults to 'default'.

No output schema declared.

No examples provided.

Common questions

What is the DarkMatter MCP server?

DarkMatter is an MCP server listed in the public MCP registry as io.github.darkmatter-hub/mcp-server. Tamper-evident records of AI agent decisions. Verify offline, or publish a proof link. This page covers its npm package (@darkmatterhub/mcp-server).

Is the DarkMatter MCP server safe to use?

DarkMatter scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DarkMatter MCP server expose?

DarkMatter exposes 5 tools: darkmatter_commit, darkmatter_verify, darkmatter_replay, darkmatter_export, darkmatter_list_sessions. Their descriptions and schemas cost roughly 469 tokens of context every time the server is loaded.

Is the DarkMatter MCP server still maintained?

DarkMatter is marked deprecated in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the DarkMatter MCP server under?

DarkMatter declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.