Dominus Node
NPM · @DOMINUSNODE/MCP-SERVER
Relay network for AI agents: fetch via agent-contributed IPs, run a node and earn (alpha).
Available components
Last scanned (19 hours ago)
Scores higher than 46% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1113 tokens (~85/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "dominusnode_pay_crypto" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 2.1.0 → 2.2.0 functional
- 14 Nov 26 +1
- Stability: unverified → 0.07 ▲ functional
- Package version: 2.0.2 → 2.1.0 functional
- 13 Nov 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 12 Nov 26 44
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@dominusnode/mcp-server@2.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dominusnode_bootstrap_help ~35
Shows how to get started with Dominus Node. Use this if you're running in bootstrap mode without an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dominusnode_check_payment ~56
Check the status of a cryptocurrency payment invoice. Returns current payment status (pending, confirming, confirmed, finished, failed, expired).
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Invoice ID (UUID) from dominusnode_pay_crypto |
No output schema declared.
No examples provided.
dominusnode_create_agent_secret ~108
Generate 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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Human-readable label for the agent secret |
No output schema declared.
No examples provided.
dominusnode_get_account_info ~25
Get account details including email, admin status, and email verification.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dominusnode_network_policy ~110
Get 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dominusnode_network_pricing ~95
Get 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dominusnode_network_stats ~69
Get 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dominusnode_pay_crypto ~145
Create 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Amount in USD to add to wallet (min $5, max $1000) |
| currency | string | yes | Cryptocurrency to pay with (BTC, ETH, LTC, XMR, ZEC, USDC, SOL, USDT, DAI, BNB, LINK) |
No output schema declared.
No examples provided.
dominusnode_register_wallet ~93
Submit 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your Ethereum wallet address (0x...) |
| signature | string | yes | The EIP-191 signature of the challenge message |
No output schema declared.
No examples provided.
dominusnode_status ~64
Get 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dominusnode_wallet_challenge ~85
Request 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your Ethereum wallet address (0x...) |
No output schema declared.
No examples provided.
dominusnode_wallet_setup ~166
Sign 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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Your Ethereum wallet address (0x...). Optional with DOMINUSNODE_WALLET_KEY_FILE. |
| key_label | string | – | Label for the API key |
| signature | string | – | The EIP-191 signature of the challenge message. Omit to sign with DOMINUSNODE_WALLET_KEY_FILE. |
No output schema declared.
No examples provided.
dominusnode_x402_info ~62
Public: 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Dominus Node MCP server?
Dominus Node runs locally as an npm package, launched with npx -y @dominusnode/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @dominusnode/mcp-server
claude mcp add 0xcircuitbreaker-dominusnode -- npx -y @dominusnode/mcp-server
What is the Dominus Node MCP server?
Dominus Node is an MCP server listed in the public MCP registry as io.github.0xcircuitbreaker/dominusnode. Relay network for AI agents: fetch via agent-contributed IPs, run a node and earn (alpha). This page covers its npm package (@dominusnode/mcp-server).
Is the Dominus Node MCP server safe to use?
Dominus Node scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Dominus Node MCP server expose?
Dominus Node exposes 13 tools: dominusnode_get_account_info, dominusnode_create_agent_secret, dominusnode_pay_crypto, dominusnode_check_payment, dominusnode_wallet_challenge, and 8 more. Their descriptions and schemas cost roughly 1,113 tokens of context every time the server is loaded.
Is the Dominus Node MCP server still maintained?
Dominus Node is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Dominus Node MCP server under?
Dominus Node declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Dominus Node MCP server?
VerifyMCP ran 16 checks on Dominus Node, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.