Rein MCP server
io.github.bugiiiii11/rein·v0.8.0Spend limits for AI agents that pay with x402: every paywall is policy-checked before a cent moves.
not scanned yet
0 stars507 downloads/wk
Reviews
Write oneNobody has reviewed Rein yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Rein tools
No tool declarations could be read from the package source. They show once the server is installed.
How Rein compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Downloads a week
- 507
- more than 88% of 12,191 servers with a package
Release history: 3 versions in the registry since 2026-10-08, latest 2026-10-18, typically one every 6 days.
Install Rein in Claude Code, Cursor or VS Code
Runs npx -y @reinconsole/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add rein -- npx -y @reinconsole/mcp
What the publisher says
From the Rein repository's README, as published. We do not edit it. Read it on GitHub
Rein
The control plane for AI agent payments. Rein sets the rules, watches every payment, and scores every counterparty — so agents can transact at machine speed without machine-speed losses.
Rein is developer tooling and middleware for the agentic payments economy (the x402 / ERC-8004 stack). It is non-custodial: Rein governs an agent's authority to spend, never the funds themselves. The whole design in one document: the whitepaper (PDF).
Status: v0.3 — all three phases have shipped their first cut, and a hosted engine runs an invited beta. Advisory SDK-mode + full observability, end to end — fully offline on mock rails, and live on real x402 rails on Base Sepolia (EIP-3009 USDC settled by the hosted x402.org facilitator — on both sides: the guarded agent and a @reinconsole/gate-monetized vendor). The session-key signer tier — the GA enforcement architecture, where the wallet key leaves the agent entirely — ships as @reinconsole/signer. The supply side ships as @reinconsole/gate, vendor monetization middleware (Phase 2). The stack is durable: @reinconsole/store persists the engine (agents, policies, spend, the signed decision chain), the reputation evidence, gate receipts + replay slots, and signer sessions across restarts. And @reinconsole/graph (Phase 3) turns the receipts both sides produce into explainable reputation scores that feed back into enforcement: vendorReputationLt policies on the agent side, payer screening at the vendor's door. Identity is on-chain: @reinconsole/erc8004 keys reputation by ratified ERC-8004 registrations — verified live against the real Base Sepolia Identity Registry.
Product phases
What's in v0.3
A complete demand-side Guard loop, runnable two ways: fully offline on mock rails (no accounts, no Docker, no chain), or live on Base Sepolia over the real x402 stack:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Rein: common questions
- Is Rein MCP server safe?
- Mostly: it is graded B (83/100). Read the Rein safety report
- How do I install Rein?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Rein need an API key?
- Yes. The registry entry asks for
REIN_ENGINE_API_KEY,REIN_PAYER_PRIVATE_KEY. - Is Rein maintained?
- The last commit was 26 days ago (2026-10-09). The latest release is v0.8.0.
- How does Rein compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); downloads a week 507 (more than 88% of 12,191 servers with a package). Full comparison.