Server data from the Official MCP Registry
Relay network for AI agents: fetch via agent-contributed IPs, run a node and earn (alpha).
About
Relay network for AI agents: fetch via agent-contributed IPs, run a node and earn (alpha).
Security Report
Valid MCP server (3 strong, 3 medium validity signals). 2 known CVEs in dependencies (1 critical, 0 high severity) ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
15 files analyzed · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: DOMINUSNODE_API_KEY
Environment variable: DOMINUSNODE_PROXY_URL
Environment variable: DOMINUSNODE_PROXY_CA_FILE
Environment variable: DOMINUSNODE_ALLOW_LOCAL_GATEWAY
Environment variable: DOMINUSNODE_PROXY_INSECURE
Environment variable: DOMINUSNODE_WALLET_KEY_FILE
Environment variable: DOMINUSNODE_NODE_KEY_FILE
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@dominusnode/mcp-server"
],
"env": {
"DOMINUSNODE_API_KEY": "your-dominusnode-api-key-here",
"DOMINUSNODE_PROXY_URL": "your-dominusnode-proxy-url-here",
"DOMINUSNODE_NODE_KEY_FILE": "your-dominusnode-node-key-file-here",
"DOMINUSNODE_PROXY_CA_FILE": "your-dominusnode-proxy-ca-file-here",
"DOMINUSNODE_PROXY_INSECURE": "your-dominusnode-proxy-insecure-here",
"DOMINUSNODE_WALLET_KEY_FILE": "your-dominusnode-wallet-key-file-here",
"DOMINUSNODE_ALLOW_LOCAL_GATEWAY": "your-dominusnode-allow-local-gateway-here"
}
}
}
}Some servers take additional arguments. See the repository for details.
Documentation
View on GitHubFrom the project's GitHub README.
DominusNode
DominusNode is a bandwidth relay network for AI agents: an agent-contributed exit network with an operator-run gateway (federation planned). Agents do two things on it:
- Buy bandwidth. They send HTTP, HTTPS or SOCKS5 traffic through the gateway and pay per GB, or per request with x402 or MPP.
- Contribute IPs. They run the node agent on a residential, mobile or datacenter connection and earn a share of the paid traffic that exits through it.
The network has no third-party IP upstream. Every exit is a node run by an agent. The gateway alone counts billable bytes, and exit nodes are treated as untrusted. Humans use the platform only as admins.
How it works
requester agent ──HTTP/CONNECT/SOCKS5──▶ gateway ──tunnel (wss, TLS 1.3, pinned)──▶ node-agent ──▶ target
(API key or x402/MPP) meter, select node, SSRF floor, port
settle split policy, caps
- HTTPS stays end-to-end TLS between the requester and the origin. Plain HTTP is refused unless the requester sets
allowhttp-1, because the exit can read it. - Node selection excludes self-dealing (same owner, wallet, team or /24) and applies per-IP, per-/24 and per-ASN caps.
- Each settled charge is split between the node owner and the platform in integer micro-USD.
Pricing and earnings
Prices are per IP class and set by the admin in network_pricing. The defaults are:
| Class | Price per GB |
|---|---|
residential / mobile | $0.50 |
dc | $0.20 |
masked (VPN/WARP/Tor egress, opt-in) | $0.10 |
Node owners earn 25% (Probation) to 50% (Partner) of what their nodes carry. The tier depends on paid tenure, uptime, active IPs and reputation. Credits mature after a 3–14 day hold. Today you can convert matured credits into bandwidth; USDC withdrawals are built but disabled in alpha (PAYOUTS_DISABLED). See docs/agent-network/ECONOMICS.md.
Paying
- x402 and MPP (Tempo): pay per request inside the HTTP 402 flow, with no account needed.
- Tempo and NOWPayments crypto: prepaid wallet top-ups.
- Stripe and PayPal exist only for admin operations. Agents never see them.
See docs/agent-network/PAYMENTS.md.
Using the proxy
The API key goes in the password field. The username holds hyphen-joined flags:
| Flag | Meaning |
|---|---|
country-XX | Exit country (OFAC countries CU, IR, KP, RU and SY are refused) |
class-residential / class-dc / class-mobile / class-masked | IP class. masked (VPN/WARP/Tor egress) is the cheapest and opt-in: unflagged requests never use it |
session-<id> | Sticky session |
allowhttp-1 | Allow plaintext HTTP (the exit can read it) |
With no flags, use relay.
Use the TLS proxy on port 8443 so your API key never crosses the network in clear:
# Recommended: HTTPS proxy (credentials sent over TLS)
curl -x https://country-US-class-residential:$DOMINUSNODE_API_KEY@proxy.dominusnode.com:8443 https://httpbin.org/ip
curl -x https://relay:$DOMINUSNODE_API_KEY@proxy.dominusnode.com:8443 https://httpbin.org/ip
Ports 8080 (HTTP proxy) and 1080 (SOCKS5) are plaintext: the
Proxy-Authorization header, including your API key, is readable on the path to
the gateway. The hosted gateway refuses credentials on plaintext and accepts them
only on the TLS proxy at :8443. Use 8080/1080 only against a gateway you run
yourself, for local development:
# Plaintext listeners on a local gateway (API key sent in clear)
curl -x http://class-dc:$DOMINUSNODE_API_KEY@localhost:8080 https://httpbin.org/ip
curl -x socks5h://class-dc-session-abc123:$DOMINUSNODE_API_KEY@localhost:1080 https://httpbin.org/ip
Get an API key
Agents sign in with a wallet; there is no email/password signup.
POST https://dominusnode.com/api/auth/wallet/challengewith{"address": "0x…"}→{message, nonce, expiresAt}.- Sign
messageexactly as returned with EIP-191personal_sign, thenPOST /api/auth/wallet/verifywith{"address", "signature"}→{token, refreshToken, user}. POST /api/keyswithAuthorization: Bearer <token>and{"label": "my-agent"}→ thedn_live_…key, shown once. Store it inDOMINUSNODE_API_KEY.
The SDKs and the MCP server wrap these steps. Or skip the key: pay per request with x402 or MPP.
Troubleshooting
| You see | Meaning | Fix |
|---|---|---|
407 Proxy Authentication Required | No or invalid credentials | Put the dn_live_ key in the proxy password field; username is flags or relay |
402 Payment Required (INSUFFICIENT_BALANCE) | Authenticated, but the wallet cannot cover the reservation | Top up (crypto) or claim starter credits; or pay per request with x402/MPP from the 402 body |
503 NO_NODES_AVAILABLE | No eligible exit node for your flags (country, class, sticky session) | Loosen country-/class- flags or retry later; GET /v1/network/stats shows what is online |
503 QUOTE_CLASS_MISMATCH | An x402/MPP payment was quoted for a class no node could serve | Request a new quote, or drop the class flag |
503 PAYOUTS_DISABLED | USDC withdrawals are disabled in alpha | Convert credits into bandwidth (POST /v1/credits/convert) |
400 PLAINTEXT_DISABLED (plain http:// target) | The exit node could read plaintext HTTP | Use https:// targets, or add allowhttp-1 if you accept that |
| Warning about credentials over plaintext | You used port 8080/1080 | Switch to the TLS proxy on 8443 |
Tooling for agents
- MCP server (packages/mcp-server): 66 tools, plus 13 bootstrap tools, for relay fetch, nodes, earnings and wallets.
- SDKs v2 (sdks/): Node.js, Python, Go, Rust, Java and C++. They share one contract in sdks/SDK_SURFACE.md.
- 27 framework integrations (integrations/): LangChain, CrewAI, LlamaIndex, Vercel AI, Mastra, n8n and others. All of them expose the same 19-tool set.
- Node agent (packages/node-agent): the
dominusnode-nodebinary for contributing an IP.
Repository layout
| Path | Purpose |
|---|---|
packages/shared | Types, DB, auth, schema, repositories |
packages/proxy-gateway | Relay gateway and node tunnel coordinator |
packages/node-agent | Exit node agent |
packages/metering | Usage and cost calculation |
packages/billing | Payment rails |
packages/dashboard | REST API (/v1 agent routes, /api, admin) |
packages/mcp-server | MCP server |
packages/frontend | Admin dashboard (React) |
packages/extension | Browser extension |
docs/agent-network/ | Design, economics, payments, APIs, abuse controls, deployment |
Development
docker compose up -d # PostgreSQL
npm install
npm run build
npm run db:migrate
npx vitest run
npm run start:api # :3000
npm run start:proxy # :8080 HTTP, :1080 SOCKS5, node tunnel
Local demo (2 minutes)
DEMO, NOT FOR PRODUCTION. One command starts Postgres, the API, the gateway, one local exit node and a pre-funded demo principal with throwaway keys. Everything binds to 127.0.0.1, runs with NODE_ENV=development, and the node uses a plaintext tunnel that only demo mode allows.
docker compose -f docker-compose.demo.yml up --build -d
KEY=$(docker compose -f docker-compose.demo.yml exec -T api cat /demo/api-key)
curl -x "http://relay:$KEY@localhost:8080" https://example.com
curl -s localhost:3000/v1/network/stats
docker compose -f docker-compose.demo.yml down -v # throw it all away
Self-host (one command)
./scripts/selfhost/install.sh
It asks for one or more public hostnames (the first is the primary DOMINUSNODE_DOMAIN; all of them are served), the role (ROLE: all, coordinator, or gateway for a separate gateway VPS over WireGuard), the TLS mode (auto, internal, off, cloudflare), an operator contact and an optional first admin email (ADMIN_BOOTSTRAP_EMAIL; the admin UI is served at your domain). It generates the coordinator key, a .env with random secrets and selfhost/Caddyfile, then starts docker-compose.selfhost.yml. Re-run it to upgrade; existing secrets and the key are kept. Non-interactive: DOMINUSNODE_HOSTNAMES="a.example b.example" TLS_MODE=auto OPERATOR_CONTACT=ops@example ./scripts/selfhost/install.sh --yes. Back up with scripts/selfhost/backup.sh (database, keys and .env, encrypted); see DEPLOYMENT.md "Self-host backup".
For production setup (coordinator signing key, SPKI pins, ASN database and tunnel ingress), see docs/agent-network/DEPLOYMENT.md. For the architecture overview, see ARCHITECTURE.md.
License
MIT. See LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
