TollWire Evidence

Name: TollWire Evidence
Author: TollWire

by TollWireversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.TollWire/evidence-mcp

Install

Overview

Description from the maker (original English)

Tamper-evident evidence log of agent changes, scans and approvals, mapped to ISO 27001/NIS2.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 615/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "evidence": {
      "command": "npx",
      "args": [
        "-y",
        "@tollwire/evidence-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add evidence -- npx -y @tollwire/evidence-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "evidence": {
      "command": "npx",
      "args": [
        "-y",
        "@tollwire/evidence-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "evidence": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tollwire/evidence-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account TollWire, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18474 servers in this category
Published to the registry more recently than 97% of the other 18474 servers in this category
Basic checks equal to or better than 100% of the other 18474 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is TollWire Evidence safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Brontide agent arena

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

Brontide agent arena

THE MECH ARENA BUILT FOR AI AGENTS. HUMANS WELCOME. Pilot mech duels over MCP, free, no sign-in.

by beeswaxpatVery newUpdated today

Runs in the cloud✓ brontide.live

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

TollWire Evidence MCP (`tollwire-evidence`, MVP)

MCP server that records agent changes, reviews, scans, approvals, deployments, incidents and permission changes as a tamper-evident hash chain. It maps event types to ISO/IEC 27001:2022 Annex A and NIS2 Article 21(2) controls (draft).

Status: version 0.x (MVP). Interfaces can change incompatibly before 1.0. Installation, the marketplace and npm options, and the project-wide security notes are in the top-level README. Issues are welcome; pull requests from third parties are not accepted, see CONTRIBUTING.md.

Tools

Tool	Purpose
`record_event`	Append an event. Events that contain a recognized secret format are refused. Type `anchor` is accepted only with a matching anchor (see below).
`list_events`	Read events, optionally filtered by type.
`verify_log`	Check the hash chain. Also checks the local anchor file (if present) and any external anchors passed in `anchors`.
`create_anchor`	Write the last entry as an anchor `{seq, hash, ts, count}` to the anchor file. Returns the anchor line, a tag name and a suggested signed Git tag command. Writes no event.
`map_controls`	Map event types to controls (draft, not confirmed by an auditor).
`export_report`	Markdown evidence report with integrity and coverage.

Storage

Log: TOLLGATE_EVIDENCE_LOG if set; otherwise .tollgate/evidence/log.jsonl in the project directory (CLAUDE_PROJECT_DIR, or the current directory).
Anchor file: .anchors.jsonl in the same directory. Append-only. Each line carries prev_anchor_hash and anchor_hash, so the anchor file is itself tamper-evident.
Lock: a lock file next to the log.
Permissions: files are created with mode 0600.
Path: every path component between the root and the log must be a real directory, not a symbolic link. Otherwise all tools that access files refuse to work. The root itself may be reached through a link.
Files: log and anchor file must be regular files with exactly one directory entry. Symbolic links and hard links are refused. Checks are repeated on the opened file descriptor.
Errors: tool error responses contain no stack trace and no file paths. Unexpected errors are reported generically.

External anchors

An anchor records the sequence number, hash, timestamp and count of the last entry in canonical JSON, for example {"count":42,"hash":"…","seq":42,"ts":"2026-10-04T08:00:00.000Z"}.

verify_log checks, besides the chain, that for each anchor an entry with that seq exists and carries exactly that hash and timestamp. A log that was rewritten after the anchor (a new, internally valid chain) or truncated is then detected.

valid means only "internally consistent".
anchored is true only if the result is valid and at least one external anchor was confirmed. valid: true with anchored: false is not proof that the log is unchanged.
A local anchor file does not protect against someone who rewrites or deletes the log and the anchor file together. An anchor is effective only when it is stored outside the machine.

Recommended procedure, performed by a person with their own signing key:

create_anchor (or node scripts/anchor.mjs create in the package directory).
Store the anchor outside the machine, for example as a signed Git tag. The tools never sign anything.
Record an anchor event with node scripts/anchor.mjs record ' ' signed_tag . Exit code 0: recorded. Exit code 2: refused.

Verification: git tag -v checks the signature. Then pass the anchor line from the tag message to verify_log (anchors), or run node scripts/anchor.mjs verify ' ' (exit 0 valid, 1 finding, 2 usage error).

`anchor` events

An anchor event documents that a person stored an anchor outside the machine. The control mapping is a draft (ISO/IEC 27001:2022 A.8.15, A.5.33, A.5.28; NIS2 Article 21(2)(f)).

Order: create_anchor, then the external storage, then the anchor event. Recording the event before storage would document a storage that has not happened yet.
The event carries ref (tag name or comment URL), details.anchor (the stored anchor) and details.storage (signed_tag or digest_comment).
The anchor must match the log: the entry at seq must have the same hash and timestamp. This is checked under the lock. Otherwise nothing is written.
The tool checks that the anchor matches the log. It does not check that the external storage happened, who stored it, or that ref points to a real storage location. Only the signed tag or comment itself is evidence of that.

Self-declared fields

The hash chain shows that the log is internally consistent. It does not show who wrote an entry.

actor is free text supplied by the caller. The server does not check identity. Any process that may write the log can record any actor, including the name of a person.
An anchor event is also self-declared. Only the external storage itself is evidence.
For reviewers, anchors in signed tags count, not anchor events in the log.

Secret filter

record_event refuses events whose content matches a known credential format: private keys (PEM, OpenSSH, PGP), GitHub, GitLab and npm tokens, AWS access keys, Anthropic and OpenAI keys (sk-…), Stripe keys (sk_live_, sk_test_, rk_…), Google API keys (AIza…), signed JWTs, Slack tokens and Slack webhook URLs. Only formats with a fixed prefix are recognized, which keeps false positives low. Unknown formats and freely chosen passwords are not detected. Do not put secrets into events.

Package contents

The files field of package.json includes dist/, .claude-plugin/, .mcp.json, scripts/anchor.mjs, LICENSE and README.md. Source code, tests, coverage and the smoke test are not shipped. Run npm run build before packing, so that no stale files are included.

Limits

The hash chain detects changes; it does not prevent them. Whoever rewrites the whole file can create a new valid chain.
External anchors detect this only for entries up to the last externally stored anchor, and only when the anchors are passed to verify_log. Entries after the last anchor are not protected.
Signing each entry and automated external storage are not implemented.
The control mapping has not been confirmed by an auditor and is not evidence of conformity with ISO/IEC 27001 or NIS2.
The server makes no network requests.

Development

npm ci --ignore-scripts

npm run check # typecheck, lint, tests with coverage, build, smoke test

Node.js 22.12.0 or later is required (engines). Runtime dependency: zod only, pinned to an exact version.

Dependencies and security: the MCP server is a small built-in implementation (src/vendor/mcpStdio.ts): JSON-RPC 2.0 over stdin/stdout, one message per line, protocol versions as in the official SDK 1.32.0 (latest 2025-11-25). It opens no network connection, rejects lines over 1 MiB (the session ends with exit code 1) and the key __proto__, and writes diagnostics to stderr only. The official @modelcontextprotocol/sdk is a development dependency only: scripts/sdkCompat.mjs (part of npm run smoke) connects its Client with StdioClientTransport to the built server and calls every tool. The SDK and its HTTP stack are not installed with the package.

License

Source-available under the PolyForm Noncommercial License 1.0.0 (SPDX: PolyForm-Noncommercial-1.0.0), see also NOTICE. Noncommercial use only; commercial use requires prior written permission. Details: LEGAL.md.

TollWire Evidence

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Brontide agent arena

README from the maker

TollWire Evidence MCP (tollwire-evidence, MVP)

Tools

Storage

External anchors

anchor events

Self-declared fields

Secret filter

Package contents

Limits

Development

License

TollWire Evidence MCP (`tollwire-evidence`, MVP)

`anchor` events