Skip to main content
Glama
Nuraveda

@qed-proof/mcp

by Nuraveda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @qed-proof/mcp

No user-submitted related servers found.

    Related Servers

    • FLINT Agent Passport

      thefraudfather
      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
    • vantic-mcp by vanticlabs

      vantic-mcpofficial

      vanticlabs
      A
      license
      Not graded
      quality
      D
      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

    • AccordTrace

      Kosta1985
      A
      license
      Not graded
      quality
      D
      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

    • ribcage-agent-services

      JRCage
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server wrapping the Ribcage Verification & Research Desk API: claim validation with receipts, scoped research, token screening, settlement verification, and editing tools for AI agents.
      MIT

    • claimgate

      caseone115
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to gate drafts before publishing by extracting and checking claims against supplied evidence, enforcing configured policy rules, and flagging missing AI-disclosure requirements. It exposes tools for draft checks, claim listing, policy-only checks, and server metadata.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    get_receipt, get_verdict, and verify_receipt all touch receipts/verdicts and could initially be confused, but descriptions clearly separate them: get_verdict reads a claim's state/verdict, get_receipt returns the full signed artifact, and verify_receipt does an independent offline cryptographic check. The remaining tools (submit_claim, list_claims, list_connections, get_log_head) target distinct resources, so boundaries are mostly clear.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern: get_receipt, get_verdict, get_log_head, verify_receipt, list_claims, list_connections, submit_claim. Verbs (get/list/verify/submit) map predictably to read, enumerate, validate, and write actions.

    Tool Count5/5

    Seven tools is well-scoped for a claim-verification service covering submit, poll, retrieve, independently verify, list, and log-head inspection. Nothing feels padded or redundant, and each tool earns its place.

    Completeness4/5

    The claim lifecycle is well covered (submit, get_verdict, get_receipt, verify_receipt, list_claims) plus supporting list_connections and get_log_head. Minor gaps: no tool to fetch a Merkle log entry or a consistency proof (the log-head description notes a consistency proof is what extends a head, but none is exposed), and receipts themselves cannot be listed directly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources