Tersign Evidence MCP server

Read from the package source without running it. The installed server may list more.

• adjudicate_dispute

  Trigger deterministic adjudication of an open dispute. The v0 rulebook is public and the verdict is recomputable by anyone from the chain — no discretion, no model in the loop.

• get_dispute

  Fetch a dispute in full: its state, both sides' evidence references, the verdict and rationale once adjudicated, and the ledger signature over the record.

• issue_receipt

  Issue an x402 offer-receipt (EIP-712) plus a Tersign action record for a payment that has ALREADY settled, and counter-sign both into your hash chain when a ledger is configured.

• open_dispute

  Open an objective dispute against a counter-signed receipt as the PAYER (the configured key must be the receipt payer). Reasons: not_delivered, wrong_content, duplicate_charge. Contested non-mechanical claims escalate to the arbiter; duplicate_charge is decided instantly from ledger arithmetic.

• record_disclosure

  One-call disclosure evidence (EU AI Act Art 50 dialect): digests the disclosure text LOCALLY, signs an action record with your key, and the public ledger counter-signs it into your per-signer hash chain. No API key needed — first call self-provisions a free signer-keyed account.

• record_refundwrite action

  Record a refund against an already-chained receipt, as the SELLER. The refund becomes its own counter-signed entry that references the original — nothing is edited or deleted, so the chain stays append-only and both the charge and the refund remain visible.

• submit_dispute_evidencewrite action

  Submit signed evidence to an open dispute. Claimant evidence must be signed by the payer key; respondent evidence additionally requires the seller API key (TERSIGN_LEDGER_API_KEY).

• verify_compliance_record

  Verify a Tersign action record against its attestation: recompute the record's canonical digest, confirm the attestation commits to that exact digest, and recover the signature.

• verify_receipt

  Verify an offer-receipt artifact: recover the EIP-712 signature and confirm the payload digest binds to it.

• Code scan61 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 22 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Tersign Evidence: common questions

Is Tersign Evidence MCP server safe?

Mostly: it is graded B (82/100). Read the Tersign Evidence safety report

How do I install Tersign Evidence?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Tersign Evidence need an API key?

Yes. The registry entry asks for TERSIGN_SELLER_KEY, TERSIGN_LEDGER_API_KEY.

Is Tersign Evidence maintained?

The last commit was 22 days ago (2026-08-30). The latest release is v0.4.11.

What can I use instead of Tersign Evidence?

Servers from other publishers that do the same job: Protect MCP server, Mockserver MCP server and CHAP Coordinator MCP server. Compare all Tersign Evidence alternatives.