forestrie-verify
OfficialRelated Servers
Alternatives to forestrie-verify
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables offline verification of signed AI-agent receipt bundles and generation of auditor-ready Markdown compliance reports for frameworks including EU AI Act Annex IV, ISO/IEC 42001, NIST AI RMF, SOC 2, GDPR, HIPAA, and EU CRA.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to verify signed ResultBond Proof Receipts offline against a root-signed keyset, enforcing signature, role, time, revocation, and minimum serial checks without altering files or making network calls.Apache 2.0
- 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-
- 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
- AlicenseAqualityCmaintenanceMCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.46Apache 2.0
- AlicenseAqualityBmaintenanceLets an agent verify VSL settlement receipts entirely offline and produce signed triggers authorizing a settlement, with the signing key and endpoint fixed at start-up rather than passed in tool calls. When started with an endpoint and token, it can also request a receipt from an issuer, which is the only tool that touches the network.192 PyPIApache 2.0
TDQS
Scored across 3 tools
verify_receipt and verify_grant_receipt both perform verification but target different artifact types (regular receipt vs. grant receipt), and the descriptions clarify the distinction. decode_receipt is clearly separate since it only renders CBOR without verification.
All tool names use snake_case and follow a predictable verb_noun pattern: verify_receipt, verify_grant_receipt, decode_receipt. The longer grant variant remains readable and consistent with the others.
Three tools is a focused, well-scoped set for a verification service, with each tool earning its place. It sits at the low end of the typical 3–15 range, so it is slightly thin but still appropriate.
The server covers the core lifecycle: verifying a standard receipt, verifying a grant receipt, and decoding raw receipt data. Minor gaps exist around batch verification or chain-level checks, but the essential verification surface is present.