Lets AI agents fetch web content through a decentralized relay network and earn rewards by contributing their own IP addresses.
Also known as 0xcircuitbreaker/DomiNode, dominusnode, @dominusnode/mcp-server
- Stars
- 0
- Tools
- 13
- Downloads, 30 days
- 704
- Latest version
- 2.2.0
- Last commit
- Nov 14, 2026
- License
- MIT
What is Dominus Node MCP?
Dominus Node lets AI agents fetch web content through a decentralized relay network and earn rewards by contributing their own IP addresses. It exposes 13 tools, such as dominusnode_get_account_info, dominusnode_create_agent_secret, dominusnode_pay_crypto.
Summary generated from the project's README
About Dominus Node MCP server
Fetching web content through a decentralized relay network is what Dominus Node enables for AI agents. This MCP server allows users to route requests through various IP classes, including residential, data center, and mobile, to access web data. It is designed for developers using clients like Claude Desktop, Cursor, or VS Code, and can be integrated into frameworks such as LangChain or elizaOS.
Beyond simple fetching, the server provides a way for node operators to earn rewards by contributing their own IP addresses to the network. Users can manage their participation through tools like dominusnode_node_register and monitor their earnings with dominusnode_credits_balance. The system operates in two modes: a bootstrap mode with 12 tools for initial setup and an authenticated mode with 65 tools for full network interaction. To access authenticated features, a DOMINUSNODE_API_KEY must be provided in the environment variables.
Written from the project's README. Every use case is checked against a quote from it.
How to install Dominus Node MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Dominus Node MCP in Claude Code
$ claude mcp add --env 'DOMINUSNODE_API_KEY=<YOUR_DOMINUSNODE_API_KEY>' dominusnode -- npx -y @dominusnode/mcp-serverInstall Dominus Node MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"dominusnode": {
"command": "npx",
"args": [
"-y",
"@dominusnode/mcp-server"
],
"env": {
"DOMINUSNODE_API_KEY": "<YOUR_DOMINUSNODE_API_KEY>"
}
}
}
}Install Dominus Node MCP in VS Code
.vscode/mcp.json
{
"servers": {
"dominusnode": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dominusnode/mcp-server"
],
"env": {
"DOMINUSNODE_API_KEY": "<YOUR_DOMINUSNODE_API_KEY>"
}
}
}
}Install Dominus Node MCP in VS Code CLI
$ code --add-mcp '{"name":"dominusnode","type":"stdio","command":"npx","args":["-y","@dominusnode/mcp-server"],"env":{"DOMINUSNODE_API_KEY":"<YOUR_DOMINUSNODE_API_KEY>"}}'Install Dominus Node MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"dominusnode": {
"command": "npx",
"args": [
"-y",
"@dominusnode/mcp-server"
],
"env": {
"DOMINUSNODE_API_KEY": "<YOUR_DOMINUSNODE_API_KEY>"
}
}
}
}Install Dominus Node MCP in Codex
$ codex mcp add dominusnode --env 'DOMINUSNODE_API_KEY=<YOUR_DOMINUSNODE_API_KEY>' -- npx -y @dominusnode/mcp-serverInstall Dominus Node MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.dominusnode] command = "npx" args = ["-y", "@dominusnode/mcp-server"] [mcp_servers.dominusnode.env] DOMINUSNODE_API_KEY = "<YOUR_DOMINUSNODE_API_KEY>"
Install Dominus Node MCP in Gemini CLI
$ gemini mcp add -s user -e 'DOMINUSNODE_API_KEY=<YOUR_DOMINUSNODE_API_KEY>' dominusnode npx -- -y @dominusnode/mcp-serverInstall Dominus Node MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"dominusnode": {
"command": "npx",
"args": [
"-y",
"@dominusnode/mcp-server"
],
"env": {
"DOMINUSNODE_API_KEY": "<YOUR_DOMINUSNODE_API_KEY>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @dominusnode/mcp-server 2.2.0 in an isolated container with no network and no keys. It answered and listed 13 tools.
Dominus Node MCP tools 13
Read from the server with tools/listdominusnode_get_account_infoGet account details including email, admin status, and email verification.
dominusnode_create_agent_secretGenerate a per-agent secret (das_...) that marks this agent's API requests as a verified agent, which raises its API rate limits. Set it as DOMINUSNODE_AGENT_SECRET for this MCP server (sent as X-DominusNode-Agent-Secret). It does not bypass brute-force protections. Max 5 active secrets per account; the oldest is revoked. Requires authentication. Shown only once.
dominusnode_pay_cryptoCreate a cryptocurrency payment invoice to top up your Dominus Node wallet. Supports BTC, ETH, LTC, XMR, ZEC, USDC, SOL, USDT, DAI, BNB, and LINK. Returns a payment address and amount. Privacy coins (XMR, ZEC) provide anonymous billing — no identity linked to payment.
dominusnode_check_paymentCheck the status of a cryptocurrency payment invoice. Returns current payment status (pending, confirming, confirmed, finished, failed, expired).
dominusnode_wallet_challengeRequest a signature challenge for wallet-based authentication. Send your Ethereum address to get a message to sign with your wallet (EIP-191 personal_sign: MetaMask, Coinbase Agentic Wallets, ethers.Wallet, viem, ...). Then call dominusnode_wallet_setup with the signature.
dominusnode_register_walletSubmit a signed challenge to authenticate with your wallet. Creates a new account if this wallet hasn't been seen before, or logs in to the existing account. Prefer dominusnode_wallet_setup, which also creates an API key and unlocks the full tool set.
dominusnode_wallet_setupSign in with a wallet and create an API key in one call; the full tool set is then unlocked in this session (no restart needed). Either pass address + signature of a challenge from dominusnode_wallet_challenge, or omit the signature when DOMINUSNODE_WALLET_KEY_FILE is configured: the server then requests the challenge and signs it with that key (it only signs the standard sign-in message).
dominusnode_network_policyGet the active relay network policy (GET /v1/policy, public): which destination ports nodes will dial (only 80/443, ever), plaintext HTTP mode (deny | opt_in via allowhttp-1 | allow), requester rate/spend limits, sanctioned countries, node defaults, the attestation text node operators sign, and the fixed node-floor guarantees (no private/loopback/metadata targets, no SMTP/SSH/RDP). Read this before fetching or registering a node.
dominusnode_network_pricingGet live relay pricing (GET /v1/pricing, public): the per-GB price requesters pay for each IP class (residential, dc, mobile), the share of that price paid to the node operator at each tier (Probation 25% up to Partner 50%), how long earnings take to mature, and the enabled payment rails. Prices are admin-set; never assume a fixed number.
dominusnode_network_statsGet aggregate relay network capacity (GET /v1/network/stats, public): nodes online in the last 5 minutes, by IP class and by country. Countries with fewer than 3 nodes are folded into 'other'. Use this to pick a country/class that has exits before fetching.
dominusnode_statusGet live network status (GET /v1/status, public): overall status, gateway and coordinator health, 24h/7d gateway availability, online node count and open incidents. Check this first when a fetch fails with no eligible node or the proxy is unreachable.
dominusnode_x402_infoPublic: how to pay per request with x402 (USDC) instead of a prepaid wallet. Shows whether x402 is ENABLED on this deployment, the facilitators/networks and receiving addresses, and how to use it with the relay gateway.
Show all 13 toolsShow fewer tools
dominusnode_bootstrap_helpShows how to get started with Dominus Node. Use this if you're running in bootstrap mode without an API key.
Configuration
DOMINUSNODE_API_KEYSecretdn_live_ API key. Omit to start in bootstrap mode (wallet sign-in tools only).
DOMINUSNODE_ALLOW_LOCAL_GATEWAYSet to 1 to allow a localhost or private-network gateway host (local demo or self-hosted gateway).
DOMINUSNODE_NODE_KEY_FILEWhere node registration writes the dn_node_ credential file.
DOMINUSNODE_PROXY_CA_FILEExtra PEM CA file for a privately issued gateway certificate.
DOMINUSNODE_PROXY_INSECURESet to 1 to use the plaintext gateway listener (API key sent in clear). Local development only.
DOMINUSNODE_PROXY_URLTLS gateway https://host[:port]. Default https://proxy.dominusnode.com:8443.
DOMINUSNODE_WALLET_KEY_FILEPath to a chmod-600 file holding the owner wallet key (node registration and withdrawals only).
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachable0xcircuitbreaker/dominode is public and reachablegithub.com/0xcircuitbreaker/dominode ↗Pass
- Package names this repository as its source@dominusnode/mcp-server names 0xcircuitbreaker/dominode as sourcenpmjs.com/package/@dominusnode/mcp-server ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/0xcircuitbreaker/dominode ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @dominusnode/mcp-serverPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@dominusnode/mcp-server
MCP (Model Context Protocol) server for the DominusNode relay network: AI agents fetch through IPs that other AI agents contribute, and earn by contributing their own.
Works with any MCP client (Claude Desktop, Claude Code, Gemini CLI, Codex CLI, Cursor, VS Code, elizaOS, LangChain MCP adapters, ...).
How the network works
- Requesters pay per GB relayed, priced by exit IP class (
residential,dc,mobile). Prices are admin-set and published atGET /v1/pricing; usedominusnode_network_pricingfor the live numbers (never hardcode them). - Node operators (agents running the node agent) receive their tier's share of each paid GB: Probation 25% up to Partner 50%. Tiers rise with paid tenure, uptime, active IPs and reputation (
dominusnode_node_tier). - Self-dealing earns nothing: traffic from you, your wallet, your team or your /24 is never routed to your own nodes, and settles with a zero node share if it is.
- Policy (
GET /v1/policy): nodes dial only ports 80/443; private, loopback, metadata and embedded-IPv4 ranges are always blocked; SMTP/SSH/RDP never. Plaintexthttp://is exit-visible and needs theallowhttp-1opt-in under the defaultopt_inpolicy.
Quick install
npm install -g @dominusnode/mcp-server # or run it on demand with npx, as below
Registry name: io.github.0xcircuitbreaker/dominusnode in the official MCP Registry.
{
"mcpServers": {
"dominusnode": {
"command": "npx",
"args": ["-y", "@dominusnode/mcp-server"],
"env": { "DOMINUSNODE_API_KEY": "dn_live_your_key_here" }
}
}
}
The same block works for Claude Desktop, Claude Code (.mcp.json), Gemini CLI, Codex CLI, Cursor and VS Code. Without DOMINUSNODE_API_KEY the server starts in bootstrap mode.
Bootstrap mode (no API key): 12 tools
| Tool | Purpose |
|---|---|
dominusnode_bootstrap_help |
How to get started |
dominusnode_wallet_challenge |
Get an EIP-191 message to sign with your wallet |
dominusnode_register_wallet |
Submit the signature (creates or logs in to a wallet account) |
dominusnode_wallet_setup |
Signature + API key in one call; unlocks the authenticated tools in the same session (no restart). With DOMINUSNODE_WALLET_KEY_FILE set, omit the signature and the server signs the standard sign-in message |
dominusnode_get_account_info |
Account details |
dominusnode_create_agent_secret |
Per-agent das_ secret |
dominusnode_pay_crypto / dominusnode_check_payment |
Crypto top-up and status (sign in first) |
dominusnode_x402_info |
Public: whether x402 pay-per-request is enabled and how to use it |
dominusnode_network_policy / dominusnode_network_pricing / dominusnode_network_stats |
Public network info |
Email/password registration, login and email verification are human flows (admin-only) and are not exposed.
Wallet sign-in is rate limited: 20 challenges and 5 failed verifications per hour per process; successful sign-ins do not count.
Authenticated mode: 65 tools
Relay fetch and proxy config
dominusnode_fetch: GET/HEAD through the HTTP proxy gateway (CONNECT tunnel for https, full-URL request for http). Options:country(country-XX),ip_class(class-residential|dc|mobile),session_id(session-<id>, sticky exit),allow_http(allowhttp-1). Client-side SSRF checks incl. DNS rebinding (every resolved IP is checked), ports 80/443 only, no redirects, 10MB cap, credentials scrubbed from errors. Responses over plaintext are flagged when the gateway sendsX-DominusNode-Exit-Visible: 1.dominusnode_get_proxy_config: endpoints, username flags, live pricing and policy for use with curl/SDKs.dominusnode_get_proxy_status,dominusnode_get_active_sessions
Network (public): dominusnode_network_policy, dominusnode_network_pricing, dominusnode_network_stats
Nodes (earning)
dominusnode_node_setup_guide: exact install/run steps for the node agentdominusnode_node_register_challenge: preview the attestation you will sign and the PoW difficultydominusnode_node_register: challenge, attestation (shared builder, must match the server's), PoW, EIP-191 signature with the wallet key read fromDOMINUSNODE_WALLET_KEY_FILE, thenPOST /v1/nodes. Thedn_node_key is written to a new 0600 file (DOMINUSNODE_NODE_KEY_FILE) and never shown; the tool returns the path.dominusnode_node_list,dominusnode_node_revoke,dominusnode_node_tierdominusnode_node_update_caps: lower a node's stream, GB/day or req/s caps (never above policy defaults)
Earnings and payouts (shapes: docs/agent-network/AGENT_API.md)
dominusnode_credits_balance,dominusnode_credits_transactions: pending/available credit, tier hold, tax status, ledgerdominusnode_credits_convert: available credit into your own requester wallet (idempotent)dominusnode_payout_wallet_get,dominusnode_payout_wallet_set: USDC payout address on Base. Signs a server challenge (rebuilt locally first) with the key inDOMINUSNODE_WALLET_KEY_FILE; a change also needs the current payout wallet's key inDOMINUSNODE_PAYOUT_WALLET_KEY_FILEand starts a 72h cooldown. Keys are never tool arguments.dominusnode_credits_withdraw: on-demand USDC payout (min $1, tier daily limit, fresh signature);503 PAYOUTS_DISABLEDwhile payouts are offdominusnode_payouts_list: your payouts with status and tx hashdominusnode_session_report: report a burned exit for one of your relay sessions (5 per node per day)
Wallet and payments: dominusnode_get_balance, dominusnode_get_forecast, dominusnode_get_transactions, dominusnode_pay_crypto, dominusnode_check_payment, dominusnode_x402_info
Agentic wallets: dominusnode_agent_wallet_create, _balance, _fund, _list, _freeze, _unfreeze, _delete, _transactions, dominusnode_update_wallet_policy
Usage and keys: dominusnode_get_usage, dominusnode_get_daily_usage, dominusnode_get_top_hosts, dominusnode_list_keys, dominusnode_create_key, dominusnode_revoke_key
Account: dominusnode_get_account_info, dominusnode_create_agent_secret, dominusnode_wallet_challenge, dominusnode_register_wallet, dominusnode_wallet_setup
Teams (17): dominusnode_create_team, dominusnode_list_teams, dominusnode_team_details, dominusnode_team_update, dominusnode_team_update_member_role, dominusnode_team_add_member, dominusnode_team_remove_member, dominusnode_team_fund, dominusnode_team_create_key, dominusnode_team_revoke_key, dominusnode_team_usage, dominusnode_team_list_members, dominusnode_team_invite_member, dominusnode_team_list_invites, dominusnode_team_cancel_invite, dominusnode_team_list_keys, dominusnode_team_delete. Team keys cannot call /v1 node endpoints.
Environment variables
| Variable | Default | Purpose |
|---|---|---|
DOMINUSNODE_API_KEY |
(none: bootstrap mode) | dn_live_ API key |
DOMINUSNODE_API_URL |
https://api.dominusnode.com |
API base URL |
DOMINUSNODE_PROXY_HOST |
proxy.dominusnode.com |
Gateway host |
DOMINUSNODE_PROXY_URL |
https://proxy.dominusnode.com:8443 |
TLS gateway (https://host[:port], default port 8443). Proxy fetches always use TLS to the gateway unless DOMINUSNODE_PROXY_INSECURE=1 |
DOMINUSNODE_PROXY_CA_FILE |
(none) | Extra PEM CA for a privately issued gateway certificate (verification stays on) |
DOMINUSNODE_PROXY_INSECURE |
(unset) | 1 = use the plaintext HTTP listener (DOMINUSNODE_HTTP_PROXY_PORT). The API key is then sent in clear; a warning is printed to stderr. Local development only |
DOMINUSNODE_HTTP_PROXY_PORT |
8080 |
Gateway plaintext HTTP/CONNECT port (used only with DOMINUSNODE_PROXY_INSECURE=1) |
DOMINUSNODE_SOCKS5_PROXY_PORT |
1080 |
Gateway SOCKS5 port |
DOMINUSNODE_FETCH_TIMEOUT_MS |
30000 |
Fetch timeout (max 120000) |
DOMINUSNODE_FETCH_MAX_RESPONSE_BYTES |
10485760 |
Fetch body cap (max 10MB) |
DOMINUSNODE_WALLET_KEY_FILE |
(none) | chmod-600 file with the linked wallet private key, for node_register, payout_wallet_set and credits_withdraw |
DOMINUSNODE_PAYOUT_WALLET_KEY_FILE |
(none) | chmod-600 file with the CURRENT payout wallet key, only to co-sign a payout-wallet change when it differs from the linked wallet |
DOMINUSNODE_NODE_KEY_FILE |
~/.dominusnode/node.json |
Where node_register writes the node credential file (never overwritten) |
DOMINUSNODE_AGENT_SECRET |
(none) | Shared agent secret (32+ chars) sent as X-DominusNode-Agent-Secret; MCP_AGENT_SECRET is accepted as an alias |
Every API request carries X-DominusNode-Agent: mcp.
Example: earn by contributing a node
dominusnode_network_policy # read ports, plaintext and attestation terms
dominusnode_network_pricing # live price per GB and tier shares
dominusnode_node_register_challenge # preview what you sign
dominusnode_node_register(accept_attestation: true)
# -> Node key file (mode 0600): /home/agent/.dominusnode/node.json
node packages/node-agent/dist/src/main.js run --key-file ~/.dominusnode/node.json
dominusnode_node_list / dominusnode_node_tier
Directory listings and Docker
The package carries the metadata the MCP directories need. This package is alpha: listings must say so, and must say payouts are not live.
| File | Used by | Notes |
|---|---|---|
package.json mcpName |
Official MCP Registry | io.github.0xcircuitbreaker/dominusnode; must equal name in server.json |
server.json |
Official MCP Registry (mcp-publisher publish) |
Current registry schema; npm package, stdio transport, env vars (DOMINUSNODE_API_KEY is marked secret) |
smithery.yaml |
Smithery | Local stdio server launched with npx -y @dominusnode/mcp-server |
Dockerfile |
Docker MCP Catalog, self-hosting | Multi-stage node:22-alpine, runs as the unprivileged node user, no secrets in the image |
Publish to the registry (after npm publish of the same version):
cd packages/mcp-server
mcp-publisher login github # as the 0xcircuitbreaker GitHub account
mcp-publisher publish # reads server.json
Keep version in package.json and both version fields in server.json in step on every release.
Docker:
docker build -t dominusnode-mcp packages/mcp-server
docker run -i --rm -e DOMINUSNODE_API_KEY dominusnode-mcp
# node registration / withdrawals: mount the wallet key read-only
docker run -i --rm -e DOMINUSNODE_API_KEY \
-e DOMINUSNODE_WALLET_KEY_FILE=/run/secrets/wallet.key \
-v "$PWD/wallet.key:/run/secrets/wallet.key:ro" dominusnode-mcp
The API key is read from the environment at run time and never written to the image or to tool output.
Development
npm run build -w @dominusnode/shared -w @dominusnode/mcp-server
npx vitest run packages/mcp-server
License
MIT
Dominus Node MCP questions
How do I add Dominus Node MCP to Claude Code?
Run claude mcp add --env 'DOMINUSNODE_API_KEY=<YOUR_DOMINUSNODE_API_KEY>' dominusnode -- npx -y @dominusnode/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Dominus Node MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Dominus Node MCP provide?
It exposes 13 tools, including dominusnode_get_account_info, dominusnode_create_agent_secret, dominusnode_pay_crypto, dominusnode_check_payment, dominusnode_wallet_challenge.
How can I earn rewards with Dominus Node?
You can earn by running a node agent and contributing your IP addresses to the relay network, receiving a share of the paid traffic based on your tier.
What kind of web traffic is allowed through the proxy?
The network only allows traffic on ports 80 and 443, and specifically blocks private, loopback, metadata, and embedded-IPv4 ranges.
How is the pricing for relayed data determined?
Prices are set by the administrator and vary based on the exit IP class, such as residential, data center, or mobile.