Skip to main content
Glama
forestrie-verify

forestrie-verify

Official
by forestrie

Related Servers

Alternatives to forestrie-verify

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Issue 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.
      0
      Inno Setup
    • A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      4
      6
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Lets 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.
      1
      92 PyPI
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues