Skip to main content
Glama
Nuraveda-Labs

@qed-proof/mcp

Related Servers

Alternatives to @qed-proof/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts to verify agent spending mandates and receipts, providing stateless tools for authorization, chain verification, credential verification, and DID resolution.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and verify tamper-evident cryptographic evidence, manage key-bound Agent Passports, and support verifiable handoffs, approvals, and audit trails through MCP, REST, and A2A.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to cross-verify candidate claims against caller-supplied source texts, flagging hallucinations, numerical drift, entity mismatches, contradictions, and unverified assertions. It returns sentence-level verdicts with matched evidence snippets and machine-readable factual grounding confidence scores, exposed over MCP stdio, HTTP REST, and A2A discovery routes.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables deterministic verification of AI agent decisions and actions, providing PASS/FAIL/ABSTAIN verdicts with replayable proofs and an optional signed receipt ledger.
      7 npm
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct operation: submit a claim, get a single verdict, retrieve a receipt, verify a receipt, list claims, and list connections. Though get_verdict and list_claims both expose verdict information, one is a targeted lookup and the other is a filtered list, so selection should be unambiguous.

    Naming Consistency5/5

    All tool names consistently follow a verb_noun snake_case pattern: get_*, list_*, submit_*, verify_*. There are no mixed casing styles, vague verbs, or unpredictable naming conventions.

    Tool Count5/5

    Six tools is well-scoped for the claim/receipt verification domain. Each tool covers a necessary step in the workflow without unnecessary duplication or bloat.

    Completeness4/5

    The full claim lifecycle is covered: submit, poll/check verdict, fetch receipt, verify receipt, and list claims/connections. The only notable limitation is that verify_receipt explicitly does not check the on-chain anchor, so full trust-level-2 verification is not available within this tool set, though this is documented as an intentional scope boundary.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues