Whmcs MCP Server
whmcs-mcp-server
npm
v1.3.1
Published by not-sure-w — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Model Context Protocol server for WHMCS — automate your hosting business with AI agents. 60+ tools for client, ticket, product, invoice, order, and domain management.
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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
medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003
In the server's implementation (`dist/index.js:4914`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch("https://registry.npmjs.org/whmcs-mcp-server/latest", { signal: controller.signal
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
Tools 74
Each tool and what it can reach — statically extracted from the published source.
whmcs_send_emailnetwork egresswhmcs_accept_orderno sensitive capabilitywhmcs_add_clientno sensitive capabilitywhmcs_add_creditno sensitive capabilitywhmcs_add_invoice_paymentno sensitive capabilitywhmcs_add_orderno sensitive capabilitywhmcs_add_productno sensitive capabilitywhmcs_add_ticket_noteno sensitive capabilitywhmcs_add_transactionno sensitive capabilitywhmcs_add_userno sensitive capability
Show 64 more tools ↓
whmcs_cancel_orderno sensitive capabilitywhmcs_capture_paymentno sensitive capabilitywhmcs_create_invoiceno sensitive capabilitywhmcs_create_projectno sensitive capabilitywhmcs_delete_clientno sensitive capabilitywhmcs_delete_orderno sensitive capabilitywhmcs_delete_ticketno sensitive capabilitywhmcs_domain_get_lock_statusno sensitive capabilitywhmcs_domain_get_nameserversno sensitive capabilitywhmcs_domain_registerno sensitive capabilitywhmcs_domain_renewno sensitive capabilitywhmcs_domain_transferno sensitive capabilitywhmcs_domain_update_lock_statusno sensitive capabilitywhmcs_domain_update_nameserversno sensitive capabilitywhmcs_domain_whoisno sensitive capabilitywhmcs_fraud_orderno sensitive capabilitywhmcs_get_activity_logno sensitive capabilitywhmcs_get_announcementsno sensitive capabilitywhmcs_get_clientno sensitive capabilitywhmcs_get_client_creditsno sensitive capabilitywhmcs_get_client_domainsno sensitive capabilitywhmcs_get_invoiceno sensitive capabilitywhmcs_get_order_statusesno sensitive capabilitywhmcs_get_payment_methodsno sensitive capabilitywhmcs_get_productsno sensitive capabilitywhmcs_get_projectsno sensitive capabilitywhmcs_get_statsno sensitive capabilitywhmcs_get_support_departmentsno sensitive capabilitywhmcs_get_support_statusesno sensitive capabilitywhmcs_get_ticketno sensitive capabilitywhmcs_get_ticket_countsno sensitive capabilitywhmcs_get_ticket_notesno sensitive capabilitywhmcs_get_ticket_predefined_repliesno sensitive capabilitywhmcs_get_tld_pricingno sensitive capabilitywhmcs_get_todo_itemsno sensitive capabilitywhmcs_get_userno sensitive capabilitywhmcs_health_checkno sensitive capabilitywhmcs_list_clientsno sensitive capabilitywhmcs_list_invoicesno sensitive capabilitywhmcs_list_ordersno sensitive capabilitywhmcs_list_ticketsno sensitive capabilitywhmcs_list_transactionsno sensitive capabilitywhmcs_list_usersno sensitive capabilitywhmcs_module_change_packageno sensitive capabilitywhmcs_module_change_passwordno sensitive capabilitywhmcs_module_createno sensitive capabilitywhmcs_module_suspendno sensitive capabilitywhmcs_module_terminateno sensitive capabilitywhmcs_module_unsuspendno sensitive capabilitywhmcs_open_ticketno sensitive capabilitywhmcs_order_fraud_checkno sensitive capabilitywhmcs_pending_orderno sensitive capabilitywhmcs_refund_invoiceno sensitive capabilitywhmcs_reply_ticketno sensitive capabilitywhmcs_update_clientno sensitive capabilitywhmcs_update_client_domainno sensitive capabilitywhmcs_update_client_productno sensitive capabilitywhmcs_update_invoiceno sensitive capabilitywhmcs_update_productno sensitive capabilitywhmcs_update_projectno sensitive capabilitywhmcs_update_ticketno sensitive capabilitywhmcs_update_todo_itemno sensitive capabilitywhmcs_update_userno sensitive capabilitywhmcs_upgrade_productno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (74 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.3.1 latest |
A 96/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 whmcs-mcp-server --onlineMore in Business & CRM
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.