PluginBench
MCP Server
Active
MIT

Tersign Evidence MCP Server

io.github.tersignhq/evidence

RepositoryRegistry
How to choose

What this kind of tool is for

  • Chain multi-step workflows across the other tools in this directory.
  • Run a scheduled or triggered job instead of retyping the same request.
  • Have your agent watch a feed, queue, or repo and act on new items.

How to compare servers like this

Trigger model:
Understand what starts the automation — a command, a schedule, or an event — before relying on it.
Blast radius:
Prefer tools that hand you a review point before an irreversible action runs.
Chaining cost:
Each chained step adds a failure point; keep critical paths on the fewest tools.
Maintenance signal:
Automations break quietly; a maintained tool is the difference between repair and rediscovery.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the Tersign Evidence MCP server?

Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes.

How to install Tersign Evidence

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • TERSIGN_SELLER_KEY
    secret

    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
    secret

    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.

~/Library/Application Support/Claude/claude_desktop_config.json
JSON config
{
  "mcpServers": {
    "evidence": {
      "command": "npx",
      "args": [
        "-y",
        "tersign"
      ],
      "env": {
        "TERSIGN_SELLER_KEY": "<YOUR_TERSIGN_SELLER_KEY>",
        "TERSIGN_ISSUER_NAME": "<YOUR_TERSIGN_ISSUER_NAME>",
        "TERSIGN_ISSUER_JURISDICTION": "<YOUR_TERSIGN_ISSUER_JURISDICTION>",
        "TERSIGN_ISSUER_TAX_ID": "<YOUR_TERSIGN_ISSUER_TAX_ID>",
        "TERSIGN_LEDGER_URL": "<YOUR_TERSIGN_LEDGER_URL>",
        "TERSIGN_LEDGER_API_KEY": "<YOUR_TERSIGN_LEDGER_API_KEY>",
        "TERSIGN_LEDGER_SELLER_ID": "<YOUR_TERSIGN_LEDGER_SELLER_ID>"
      }
    }
  }
}

Related MCP servers

AI-powered crypto trading tools. Strategies, backtests, bots, and portfolio management.

0
TypeScript
View repository →

AI agent service marketplace — browse, purchase, and manage services via x402/USDC

2
TypeScript
MIT
View repository →

MCP server for amoCRM API — leads, contacts, pipelines. Auth: Bearer token.

0
TypeScript
MIT
View repository →

MCP server for Boxberry delivery API — city/point search, delivery calculation, tracking. 4 tools.

0
TypeScript
MIT
View repository →

A MCP server for TestDino

8
TypeScript
MIT
View repository →
TETesterArmy logo

AI agents that test your web and mobile apps like real users on every pull request.

51
Shell
MIT
View repository →