Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TERSIGN_SELLER_KEYAPI keyoptionalOptional: 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…
TERSIGN_LEDGER_API_KEYAPI keyoptionalLedger 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…
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
issue_receiptNo description publishedThis tool published no description. Forge does not invent one.
verify_receiptNo description publishedThis tool published no description. Forge does not invent one.
record_disclosureNo description publishedThis tool published no description. Forge does not invent one.
verify_compliance_recordNo description publishedThis tool published no description. Forge does not invent one.
record_refundNo description publishedThis tool published no description. Forge does not invent one.
open_disputeNo description publishedThis tool published no description. Forge does not invent one.
submit_dispute_evidenceNo description publishedThis tool published no description. Forge does not invent one.
adjudicate_disputeNo description publishedThis tool published no description. Forge does not invent one.
get_disputeNo description publishedThis tool published no description. Forge does not invent one.
0 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.