tersign
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERSIGN_LEDGER_URL | No | Hosted ledger for counter-signing + chain checks | |
| TERSIGN_SELLER_KEY | Yes | 0x-prefixed private key that signs your receipts and records | |
| TERSIGN_ISSUER_NAME | No | Issuer name stamped on compliance records | |
| TERSIGN_LEDGER_API_KEY | No | Your seller API key on that ledger | |
| TERSIGN_LEDGER_SELLER_ID | No | Your seller id on that ledger | |
| TERSIGN_ISSUER_JURISDICTION | No | Issuer jurisdiction stamped on compliance records |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| issue_receiptA | Issue an x402 offer-receipt (EIP-712) plus an Tersign compliance record for a settled payment; counter-signs into the ledger when configured. |
| verify_receiptA | Verify an offer-receipt artifact (EIP-712) and optionally enforce an expected signer (payTo authorization). |
| record_disclosureA | 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. |
| verify_compliance_recordC | Verify an Tersign compliance record + attestation (digest binding and signature). |
| record_refundB | Record a refund against a receipt digest in the Tersign ledger (requires ledger configuration). |
| open_disputeA | 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. |
| submit_dispute_evidenceA | 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). |
| adjudicate_disputeA | Trigger deterministic adjudication of an open dispute (public — the v0 rulebook is recomputable by anyone). Refund verdicts create refund records automatically. |
| get_disputeA | Fetch a dispute record with its evidence, verdict, rationale, and ledger signature. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tersignhq/tersign-js'
If you have feedback or need assistance with the MCP directory API, please join our Discord server