{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"io.github.tersignhq/evidence","description":"Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes.","title":"Tersign Evidence","repository":{"url":"https://github.com/tersignhq/tersign-js","source":"github"},"version":"0.6.3","websiteUrl":"https://tersign.ai","packages":[{"registryType":"npm","identifier":"tersign","version":"0.6.3","runtimeHint":"npx","transport":{"type":"stdio"},"environmentVariables":[{"description":"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.","format":"string","isSecret":true,"name":"TERSIGN_SELLER_KEY"},{"description":"Seller/issuer display name","format":"string","name":"TERSIGN_ISSUER_NAME"},{"description":"Seller jurisdiction (e.g. HK)","format":"string","name":"TERSIGN_ISSUER_JURISDICTION"},{"description":"Seller tax/business-registration id (optional)","format":"string","name":"TERSIGN_ISSUER_TAX_ID"},{"description":"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","format":"string","name":"TERSIGN_LEDGER_URL"},{"description":"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.","format":"string","isSecret":true,"name":"TERSIGN_LEDGER_API_KEY"},{"description":"Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt.","format":"string","name":"TERSIGN_LEDGER_SELLER_ID"}]}],"_meta":{"io.modelcontextprotocol.registry/publisher-provided":{"categories":["finance","security"],"license":"Apache-2.0","summary":"Tersign is the evidence layer for agent commerce (B2B / machine-to-machine). Agents issue seller-signed EIP-712 receipts and action records; the hosted ledger at https://tersign.ai optionally counter-signs them into per-seller hash chains that anyone can verify without an account. Disputes export as venue-ready evidence envelopes (generic / internet-court / kleros / uma). The SDK and MCP server work fully standalone without the hosted ledger: issue and verify offline, counter-sign later. No configuration is needed: every environment variable is optional, and the server generates and keeps a local signing key on first run when none is set. record_disclosure's first call self-provisions a free signer-keyed account on the ledger (https://tersign.ai by default), except when that key is already registered to an API-key account (409) or the daily provisioning caps are reached (429; https://tersign.ai/pricing). Canonical bytes, digests and chain construction are pinned by public two-sided conformance vectors: https://github.com/tersignhq/evidence-record-conformance (Apache-2.0, CI-tested). Verify a live counter-signed record right now: npx tersign verify 0xe5874f1ffe87f0a6dd9eb157730f67b86ee4538b125fe30fcc4e165213dd3fc4 --ledger https://tersign.ai","tags":["evidence","receipts","counter-signing","agent-commerce","agent-payments","x402","disputes","eip-712","audit-trail","verification"],"tools":["issue_receipt","verify_receipt","verify_compliance_record","record_disclosure","record_refund","open_dispute","submit_dispute_evidence","adjudicate_dispute","get_dispute"]}}},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-10-09T17:20:05.191152Z","publishedAt":"2026-10-09T17:20:05.191152Z","updatedAt":"2026-10-09T17:20:05.191152Z","isLatest":true}}}