RMI MCP + x402 Gateway
Provides Solana chain-data tools via the data_mcp_solana module, using a configured Helius RPC endpoint, and supports Solana as an x402 payment network through per-network payee configuration.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
rmi-mcp-x402
An MCP server whose tools are paid per call over x402: an agent discovers a tool, gets a 402 with a price, pays in USDC on-chain, and retries with proof of payment. The facilitator is bundled, so it runs as one stack.
Status: beta · Licence: MIT, see LICENSE.
Canonical: https://git.rugmunch.io/RugMunchMedia/rmi-mcp-x402
Run it yourself
Needs: Python 3.11+, Redis for receipts, and a receiving address you control.
Settlement needs a funded payer and a reachable RPC.
Minimal env: X402_WALLET, X402_SELF_FACILITATE, REDIS_URL.
git clone https://git.rugmunch.io/RugMunchMedia/rmi-mcp-x402.git
cd rmi-mcp-x402
python3 -m venv .venv && . .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env # X402_WALLET, X402_SELF_FACILITATE, REDIS_URL
python data_mcp_server.pyCompose runs the MCP server and its facilitator together:
docker compose up -d # services: rmi, coffer, redisCheck it works:
curl -s localhost:8001/v1/x402/healthThat is the bundled facilitator answering, which is the dependency that actually
fails first. The compose healthcheck probes the same URL, so a healthy container
and a healthy curl mean the same thing.
Read-only tools answer without payment. Anything priced returns a 402 first — that is the expected first response, not a failure.
Related MCP server: coinopai-mcp
What it needs
Component | Role | Where it comes from |
| the facilitator: challenge, verify, settle, receipts | bundled in this repo and in its compose file |
Redis | receipt store; without it replay protection is off | your own, or |
A payee address | where payments land; anything else is rejected | you, via |
An RPC endpoint | settlement | your own |
| Solana reads for the chain-data tools | your own key |
| scrape backend for the web tools | separate public repo; those tools are unavailable without it |
Postgres | intelligence store for the intel tools | your own |
No tool calls a RugMunch host. Every upstream is a URL you configure, and a tool whose upstream is unset fails rather than falling back to ours.
What it does
Paid MCP tools. Each tool declares a price; the server issues the x402 challenge, verifies the payment header, and only then runs the handler.
Bundled facilitator.
coffer/settles payments and keeps receipts in Redis, so a replay of the same payment header is rejected.Tool families. Chain data (
data_mcp_evm,data_mcp_solana), intelligence (data_mcp_intel), web extraction (data_mcp_web) and infra status (data_mcp_infra) are separate modules over one registration point.Client SDK.
coffer_client/is what an agent-side caller uses: build the request, pay, retry, and check the receipt.
How it is put together
data_mcp_server.py MCP entry point, tool registration
data_mcp_*.py tool families
app/ x402 middleware, pricing, verification
coffer/ facilitator: verify, settle, receipts
coffer_client/ caller-side payment helper
tests/ includes bypass and replay casesConfiguration
Variable | Purpose |
| generic receiving address; a payment to anything else is rejected |
| per-network payees |
| settle through the bundled facilitator rather than an upstream one |
| signer and node for settlement |
| receipt store — without it replay protection is off |
| Solana RPC for the chain-data tools |
| scrape backend used by the web tools |
| intelligence store for the intel tools |
Prices and payee addresses are configuration, never hardcoded; a fork with a different payee is a config change.
Known limits
Settlement needs a funded payer and a reachable RPC. Testnet is the sane default while you integrate.
Receipt storage is Redis with no long-term archive; losing the keys loses the audit trail.
Tool prices are set by the operator. This repo does not ship a marketplace or discovery service.
The 402 flow assumes the client can sign. An agent without a wallet can only use the free tools.
Licence
MIT.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Pay-per-call DeFi and macro intel for AI agents. x402 USDC tools via streamable HTTP /api/mcp.
Pay-per-call ($0.005-$0.03 USDC) market, on-chain, and prediction-market data API for AI agents and trading bots via x402 — no signup, no API key. Remote MCP server, 28 tools: token security (honeypot/liquidity/counterfeit checks), Hyperliquid oracle-gap risk, kimchi premium, funding APR, DEX slippage, Polymarket arbitrage/liquidity audits, Hyperliquid HIP-4 odds.
Remote MCP server exposing 330 production AI-agent services for web/data processing, validation, AI utilities, blockchain/crypto utilities, and x402 pay-per-use access.
Parallel Solana token risk and transaction safety for AI agents. Paid MCP tools inspect tokens and unsigned transactions; the HTTP risk panel queries compatible advisors in parallel and returns an indicative consensus. x402-compatible clients pay USDC automatically, with no signup or API key.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes T54 x402 seller SKUs from OpenAPI as tools: contract triage, audit, and monitoring plus T54 commerce tools. HTTP 402 invoices are paid via x402_broker_client (XRPL / Base USDC depending on env); stdio for Cursor/Claude, Streamable HTTP for hosted use.-
- AlicenseNot gradedqualityFmaintenanceLocal stdio MCP server for x402-powered paid crypto intelligence, decision verification, and agent automation search over USDC micropayments on Base.707 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.MIT
- FlicenseNot gradedqualityDmaintenanceProduction-grade Model Context Protocol (MCP) server delivering paywalled Web3 micro-services powered by autonomous x402 payment challenges on Base Mainnet.-