proofmarket-mcp
Related Servers
Alternatives to proofmarket-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP hosts such as Claude and Cursor to dispatch tasks to live marketplace agents, poll or wait for verified settled results, list available agents by capability, and retrieve live protocol statistics with atomic settlement on Tempo.5109 npmMIT

io.github.zkp2p/peerofficial
AlicenseNot gradedqualityBmaintenanceExposes protocol, indexer, market, checkout, and cash-flow operations to agents through read-only, cash-preparation, and full operator profiles, with state-changing actions previewed before execution unless explicitly authorized.90 npmMIT- FlicenseNot gradedqualityAmaintenanceEnables AI agents to discover and inspect agent-bound markets, request HTTP 402 quotes, buy tokens cross-chain with USDC via EIP-3009 authorization, and read market history.2-

operate-mcpofficial
AlicenseAqualityCmaintenanceEnables MCP-compatible agents to publish marketplace services, poll and claim escrow-backed jobs, and submit fulfillments for review and payout.651 npm3MIT- AlicenseNot gradedqualityCmaintenanceEnables people and AI agents to create, preview, publish, withdraw, and discover offers and requests across goods, services, trips, and delivery, with semantic matching and secure shared rooms for negotiation.MIT

BlurHook MCPofficial
AlicenseAqualityBmaintenanceEnables Robinhood Chain trading agents to obtain quotes, policy-checked unsigned public-swap calldata, simulations, hook information, prices, and deployment discovery without holding keys or signing transactions.9MIT
TDQS
Scored across 5 tools
Most tools have clear boundaries: submit_proof_request and poll_proof handle request lifecycle, simulate_coordination explores scenarios, and compose_workflow orchestrates. However, market_state and simulate_coordination both report utilization and gaps, so agents could initially confuse which to use for current market health vs. hypothetical coordination regimes.
The set is mostly verb_noun (simulate_coordination, submit_proof_request, poll_proof, compose_workflow), but market_state breaks the pattern as a noun phrase rather than get_market_state, creating minor inconsistency.
Five tools is appropriate for the server's focus on market analysis, request submission, status polling, and workflow composition. It's neither sparse nor bloated, covering the core interactions with a proof market.
The core lifecycle is covered: market state inquiry, simulation for planning, request submission, result polling, and workflow orchestration. Missing operations like canceling requests or listing historical requests are workable gaps, but the essential seeker-approval journey is represented.