mcpbeat Sign in

Tersign Evidence MCP Server

by tersignhq Your server? Claim it
local only

Tersign Evidence runs on your own machine — the client starts it, so there is no endpoint to ping. 472 installs a week from npm. Last commit 27 Oct 2026.

The record layer for the machine age: counter-signed receipts and agent action records.

Installs per day peak 241 · avg 59 · -31% w/w
a month agotoday
472
Installs / week
npm · tersign
1
Stars
0 open issues
27 Oct 2026
Last commit
23 releases in 90 days
Apache-2.0
License
TypeScript

What the code does

We read the source, 5 d ago · rules 995398eba69f

Capabilities

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.

Runs an external command src/intercept/proxy.ts:35
  const child = spawn(opts.command, [...opts.args], { stdio: ['pipe', 'pipe', opts.stderr] });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

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.

Three servers free · no card

Connect this server

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.

run in your terminal
claude mcp add evidence -- npx -y tersign
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "evidence": {
      "command": "npx",
      "args": [
        "-y",
        "tersign"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.evidence]
command = "npx"
args = ["-y", "tersign"]
.cursor/mcp.json
{
  "mcpServers": {
    "evidence": {
      "command": "npx",
      "args": [
        "-y",
        "tersign"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "evidence": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tersign"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TERSIGN_SELLER_KEY (Optional: your own 0x-prefixed signing key. Unset or empty, the server uses the key in the macOS keychain (tersign-signer) or ~/.tersign/signer.key, and generates one there on first run. The key never leaves your machine. If your ledger account has a registered signing key, set that key here: the ledger rejects respondent dispute evidence signed by any other key), TERSIGN_ISSUER_NAME (Seller/issuer display name), TERSIGN_ISSUER_JURISDICTION (Seller jurisdiction (e.g. HK)), TERSIGN_ISSUER_TAX_ID (Seller tax/business-registration id (optional)), TERSIGN_LEDGER_URL (Ledger base URL (optional). Needed by the dispute tools, and with the API key and seller id by record_refund and chained issue_receipt; record_disclosure defaults to https://tersign.ai), TERSIGN_LEDGER_API_KEY (Ledger seller API key (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_SELLER_ID it enables record_refund and chained issue_receipt; with TERSIGN_LEDGER_URL it authenticates respondent dispute evidence. record_disclosure needs no API key), TERSIGN_LEDGER_SELLER_ID (Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt).

Alternatives to Tersign Evidence

same job, measured the same way
Kasbah MCP
by al-adnane

Governance layer for agentic AI — signed, verifiable receipts for every agent action.

39 installs/wk local only
Evermint MCP
by evermint-app

Mint tamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.

47 installs/wk local only
Postcept
by postcept

Verify agent actions against the system of record and get signed completion receipts.

31 installs/wk local only
PEAC Protocol: Signed interaction receipts
by peacprotocol

Portable signed records for agent, API, MCP, and cross-runtime interactions.

345 installs/wk local only
Proof Layer
by world-999-labs

Signed, hash-chained provenance receipts for AI agent actions.

39 installs/wk local only
Ccs
by correctover

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

local only
agentgate
by ciceroyang

Read-only evidence for the tools agents run: MCP server records, coverage and policy.

90 installs/wk local only
TookEffect
by tookeffect

Independent effect verification and signed receipts for consequential AI agent actions.

answering

Tersign Evidence — questions

Answers built from our own checks of this server.

Why is there no uptime for Tersign Evidence?
Tersign Evidence runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package tersign was installed 472 times last week.
How do I connect Tersign Evidence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls tersign straight from npm; nothing to host, nothing to sign up for.
How many people use Tersign Evidence?
The npm package tersign was installed 472 times in the last week. Week over week that is -31%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Tersign Evidence open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.