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.
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 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.
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 evidence -- npx -y tersign
{
"mcpServers": {
"evidence": {
"command": "npx",
"args": [
"-y",
"tersign"
]
}
}
}
[mcp_servers.evidence]
command = "npx"
args = ["-y", "tersign"]
{
"mcpServers": {
"evidence": {
"command": "npx",
"args": [
"-y",
"tersign"
]
}
}
}
{
"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).
Governance layer for agentic AI — signed, verifiable receipts for every agent action.
Mint tamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.
Verify agent actions against the system of record and get signed completion receipts.
Portable signed records for agent, API, MCP, and cross-runtime interactions.
Signed, hash-chained provenance receipts for AI agent actions.
Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
Independent effect verification and signed receipts for consequential AI agent actions.
Answers built from our own checks of this server.