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.2 npm-
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- 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.271,587 npm2MIT
- FlicenseNot gradedqualityCmaintenanceProduction-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.441 npm1MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.