Tersign Evidence MCP Server

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

Local serverstdio

What is the Tersign Evidence MCP Server?

Tersign Evidence is an MCP integration. Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes.

Packages and local setup

The published npm package is tersign, version 0.6.4. Its declared MCP transport is stdio.

The package declares 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.6.4 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
TERSIGN_SELLER_KEYOptional: 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.Check documentation
TERSIGN_ISSUER_NAMESeller/issuer display nameCheck documentation
TERSIGN_ISSUER_JURISDICTIONSeller jurisdiction (e.g. HK)Check documentation
TERSIGN_ISSUER_TAX_IDSeller tax/business-registration id (optional)Check documentation
TERSIGN_LEDGER_URLLedger 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.aiCheck documentation
TERSIGN_LEDGER_API_KEYLedger 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.Check documentation
TERSIGN_LEDGER_SELLER_IDLedger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.Check documentation