WhoisJSON
NPM · @WHOISJSON/MCP-SERVER · SCANNED AUG 4
WHOIS, DNS, SSL, and domain availability lookups for AI assistants
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 117 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 341 tokens (~85/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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @whoisjson/mcp-server
claude mcp add whoisjson-mcp-server -- npx -y @whoisjson/mcp-server
codex mcp add whoisjson-mcp-server -- npx -y @whoisjson/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"whoisjson-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@whoisjson/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add whoisjson-mcp-server --command npx --arg -y --arg @whoisjson/mcp-server
mcp_servers:
whoisjson-mcp-server:
command: "npx"
args: ["-y", "@whoisjson/mcp-server"] {
"mcpServers": {
"whoisjson-mcp-server": {
"command": "npx",
"args": [
"-y",
"@whoisjson/mcp-server"
]
}
}
} 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.
- 4 Aug 26 +5
- Stability: unverified → 0.30 ▲ functional
- 3 Aug 26 +29
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
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 4 Aug 2026 · Analysed npm/@whoisjson/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
dns_lookup ~110
Query DNS records for a domain name. Returns all available record types including A (IPv4), AAAA (IPv6), MX (mail), NS (nameservers), TXT, CNAME, SOA, CAA, DMARC, BIMI, MTA-STS, and TLS-RPT records. Useful for diagnosing DNS configuration, verifying mail settings, or auditing domain infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to query, e.g. "example.com". Do not include protocol or path. |
No output schema declared.
No examples provided.
domain_availability ~63
Check whether a domain name is available for registration. Returns a boolean indicating if the domain is available. Useful for finding an unregistered domain before attempting to register it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name to check availability for (e.g. "example.com") |
No output schema declared.
No examples provided.
ssl_check ~90
Retrieve and validate the SSL/TLS certificate details for a domain. Returns the issuer, validity period (valid_from / valid_to), whether the certificate is currently valid, fingerprints, subject alternative names, and full certificate details. Useful for checking certificate expiry, verifying the issuer, or auditing TLS configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain name to check the SSL certificate for (e.g. "example.com") |
No output schema declared.
No examples provided.
whois_lookup ~78
Retrieve WHOIS registration data for a domain name. Returns registrar details, creation/expiration dates, nameservers, contact information, DNSSEC status, and domain age analysis. Useful for checking domain ownership and registration info.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up, e.g. "example.com". Do not include protocol or path. |
No output schema declared.
No examples provided.