Skip to main content
Glama
reciprocal-ruler-mcp
by hwcho310

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RULER_API_BASENoAPI base URL (point it at a local or self-hosted instance if you run one).https://reciprocla-ruler-x402.onrender.com
RULER_TIMEOUT_SECONDSNoPer-request timeout. The free hosting tier sleeps when idle, so the first call of a session may need a warm-up; the client retries once on a network failure.90
RULER_TRIAL_CLIENT_IDNoSent as X-Trial-Client so your 3 free calls follow this agent id instead of the shared IP address. Recommended behind a NAT or shared proxy.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Reciprocal Ruler is a settlement oracle for transactions between AI agents. Start with ruler_trial_reconcile (3 free calls) to see the judgment; the paid tools ruler_quote_lock ($0.05) and ruler_reconcile ($0.25) settle in USDC on Base over x402. Amounts are KRW integers. Call /health on the API to check the service before a paid call.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ruler_trial_reconcileA

Run a settlement reconciliation between two AI agents for free (up to 3 calls per client). Compares the expected amount with what actually settled and returns a deterministic judgment: SETTLED_OK, COMPENSATED (shortfall covered from the holdback), or PENDING_RECONCILIATION (half-open timeout, left pending). Use it to evaluate whether Reciprocal Ruler fits your agent-to-agent transaction flow before paying. Amounts are KRW integers.

ruler_quote_lockA

Lock the trade terms the two agents agreed on and get a deterministic quote_hash both sides can cite later. Costs $0.05 USDC on Base, paid with x402. Without a payment this tool returns the HTTP 402 payment challenge decoded into Base USDC instructions; pay it with an x402 wallet and pass the signed payload back as payment_header to complete the call. If the two agents run different rule versions the call is refused with VERSION_MISMATCH (409) and nothing is charged.

ruler_reconcileA

Idempotent settlement reconciliation recorded in an append-only audit ledger. Costs $0.25 USDC on Base via x402; without payment it returns the decoded payment challenge and Base USDC instructions. Reusing the same idempotency_key makes a retry return the original judgment instead of charging again, so always pass the key your first attempt used. Judgment is one of SETTLED_OK, COMPENSATED, PENDING_RECONCILIATION.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues