Rein
Related Servers
Alternatives to Rein
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceSpending limits for AI agents. Create budgets, enforce limits, track spend across x402, cards, MPP, or any payment rail.7Apache 2.0
- AlicenseNot gradedqualityCmaintenanceBudget & 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
- AlicenseAqualityAmaintenanceA 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.810MIT
- AlicenseAqualityBmaintenanceThis tool library gives AI agents a discovery and "know before you pay" layer to find useful services and check the historic reputation across >200,000 endpoints in the public x402 ecosystem.15237 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to securely access x402-protected APIs on Base L2 with automatic USDC payments under deterministic spending limits, domain and contract allowlists, transaction simulation, and audit logging.467 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to discover and inspect x402 paid APIs, check payment requirements, and make capped payments using configurable wallets, with optional Nevermined credit support. Human-controlled spending limits and network settings help keep payments within approved hosts and budgets.8MIT
TDQS
Scored across 5 tools
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.
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).
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.
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.