🛡️ AEGIS MCP Server

The agent control plane for private, pay-per-request internet access

Give any AI agent its own privacy layer + payment rail — route HTTP through residential & datacenter exit nodes, pay per request in USDC on Solana, and govern its own budget and keys, all from inside Claude, Cursor, or any MCP client.

Website · Get an API key · Docs · X · Telegram

What is this?

AEGIS is privacy infrastructure for the open internet — a residential/datacenter proxy + VPN where humans and autonomous agents route traffic through operator-run exit nodes and pay per request in USDC, settled on Solana. No logs. No KYC.

This package exposes AEGIS as a Model Context Protocol server, so an agent can run its entire lifecycle without leaving the chat:

• 🌐 Fetch through a privacy node — hide the agent's origin IP, pick an exit country, choose residential / datacenter / mobile.

• 💸 Pay as it goes — ~$0.001 USDC per request from a prepaid balance, or auto‑settle on‑chain with pay‑and‑retry when the balance hits zero.

• 🔑 Govern its own budget — mint capped, geo/time‑scoped child keys for sub‑agent swarms (AP2‑style mandates), rotate and revoke them.

• 📊 Audit its own spend — usage, request history, live network stats, and (if it runs a node) earnings.

Every tool is a thin, audited wrapper over a public AEGIS REST endpoint. No secrets are baked in — you bring your own API key (and, optionally, a funded wallet) via environment variables.

Related MCP server: Apollo Proxy MCP Server

Quickstart

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "aegis": {
      "command": "npx",
      "args": ["-y", "@aegisprivacy/mcp"],
      "env": {
        "AEGIS_API_KEY": "aegis_your_key_here"
      }
    }
  }
}

Grab a key at aegisprivacy.org/agent, restart Claude, and ask it to "fetch example.com through a German residential node."

Cursor / other MCP clients

Point any MCP‑capable client at the same npx -y @aegisprivacy/mcp command with AEGIS_API_KEY in the environment.

Configuration

Spending is opt‑in. Without AEGIS_WALLET_SECRET, an empty balance simply surfaces a 402 with top‑up instructions — the agent can never spend on‑chain unless you hand it a funded wallet.

The toolbox (19 tools)

🌐 Routing

💸 Balance & cost

📡 Network

📊 Self‑audit

🔑 Key governance

⚙️ Operator (if you run a node)

Example prompts

"Use AEGIS to GET https://api.ipify.org through a residential node in Japan and tell me the exit IP."

"Mint a child key labeled scraper capped at $5 lifetime, locked to US datacenter, expiring in 24h — then show me the key tree."

"Estimate the cost of 2,000 requests, check my balance, and tell me if I can afford it."

How it works

  AI agent (Claude / Cursor)
        │  MCP (stdio)
        ▼
  @aegisprivacy/mcp  ──►  aegisprivacy.org  ──►  exit node (residential / datacenter)
        │   Bearer API key        x402 per‑request billing        │
        │                         metered in USDC                 ▼
        └── optional wallet ── 402? settle USDC on Solana ── retry & serve

The server holds no privileged state — it authenticates with your API key and (optionally) signs USDC settlements with your wallet. All billing, node selection, and metering happen server‑side on the AEGIS network.

Development

npm install
npm run build      # tsc → dist/
npm start          # run the stdio server

Requires Node ≥ 18.

License

MIT © AEGIS Privacy