Status
MCP v0 is implemented locally in packages/rugburn-mcp. It is intended for frontier testing against the same public API contract used by developers.
API contract -> API keys -> quotas -> OpenAPI -> MCP v0 -> x402Run Locally
cd packages/rugburn-mcp
RUGBURN_API_KEY=rbn_live_xxx node src/server.mjsThe server speaks MCP over stdio. It is not an HTTP server, and it should be launched by an MCP-compatible client.
Client Config
{
"rugburn": {
"command": "node",
"args": ["./packages/rugburn-mcp/src/server.mjs"],
"env": {
"RUGBURN_API_BASE_URL": "https://rugburn.io",
"RUGBURN_API_KEY": "${RUGBURN_API_KEY}"
}
}
}Tools
screen_token(address)callsPOST /api/v1/token/risk.screen_wallet(walletAddress)callsPOST /api/v1/wallet/risk.explain_score(address, kind)returns a compact token or wallet explanation plus the raw API response.get_deployer_history(wallet)callsGET /api/v1/deployer/:wallet/history.
Environment
RUGBURN_API_BASE_URL=https://rugburn.io
RUGBURN_API_KEY=rbn_live_...
RUGBURN_MCP_TIMEOUT_MS=20000The MCP package must never require Supabase keys, service-role keys, database credentials, Helius keys, or worker internal secrets.
Safety Boundary
MCP returns RugBurn risk-screening evidence for agents. It is not financial advice, not a legal compliance determination, and not permission for an agent to trade, block users, or make irreversible decisions without operator review.
x402 Position
x402 remains a later payment rail for paid agent calls. It can sit beside API keys and quotas, but it does not replace account identity, entitlement checks, billing logs, or abuse controls.