Skip to main content
Glama

Related Servers

Alternatives to agentverify-checks

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Append-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.
      5
      826 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      The deterministic fact-verification layer for AI agents. Validates the structured facts an agent emits — IBANs, payment cards, VAT and national tax IDs, crypto and bank addresses, domains, emails, phone numbers, securities and academic identifiers, plus dates, currencies and holidays — against checksums and curated authoritative data, not guesses.
      56
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to verify claims deterministically by computing arithmetic, ratios, and dates and matching statements against provided sources, returning a confidence ladder of certain, source-backed, or unverifiable.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to obtain independent, Ed25519-signed receipts confirming real-world facts: whether a page is online, a domain is legitimate, an email address is deliverable, a heartbeat was declared, or a scheduled task actually ran. Each response includes a verifiable cryptographic receipt, so agents can prove to their users that an asserted outcome was observed by a neutral third party rather than self-attested.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to validate deliverables (JSON, ZIP, PDF, DOCX) against signed contracts, generating verifiable receipts with Ed25519 signatures.
      -

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct operation: single verification, batch verification, verification with signing, receipt signature check, and public key retrieval. The only mild overlap is between verify_calculation and verify_and_sign, but the descriptions make the signing distinction explicit.

    Naming Consistency5/5

    All names are snake_case and verb-led (verify_*, check_*, get_*), forming a predictable pattern throughout. verify_and_sign is slightly longer but still follows the convention.

    Tool Count5/5

    Five tools is well-scoped for a verification-and-signing service, with each tool earning its place. No redundant or filler tools are present.

    Completeness4/5

    The surface covers the core lifecycle: verify, batch verify, sign, check receipt, and retrieve public key. Minor gaps exist, such as no batch signing or receipt listing/retrieval, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues