Tersign Evidence

Package (npm 0.6.8)

npx -y [email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "tersign-js": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "TERSIGN_SELLER_KEY": "<YOUR_VALUE>",
        "TERSIGN_LEDGER_API_KEY": "<YOUR_VALUE>"
      }
    }
  }
}

• 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.