Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@RMI MCP + x402 Gateway check the risk score for token 0x6982f5f3c8e4b1d6a9c7e2f0b8a4d1c3e5f7a9b2"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Model Context Protocol (MCP) server and x402 payment gateway for Rug Munch Intelligence. Exposes typed RMI crypto-security tools to AI agents and settles per-call x402 payments — so agents can discover, pay for, and consume token-risk and wallet-intelligence tools without learning a bespoke API.
Status: Beta / active development. Tool schemas and payment flow are stable; see Honest status for what is and isn't live.
This repo is the MCP-facing edge of the Rug Munch Intelligence platform:
MCP server — typed tools over streamable HTTP / stdio, consumable from Claude Code, opencode, Cursor, or any MCP-capable agent.
x402 gateway — gates premium tool calls behind per-request crypto micropayments, delegating verification and settlement to a self-hosted facilitator (see below).
Verified badge domain — the badge logic for verified RMI listings.
It is not the scanning engine (that lives in rmi-backend) or the wallet
generator (that lives in walletpress).
Related MCP server: coinopai-mcp
The gateway publishes a typed catalog (app/mcp/server.py). Core tools:
Tool | Purpose |
| 0–100 token risk score with category breakdown |
| Wallet forensics: holdings, counterparties, labels |
| Deployer history and reputation signals |
| News and social sentiment for an asset |
| Structured investigation report |
| Search the tool/asset catalog |
| Similarity lookup across indexed tokens |
The stdio surface (mcp_stdio.py) exposes the catalog over
fastmcp run mcp_stdio.py:mcp.
The gateway does not verify payments in-house. It delegates verification
and settlement to a self-hosted x402-coffer
facilitator over HTTP. Coffer is the source of truth for whether a payment is
real; the gateway's X-Payment-ID gate fails closed when coffer cannot be
reached.
Setting | Default | Meaning |
|
| Base URL of the coffer deployment |
Endpoints the gateway calls on coffer:
Gateway call | Coffer endpoint | Purpose |
payment re-check |
| Confirm an |
settlement |
| Settle a verified payment |
Fail-closed contract: a payment-gated call is allowed through only when
coffer answers verified: true. If coffer is unreachable, times out, or
returns 5xx after bounded retries, the gateway answers 402 Payment Required
— it never falls back to allowing the call through unverified. The gateway's
local payment store is caller/tx memory only; it cannot self-verify.
Agent (MCP client)
│ tools/list, tools/call
▼
rmi-mcp-x402 gateway ──── app/mcp/ MCP server, tool catalog, tool manager
│ ├── app/domain/x402/ payment middleware, models, service
│ ├── app/domain/verified/ badge domain
│ └── app/api/v1/ HTTP API routes
│ verify / settle (HTTP)
▼
x402-coffer (self-hosted facilitator)
│
▼
RMI backend (security data) · Qdrant · Redis · Postgres# Install (editable)
make install
# Run the MCP server (streamable HTTP, :8001)
make dev
# Run the x402 facilitator locally (:8001)
make run
# Full stack: coffer + redis via Docker Compose
make upRun make help for all targets. Quality gates: make lint, make typecheck,
make test, make security, and make ci (ruff + mypy + pytest).
Wallets resolve from the environment only — there are no hardcoded wallet
defaults. Unset resolves to "" and the deployment fails closed:
load_settings() raises at boot and the app refuses to serve an unconfigured
402.
Env var | Chain | Purpose |
| EVM — default payee for all | Receiving address |
| Solana ( | Receiving address |
| TRON ( | Receiving address |
| — | Coffer facilitator base URL |
| — | Payment nonce / replay store |
Per-network EVM overrides: X402_WALLET_BASE / _ETH / _ARBITRUM /
_OPTIMISM / _POLYGON (fall back to X402_WALLET). Old names are honored
as read-time aliases only.
We do not overclaim. Scaffolded paths are never reported as verified:
TRON is structural work only — shape, price, and asset are validated,
and health reports tron=scaffolded:needs_facilitator until a real
facilitator implementation is registered.
Verifying is not settling. Self-verify paths read on-chain receipts only
and fail closed with needs_facilitator rather than fabricating a settlement.
A bare HTTP-200 is not proof of payment — an explicit verification or settlement signal is required before reporting success.
docs.cryptorugmunch.com/rmi-mcp-x402 — product docs
docs/X402-SPEC-CONTRACT.md — x402 conformance contract
ARCHITECTURE.md — module layering and the 402 flow
CONTRIBUTING.md — how to add a tool or a network
Repo | Purpose |
Self-hosted x402 payment facilitator | |
Intelligence engine and data APIs | |
Web dashboard | |
Wallet management |
MIT — see LICENSE. Built by Rug Munch Media LLC.
This server cannot be deployed
Pay-per-call ($0.005–$0.03 USDC) market, on-chain, and prediction-market data API for AI agents and trading bots via the x402 protocol — no signup, no API key. Exposed as a remote MCP server with 15 tools: pre-trade token security (honeypot/liquidity checks), kimchi premium, funding rate APR, DEX slippage, Polymarket arbitrage & liquidity audits, and Hyperliquid HIP-4 prediction-market odds.
Pay-per-call DeFi and macro intel for AI agents. x402 USDC tools via streamable HTTP /api/mcp.
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.
