DarkMatter runs on your own machine — the client starts it, so there is no endpoint to ping. 26 installs a week from npm. Last commit 23 Sep 2026.
Tamper-evident records of AI agent decisions. Verify offline, or publish a proof link.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const dir = path.join(ROOT, sessionId);
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Update status
env:
TOKEN: ${{ steps.auth.outputs.token }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add verifiable-agent-audit-trail -- npx -y @darkmatterhub/mcp-server
{
"mcpServers": {
"verifiable-agent-audit-trail": {
"command": "npx",
"args": [
"-y",
"@darkmatterhub/mcp-server"
]
}
}
}
[mcp_servers.verifiable-agent-audit-trail]
command = "npx"
args = ["-y", "@darkmatterhub/mcp-server"]
{
"mcpServers": {
"verifiable-agent-audit-trail": {
"command": "npx",
"args": [
"-y",
"@darkmatterhub/mcp-server"
]
}
}
}
{
"servers": {
"verifiable-agent-audit-trail": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@darkmatterhub/mcp-server"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
DARKMATTER_API_KEY (Optional. Publishes each record to DarkMatter and returns a verification URL. Without it, records stay on local disk and verify offline), DARKMATTER_SHARE (Optional. Set to 'true' to make published records readable by anyone holding the link. Off by default), DARKMATTER_API_URL (Optional. Override the API host. Defaults to https://darkmatterhub.ai), DARKMATTER_MCP_STORE_DIR (Optional. Directory for local record storage).
Attest agent decisions and verify records on a public ledger. Evidence, not just data.
Record AI decisions to a tamper-evident audit ledger from any MCP-compatible agent.
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
Signed, publicly logged records of what your AI agent did, with proofs anyone can check offline.
Record an agent's decisions with reasons anyone can re-execute offline — verify recomputes them.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
Read, verify and export a tamper-evident log of what an AI agent did. Read-only.
Answers built from our own checks of this server.