Tersign Evidence MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

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.

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.

claude mcp add evidence -- npx -y tersign

{
  "mcpServers": {
    "evidence": {
      "args": [
        "-y",
        "tersign"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.evidence]
command = "npx"
args = ["-y", "tersign"]

{
  "mcpServers": {
    "evidence": {
      "args": [
        "-y",
        "tersign"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "evidence": {
      "args": [
        "-y",
        "tersign"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: TERSIGN_SELLER_KEY (0x-prefixed private key the seller signs receipts with), 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 (Hosted ledger base URL for counter-signing (optional; SDK works standalone)), TERSIGN_LEDGER_API_KEY (Ledger seller API key (required only if counter-signing)), TERSIGN_LEDGER_SELLER_ID (Ledger seller id (required only if counter-signing)). The author declared them in the registry entry; get the values from the project itself.