Whoisxml
NPM · @PIPEWORX/MCP-WHOISXML · 2 COMPONENTS
WhoisXML MCP — wraps WhoisXML API (whoisxmlapi.com)
Available components
Last scanned (9 hours ago)
Scores higher than 87% of npm servers
Category Security
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-whoisxml). View diagnostics → Pass
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 472 tokens (~118/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 81
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-whoisxml@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-whoisxml |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-whoisxml/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561087781 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f9f9a1a40504f21f119899a88525700fdddab99b69b7efd3827239881d8d7e8ffa88293bc72b890f963a1d13d99ed41097a09c4e36bf0d517008a6ea4 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
whoisxml_dns ~94
DNS records for <domain> — A, AAAA, MX, NS, TXT, and other records with their values and TTLs. Example: whoisxml_dns({ domain: "google.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | WhoisXML API key |
| domain | string | yes | Domain name to resolve DNS records for, e.g. "google.com" |
No output schema declared.
No examples provided.
whoisxml_reverse_whois ~112
Find domains registered by <email/name/org> — reverse WHOIS lookup returning every domain whose current WHOIS record contains the search term. Example: whoisxml_reverse_whois({ term: "admin@google.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | WhoisXML API key |
| term | string | yes | Registrant email, name, or organization to search for, e.g. "admin@google.com" or "Google LLC" |
No output schema declared.
No examples provided.
whoisxml_whois ~113
Current WHOIS for <domain> — registrar, creation/expiry dates, registrant org, name servers, and status. Example: whoisxml_whois({ domain: "google.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | WhoisXML API key (get one at whoisxmlapi.com — one key works across all products) |
| domain | string | yes | Domain name to look up, e.g. "google.com" (no protocol) |
No output schema declared.
No examples provided.
whoisxml_whois_history ~98
Historical WHOIS records for <domain> — past registrars, registrants, and creation/expiry dates over time. Example: whoisxml_whois_history({ domain: "google.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | WhoisXML API key |
| domain | string | yes | Domain name to look up historical WHOIS for, e.g. "google.com" |
No output schema declared.
No examples provided.
How do I install the Whoisxml MCP server?
Whoisxml runs locally as an npm package, launched with npx -y @pipeworx/mcp-whoisxml. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-whoisxml
claude mcp add pipeworx-io-whoisxml -- npx -y @pipeworx/mcp-whoisxml
What is the Whoisxml MCP server?
Whoisxml is an MCP server listed in the public MCP registry as io.github.pipeworx-io/whoisxml. WhoisXML MCP, wraps WhoisXML API (whoisxmlapi.com). This page covers its npm package (@pipeworx/mcp-whoisxml).
Is the Whoisxml MCP server safe to use?
Whoisxml scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Whoisxml MCP server expose?
Whoisxml exposes 4 tools: whoisxml_whois, whoisxml_whois_history, whoisxml_reverse_whois, whoisxml_dns. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.
Is the Whoisxml MCP server still maintained?
Whoisxml is still listed as active in the MCP registry. We last reached this channel on 5 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 Whoisxml MCP server under?
Whoisxml declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.