Cyberwarex Chain Data MCP server

CyberWareX MCP Servers

MCP (Model Context Protocol) servers for the CyberWareX suite — pay-per-call APIs built for AI agents. Every backing API is live, speaks x402 (HTTP 402 → pay USDC on Base → result), and needs no account and no API key: the first paid call is the entire onboarding.

Install

pip install mcp requests

Each server is a single self-contained file speaking MCP over stdio:

python web-access/mcp_server.py

Claude Desktop / Claude Code config

{
  "mcpServers": {
    "cyberwarex-web":    { "command": "python", "args": ["/path/to/cyberwarex-mcp/web-access/mcp_server.py"] },
    "cyberwarex-oracle": { "command": "python", "args": ["/path/to/cyberwarex-mcp/defi-oracle/mcp_server.py"] },
    "cyberwarex-chain":  { "command": "python", "args": ["/path/to/cyberwarex-mcp/chain-data/mcp_server.py"] },
    "cyberwarex-voice":  { "command": "python", "args": ["/path/to/cyberwarex-mcp/voice-stt/mcp_server.py"] }
  }
}

How payment works

These servers never hold keys and never pay. An unpaid tool call returns the x402 invoice (x402paymentrequired: true with the full accepts block) so the calling agent's x402 client can sign the gasless EIP-3009 USDC authorization and retry — either through the agent's own payment stack, or by setting the XPAYMENT env var with a pre-signed payment header.

Machine-readable catalog of everything: https://cyberwarex.com/.well-known/x402 (LLM-readable summary at /llms.txt).

Configuration (env vars)

Defaults point at the live public services — they work out of the box.

License

MIT — see LICENSE. Contact: x402@cyberwarex.com