sdcreceipt-mcp
OfficialRelated Servers
Alternatives to sdcreceipt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables agents to issue and verify Ed25519-signed receipts over artifacts, binding an agent, task and file hash so anyone can confirm offline that a delivered file is unchanged. It exposes two tools, issue_receipt and verify_receipt, requiring no account, chain or network access.MIT
- AlicenseNot gradedqualityBmaintenanceExposes two tools over streamable HTTP: write_receipt, which issues a signed, hash-chained receipt for each cleared agent read using a per-writer bearer token, and verify_receipt, a public endpoint that checks a receipt against the published JWKS keyring. This lets agents and auditors prove what an answer relied on without contacting the issuer.MIT

vantic-mcpofficial
AlicenseNot gradedqualityDmaintenanceEnables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.Apache 2.0- AlicenseNot gradedqualityBmaintenanceIssue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.0Inno Setup
- FlicenseNot gradedqualityCmaintenanceEnables querying and verifying signed receipts of static inspections of public agent skills via read-only tools such as search_receipts, get_receipt, and get_verification_material.1-
- AlicenseAqualityCmaintenanceProvides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.453 npm1MIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another tool. Its purpose (verify a VSL Settlement Receipt) is stated clearly and unambiguously.
The lone tool follows a clean verb_noun snake_case convention (verify_receipt), which is the idiomatic form for MCP tools. No naming conflicts or mixed conventions exist.
A single tool is thin even for a narrow domain; there is no way to run individual checks, fetch issuer keys, or introspect the verification process. It is defensible for a focused verifier but leaves no granularity for callers.
The tool covers the core lifecycle of the stated purpose (full verification reporting all checks, including passes), so the main workflow has no dead end. Minor gaps remain, such as discovering issuer keys or running a subset of checks, but the caller-supplied key document mitigates the biggest one.