Search / io.github.tersignhq/evidence
protogridL0· runs locallyThe record layer for the machine age: counter-signed receipts and agent action records.
v0.6.7 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"evidence": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"TERSIGN_SELLER_KEY": "${TERSIGN_SELLER_KEY}",
"TERSIGN_LEDGER_API_KEY": "${TERSIGN_LEDGER_API_KEY}"
}
}
}
}claude mcp add evidence -e "TERSIGN_SELLER_KEY=${TERSIGN_SELLER_KEY}" -e "TERSIGN_LEDGER_API_KEY=${TERSIGN_LEDGER_API_KEY}" -- npx -y [email protected][mcp_servers.evidence]
command = "npx"
args = ["-y", "[email protected]"]
env = { "TERSIGN_SELLER_KEY" = "${TERSIGN_SELLER_KEY}", "TERSIGN_LEDGER_API_KEY" = "${TERSIGN_LEDGER_API_KEY}" }
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"evidence": {
"type": "local",
"command": [
"npx",
"-y",
"[email protected]"
],
"enabled": true,
"environment": {
"TERSIGN_SELLER_KEY": "{env:TERSIGN_SELLER_KEY}",
"TERSIGN_LEDGER_API_KEY": "{env:TERSIGN_LEDGER_API_KEY}"
}
}
}
}{
"mcpServers": {
"evidence": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"TERSIGN_SELLER_KEY": "${TERSIGN_SELLER_KEY}",
"TERSIGN_LEDGER_API_KEY": "${TERSIGN_LEDGER_API_KEY}"
}
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=evidence&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInRlcnNpZ25AMC42LjciXSwiZW52Ijp7IlRFUlNJR05fU0VMTEVSX0tFWSI6IiR7VEVSU0lHTl9TRUxMRVJfS0VZfSIsIlRFUlNJR05fTEVER0VSX0FQSV9LRVkiOiIke1RFUlNJR05fTEVER0VSX0FQSV9LRVl9In19"
}{
"servers": {
"evidence": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"TERSIGN_SELLER_KEY": "${TERSIGN_SELLER_KEY}",
"TERSIGN_LEDGER_API_KEY": "${TERSIGN_LEDGER_API_KEY}"
}
}
}
}{
"mcpServers": {
"evidence": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"TERSIGN_SELLER_KEY": "${TERSIGN_SELLER_KEY}",
"TERSIGN_LEDGER_API_KEY": "${TERSIGN_LEDGER_API_KEY}"
}
}
}
}extensions:
"evidence":
enabled: true
name: "evidence"
type: stdio
cmd: "npx"
args:
- "-y"
- "[email protected]"
envs:
"TERSIGN_SELLER_KEY": "${TERSIGN_SELLER_KEY}"
"TERSIGN_LEDGER_API_KEY": "${TERSIGN_LEDGER_API_KEY}"
timeout: 300
Placeholders to fill from your own secret store: ${TERSIGN_SELLER_KEY}, ${TERSIGN_LEDGER_API_KEY}. The registry never accepts secret values.
This is a local package: the command runs on your machine.
Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)stability.changes, stability.rug_pulltool list unknownNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website ~liveness-unmeasured +updated-4d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
[email protected] npmthis version is not known to the dependency resolver
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
tersign | npm | 0.6.7 | npx | TERSIGN_SELLER_KEY, TERSIGN_LEDGER_API_KEY |
No tools observed. Local packages are never executed by the registry.
Schemas: list_tools.
{
"name": "io.github.tersignhq/evidence",
"_meta": {
"io.modelcontextprotocol.registry/publisher-provided": {
"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"
],
"license": "Apache-2.0",
"summary": "Tersign is the record layer for the machine age: what AI agents do and pay, counter-signed by a party outside the deal, anchored where no one can move it, checkable by anyone (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-formatted 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",
"categories": [
"finance",
"security"
]
}
},
"title": "Tersign Evidence",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"version": "0.6.7",
"packages": [
{
"version": "0.6.7",
"transport": {
"type": "stdio"
},
"identifier": "tersign",
"runtimeHint": "npx",
"registryType": "npm",
"environmentVariables": [
{
"name": "TERSIGN_SELLER_KEY",
"format": "string",
"isSecret": true,
"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."
},
{
"name": "TERSIGN_ISSUER_NAME",
"format": "string",
"description": "Seller/issuer display name"
},
{
"name": "TERSIGN_ISSUER_JURISDICTION",
"format": "string",
"description": "Seller jurisdiction (e.g. HK)"
},
{
"name": "TERSIGN_ISSUER_TAX_ID",
"format": "string",
"description": "Seller tax/business-registration id (optional)"
},
{
"name": "TERSIGN_LEDGER_URL",
"format": "string",
"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"
},
{
"name": "TERSIGN_LEDGER_API_KEY",
"format": "string",
"isSecret": true,
"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."
},
{
"name": "TERSIGN_LEDGER_SELLER_ID",
"format": "string",
"description": "Ledger seller id (optional). With TERSIGN_LEDGER_URL and TERSIGN_LEDGER_API_KEY it enables record_refund and chained issue_receipt."
}
]
}
],
"repository": {
"url": "https://github.com/tersignhq/tersign-js",
"source": "github"
},
"websiteUrl": "https://tersign.ai",
"description": "The record layer for the machine age: counter-signed receipts and agent action records."
}