com.mambabuilt/mcp-whois-domain-lookup
NPM · @MAMBALABSDEV/MCP-WHOIS-DOMAIN-LOOKUP
Registrar, created and expiry dates, domain age, and nameservers per domain, from RDAP and WHOIS
Available components
Last scanned (3 hours ago)
Scores higher than 30% of npm servers
Category Search and Retrieval
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 Security48
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 325 tokens (~325/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.0 → 1.0.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 69
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/@mambalabsdev/mcp-whois-domain-lookup@1.0.1
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
lookup_domain_whois Look up domain WHOIS and RDAP records ~325
Look up who registered a domain, when, and when it expires. Give domains, website URLs, or email addresses (up to 5,000). For each registrable domain the actor asks the registry's own RDAP server (from the IANA list), or its port 43 WHOIS server where there is no RDAP, and returns one row: registered true or false, registrar, created_at, updated_at, expires_at, domain_age_days, days_until_expiry, status codes, nameservers, dnssec, and the registrant organization and country where the registry publishes them. Rows with no dates published, error rows, and input that is not a domain come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per domain lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | One domain, URL, or email address, for example stripe.com. |
| domains | array | – | Domains, website URLs, or email addresses, up to 5,000. Subdomains are looked up as their registrable domain. |
| follow_registrar_rdap | string | – | true (default) also reads the registrar's RDAP record for the abuse email and any registrant details it publishes. |
| include_raw | string | – | true puts the registry's raw RDAP JSON or WHOIS text in raw_response. Default false. |
| max_charge_usd | string | – | Optional. The run stops before a charge would pass this amount. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-whois-domain-lookup server?
com.mambabuilt/mcp-whois-domain-lookup runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-whois-domain-lookup. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-whois-domain-lookup
claude mcp add com-mambabuilt-mcp-whois-domain-lookup -- npx -y @mambalabsdev/mcp-whois-domain-lookup
What is the com.mambabuilt/mcp-whois-domain-lookup server?
com.mambabuilt/mcp-whois-domain-lookup is listed in the public MCP registry as com.mambabuilt/mcp-whois-domain-lookup. Registrar, created and expiry dates, domain age, and nameservers per domain, from RDAP and WHOIS. This page covers its npm package (@mambalabsdev/mcp-whois-domain-lookup).
Is the com.mambabuilt/mcp-whois-domain-lookup server safe to use?
com.mambabuilt/mcp-whois-domain-lookup scores 56 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. 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 com.mambabuilt/mcp-whois-domain-lookup server expose?
com.mambabuilt/mcp-whois-domain-lookup exposes 1 tool: lookup_domain_whois. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-whois-domain-lookup server still maintained?
com.mambabuilt/mcp-whois-domain-lookup 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 com.mambabuilt/mcp-whois-domain-lookup server under?
com.mambabuilt/mcp-whois-domain-lookup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.