Dominusnode MCP Server
@dominusnode/mcp-server
npm
v1.5.2
Published by @dominusnode — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Dominus Node MCP server — proxy tools for AI agents (Claude, Gemini, Codex, etc.)
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: dominusnode_fetch → dominusnode_list_keys → dominusnode_pay_stripe. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow dominusnode_fetch → dominusnode_list_keys → dominusnode_pay_stripe
Tools 67
Each tool and what it can reach — statically extracted from the published source.
dominusnode_fetchingests untrusted inputdominusnode_get_active_sessionsingests untrusted inputdominusnode_list_keysreads sensitive datadominusnode_pay_stripenetwork egressdominusnode_team_list_keysreads sensitive datadominusnode_agent_wallet_balanceno sensitive capabilitydominusnode_agent_wallet_createno sensitive capabilitydominusnode_agent_wallet_deleteno sensitive capabilitydominusnode_agent_wallet_freezeno sensitive capabilitydominusnode_agent_wallet_fundno sensitive capability
Show 57 more tools ↓
dominusnode_agent_wallet_listno sensitive capabilitydominusnode_agent_wallet_transactionsno sensitive capabilitydominusnode_agent_wallet_unfreezeno sensitive capabilitydominusnode_bootstrap_helpno sensitive capabilitydominusnode_change_planno sensitive capabilitydominusnode_check_paymentno sensitive capabilitydominusnode_check_slotsno sensitive capabilitydominusnode_create_agent_secretno sensitive capabilitydominusnode_create_keyno sensitive capabilitydominusnode_create_teamno sensitive capabilitydominusnode_get_account_infono sensitive capabilitydominusnode_get_balanceno sensitive capabilitydominusnode_get_daily_usageno sensitive capabilitydominusnode_get_forecastno sensitive capabilitydominusnode_get_planno sensitive capabilitydominusnode_get_proxy_configno sensitive capabilitydominusnode_get_proxy_statusno sensitive capabilitydominusnode_get_top_hostsno sensitive capabilitydominusnode_get_transactionsno sensitive capabilitydominusnode_get_usageno sensitive capabilitydominusnode_get_waitlist_countno sensitive capabilitydominusnode_join_waitlistno sensitive capabilitydominusnode_list_plansno sensitive capabilitydominusnode_list_teamsno sensitive capabilitydominusnode_loginno sensitive capabilitydominusnode_mpp_challengeno sensitive capabilitydominusnode_mpp_infono sensitive capabilitydominusnode_mpp_session_closeno sensitive capabilitydominusnode_mpp_session_openno sensitive capabilitydominusnode_pay_cryptono sensitive capabilitydominusnode_pay_mppno sensitive capabilitydominusnode_pay_paypalno sensitive capabilitydominusnode_registerno sensitive capabilitydominusnode_register_walletno sensitive capabilitydominusnode_resend_verificationno sensitive capabilitydominusnode_revoke_keyno sensitive capabilitydominusnode_setupno sensitive capabilitydominusnode_team_add_memberno sensitive capabilitydominusnode_team_cancel_inviteno sensitive capabilitydominusnode_team_create_keyno sensitive capabilitydominusnode_team_deleteno sensitive capabilitydominusnode_team_detailsno sensitive capabilitydominusnode_team_fundno sensitive capabilitydominusnode_team_invite_memberno sensitive capabilitydominusnode_team_list_invitesno sensitive capabilitydominusnode_team_list_membersno sensitive capabilitydominusnode_team_remove_memberno sensitive capabilitydominusnode_team_revoke_keyno sensitive capabilitydominusnode_team_updateno sensitive capabilitydominusnode_team_update_member_roleno sensitive capabilitydominusnode_team_usageno sensitive capabilitydominusnode_update_passwordno sensitive capabilitydominusnode_update_wallet_policyno sensitive capabilitydominusnode_verify_emailno sensitive capabilitydominusnode_wallet_challengeno sensitive capabilitydominusnode_wallet_setupno sensitive capabilitydominusnode_x402_infono sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (67 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.5.2 latest |
A 92/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @dominusnode/mcp-server --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.