The record layer for the machine age: counter-signed receipts and agent action records.
To add Tersign Evidence to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 7 environment variables, listed below.
Install
npx -y tersign@0.6.8Environment variables
TERSIGN_SELLER_KEYSet in your MCP configTERSIGN_ISSUER_NAMESet in your MCP configTERSIGN_ISSUER_JURISDICTIONSet in your MCP configTERSIGN_ISSUER_TAX_IDSet in your MCP configTERSIGN_LEDGER_URLSet in your MCP configTERSIGN_LEDGER_API_KEYSet in your MCP configTERSIGN_LEDGER_SELLER_IDSet in your MCP configInstall with your client
claude mcp add tersign-evidence --env TERSIGN_SELLER_KEY=<YOUR_TERSIGN_SELLER_KEY> --env TERSIGN_ISSUER_NAME=<YOUR_TERSIGN_ISSUER_NAME> --env TERSIGN_ISSUER_JURISDICTION=<YOUR_TERSIGN_ISSUER_JURISDICTION> --env TERSIGN_ISSUER_TAX_ID=<YOUR_TERSIGN_ISSUER_TAX_ID> --env TERSIGN_LEDGER_URL=<YOUR_TERSIGN_LEDGER_URL> --env TERSIGN_LEDGER_API_KEY=<YOUR_TERSIGN_LEDGER_API_KEY> --env TERSIGN_LEDGER_SELLER_ID=<YOUR_TERSIGN_LEDGER_SELLER_ID> -- npx -y tersign@0.6.8
Run this in a terminal to add the server to Claude Code.
What this does
Tersign Evidence exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
TERSIGN_SELLER_KEY TERSIGN_ISSUER_NAME TERSIGN_ISSUER_JURISDICTION TERSIGN_ISSUER_TAX_ID TERSIGN_LEDGER_URL TERSIGN_LEDGER_API_KEY TERSIGN_LEDGER_SELLER_ID
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install Tersign Evidence?
Run the Claude Code command in the install section to add Tersign Evidence to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with Tersign Evidence?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Tersign Evidence as well.
Does Tersign Evidence need an API key?
Yes. Before it can run, set these environment variables: TERSIGN_SELLER_KEY, TERSIGN_ISSUER_NAME, TERSIGN_ISSUER_JURISDICTION, TERSIGN_ISSUER_TAX_ID, TERSIGN_LEDGER_URL, TERSIGN_LEDGER_API_KEY, TERSIGN_LEDGER_SELLER_ID. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-tersignhq-evidence)<a href="https://clauderules.net/mcp/io-github-tersignhq-evidence" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-tersignhq-evidence" alt="Listed on clauderules.net" /></a>More DevTools MCP servers
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Inbox Zero
Search Gmail and Outlook, save drafts, manage email rules, and view email stats.