mcp stdio server exposing mossgate trust and rue render apis with x402 usdc payment
a model context protocol (mcp) stdio server that exposes two live paid apis to any mcp-enabled agent:
https://api.mossgate.dev) token and wallet risk checkshttps://rue.mossgate.dev) url/html to pdf/png/jpegpayment is x402 v2, usdc on base. the operator who runs this server funds a wallet, and every tool call spends a little usdc from it. the wallet signs an eip-3009 authorization gaslessly, so it needs only usdc, no eth for gas.
token_verdict(address, chain=base) quick risk verdict for a token contractwallet_profile(address, chain=base) behavioural risk profile for a wallettoken_report(address, chain=base) full token reportrender(url|html, format=pdf|png|jpeg) render a page, returns a base64 filecd mcp-server
npm install
node 18+ is required.
0x833589fcd6edb6e08f4c7c32d4f71b54bda02913). a few dollars covers many
calls. no eth is needed, gas is sponsored by the facilitator.export MOSSGATE_BUYER_PK=0xyourprivatekey
optional overrides: MOSSGATE_RPC (base rpc url),
MOSSGATE_TRUST_URL, MOSSGATE_RENDER_URL.
MOSSGATE_BUYER_PK=0x... node index.js
the server speaks mcp over stdio. it is meant to be launched by an mcp client, not used by hand.
add this to your mcp client config (for claude desktop:
~/.config/Claude/claude_desktop_config.json on linux, or
~/Library/Application Support/Claude/claude_desktop_config.json on macos):
{
"mcpServers": {
"mossgate": {
"command": "node",
"args": ["/absolute/path/to/products/mcp-server/index.js"],
"env": {
"MOSSGATE_BUYER_PK": "0xyourprivatekey"
}
}
}
}
restart the client. the four tools appear and each call is paid automatically from the funded wallet.
this lists the tools over stdio without touching the apis or spending anything:
printf '%s\n' \
'{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' \
'{"jsonrpc":"2.0","method":"notifications/initialized"}' \
'{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
| node index.js
this package is on npm, so agents and clients can run it via npx with no
clone or install. set the command to npx and args to
["-y", "mossgate-mcp"] in the client config:
{
"mcpServers": {
"mossgate": {
"command": "npx",
"args": ["-y", "mossgate-mcp"],
"env": {
"MOSSGATE_BUYER_PK": "0xyourprivatekey"
}
}
}
}
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y mossgate-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"dev-mossgate-mossgate-mcp": {
"command": "npx",
"args": [
"-y",
"mossgate-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemossgate-mcpnpmdev.mossgate/mossgate-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.