No user-submitted related servers found.
Scored across 8 tools
Most tools target distinct actions: deposit, balance, discovery, verification, and the three explicit proof steps are clearly separated. The only overlap is generate_proof versus the step-by-step prepare/request/submit flow, but the descriptions explicitly position generate_proof as the all-in-one alternative.
The majority follow a consistent snake_case verb_noun pattern: generate_proof, verify_proof, request_challenge, prepare_inputs, submit_proof, get_supported_circuits. Minor deviations are gateway_balance (missing a get_ prefix) and deposit_to_gateway (prepositional form), but these are not confusing.
Eight tools is well-scoped for a ZK proof service covering discovery, payment setup, proof generation, and verification. Each tool earns its place without redundancy or bloat.
The core lifecycle is covered: discover circuits, fund the gateway, check balance, generate proofs via either path, and verify on-chain. Minor gaps exist such as no explicit withdrawal/refund tool for unused gateway funds, but agents can complete the primary proof-generation workflow without dead ends.