Skip to main content
Glama
bugiiiii11

Rein

by bugiiiii11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Rein

No user-submitted related servers found.

    Related Servers

    • Budget Governor

      mightbesaad
      A
      license
      Not graded
      quality
      C
      maintenance
      Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).
      MIT
    • PipRail by piprail

      PipRailofficial

      piprail
      A
      license
      A
      quality
      A
      maintenance
      A budget-bound x402 payment wallet for AI agents: it autonomously pays HTTP 402 payment-gated URLs across every major chain (EVM, Solana, and many non-EVM families). Self-custodial and backendless, your key, your RPC, with spend caps enforced before any on-chain send.
      8
      9
      MIT

    • ada-wallet

      loveaihq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pay x402 endpoints on Cardano through a policy-gated wallet with spend caps, payee allowlists, human approval, and an audit log.
      1,341 npm
      Apache 2.0
    • @bridgenode/mcp by bridgenode-ai

      @bridgenode/mcpofficial

      bridgenode-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to make pay-as-you-go AI inference requests through x402 with automatic Solana USDC payments, no API keys or registration, while enforcing configurable spending limits.
      3
      90 npm
      1
      MIT No Attribution
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct concern: rein_fetch acts, rein_status reads rules/standing, rein_receipts reads decision history, rein_escalations reads the pending-approval queue, and rein_heartbeat signals liveness. The only mild overlap is that escalations are a subset of the payments tracked in receipts, but the descriptions explicitly separate the two.

    Naming Consistency4/5

    All five tools share a consistent 'rein_' prefix, giving a predictable namespace. The only deviation is rein_fetch, a verb-action tool among otherwise noun/resource-oriented names (escalations, heartbeat, status, receipts).

    Tool Count4/5

    Five tools is well-scoped for a focused payment-governance server; each maps to a real need (pay, check status, review receipts, review escalations, signal liveness). It sits at the low end, but nothing feels redundant.

    Completeness4/5

    The surface covers the core agent lifecycle: making governed payments, inspecting rules/standing, verifying settlement, tracking escalations, and heartbeat monitoring. Minor gaps exist — no callable approve/deny action (deliberately out of scope, since approvals are external signatures) and no tool to declare the activity expectation that heartbeat requires.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources