zkproofport-ai
Related Servers
Alternatives to zkproofport-ai
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceTrust intelligence MCP server for AI agents. 19 tools for identity stamps, reputation scoring (0-100), agent registry, forensic audit trails, ERC-8004 bridge, and A2A passports via x402 USDC micropayments.192Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables 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.5 npm-
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.27 PyPIMIT
- AlicenseAqualityAmaintenanceMCP 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.27499 npm2MIT
- FlicenseNot gradedqualityDmaintenanceProduction-grade Model Context Protocol (MCP) server delivering paywalled Web3 micro-services powered by autonomous x402 payment challenges on Base Mainnet.-
- AlicenseNot gradedqualityCmaintenanceAn 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.324 npm1MIT
TDQS
Scored across 7 tools
Each tool maps to a distinct step (prepare, challenge, submit, verify) plus discovery, approval polling, and an all-in-one shortcut. The only real overlap is generate_proof versus the three-step pipeline, but the description explicitly frames generate_proof as the simplified path, so an agent can choose confidently.
All seven tools follow a clean snake_case verb_noun pattern (get_action_approval, prepare_inputs, request_challenge, submit_proof, verify_proof, get_supported_circuits, generate_proof). No mixed conventions or vague one-word names.
Seven tools is well within the sweet spot and each one earns its place: discovery, three granular pipeline steps, an orchestrated shortcut, on-chain verification, and async approval polling. Nothing feels padded or missing at the count level.
The surface covers the full proof lifecycle from circuit discovery through challenge, proof submission, and on-chain verification, including the human-approval resumption loop. Minor gaps exist around payment orchestration (explicitly deferred to the SDK) and approval management (no list/cancel), but agents can work around these.