reciprocal-ruler-mcp
Related Servers
Alternatives to reciprocal-ruler-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn outbound arbitrage agent for 402-enabled MCP endpoints that probes, counter-offers, and settles USDC on Base L2, automating margin arbitrage without human intervention.MIT
- AlicenseNot gradedqualityDmaintenanceMulti-party escrow and settlement for autonomous agent transactions with x402 micropayments and dispute resolution on Base, Ethereum, or Solana.MIT
- AlicenseNot gradedqualityDmaintenanceSettlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * LiMIT
- AlicenseBqualityBmaintenanceEnables MCP clients to query live Base chain data — lending yields, cross-venue arbitrage spreads, pool withdrawability, token risk checks, allocation plans and wallet health — with each paid call settled in USDC over x402 without an API key or any ETH on the buyer's side. Results come from current chain state rather than a stale database, at per-call prices small enough for an agent to consult on every decision.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to access production-grade paid MCP tools with real on-chain x402 v2 settlement, including EVM wallet risk scoring, payload normalization, and facilitator discovery, all discoverable via Bazaar-compatible metadata.MIT
- AlicenseNot gradedqualityCmaintenanceEnables paid access to Polymarket odds, cross-venue disagreement data, attested market data packages, and Hyperliquid funding rates through MCP tools using x402 USDC payments on Base.MIT
TDQS
Scored across 3 tools
The tools are largely distinct, separating the initial quoting process from two different types of reconciliation. The primary overlap is between the two reconciliation functions, but their purpose (trial vs. official settlement) is clearly differentiated by their descriptions.
The tools follow a highly consistent naming convention using snake_case and a clear prefix (ruler_). The structure (action_focus) is maintained across all three entries.
For a specialized system managing the settlement lifecycle between AI agents, three tools are well-scoped and provides excellent coverage of the core necessary actions. It is neither too sparse nor overly bloated.
The set covers the core workflow: locking terms, testing the settlement process, and performing the final settlement. While it lacks tools for initiating the initial trade, it covers the necessary transactional milestones.