Skip to main content
Glama

Related Servers

Alternatives to zkproofport-ai

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request and pay for privacy-preserving human verification claims, such as age over 18, via MCP with x402 settlement on Algorand, returning proofs without exposing personal data.
      2 npm
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for wallet auth: read wallet state on-chain, evaluate against conditions, return an ECDSA-signed boolean with a post-quantum companion signature. Condition-based access across 37 chains (EVM, Solana, XRPL, Bitcoin, Tron, Stellar, Sui). No balances, no identity, no shared secrets; verifiable offline via JWKS. 27 tools: wallet attestation, trust profiles, payment verification.
      27
      1,587 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.
      441 npm
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    The step tools (prepare_inputs, request_challenge, submit_proof, verify_proof) are clearly sequenced and get_supported_circuits/get_action_approval are distinct. The main overlap is generate_proof, which deliberately duplicates the three-step flow, but the description explicitly frames it as an all-in-one shortcut so an agent can choose correctly.

    Naming Consistency5/5

    All seven tools use a consistent snake_case verb_noun pattern (prepare_inputs, request_challenge, submit_proof, generate_proof, verify_proof, get_action_approval, get_supported_circuits) with no mixing of conventions or vague verbs.

    Tool Count5/5

    Seven tools is well-scoped for a ZK proof orchestration server, cleanly covering discovery, the stepwise flow, the all-in-one path, verification, and approval status without redundant bloat.

    Completeness4/5

    The full proof lifecycle is covered: discover circuits, prepare inputs, fetch challenge, submit proof, verify on-chain, and check human approval. Minor gaps remain, such as no tool for listing/cancelling prior approvals or managing payment offers despite the payment messaging in descriptions.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive