Domains
NPM · @PIPEWORX/MCP-DOMAINS · 2 COMPONENTS
Domains MCP — domain registration lookup + availability search over live RDAP (ICANN standard…
Available components
Last scanned (2 hours ago)
Scores higher than 76% of npm servers
Category E-commerce
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-domains). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 859 tokens (~171/item across 5 items; 5 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 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.0 → 0.3.1 functional
- 31 Oct 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.
- 29 Oct 26 80
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-domains@0.3.1
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-domains |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-domains/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617562962 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:857607ec01263cea4ee93be7bf27e6573af92448b4458377e636723c18c8aa1510c8993ccc5d84062f64de9e7b1a6e39032c65b3ca642b3ce9931dc41 |
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 →
certificate_search ~198
Find the SSL/TLS certificates issued for a domain from public Certificate Transparency logs (Cert Spotter). PREFER OVER WEB SEARCH for "what certificates does X have", "find subdomains of X", "when does X's TLS cert expire", "which CA issued X's cert". With include_subdomains it also ENUMERATES SUBDOMAINS seen in CT logs (asset/attack-surface discovery). Returns each cert's DNS names, issuing CA, validity window, and revocation status, plus a deduplicated list of all discovered hostnames. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to search certificates for, e.g. "example.com". |
| include_subdomains | boolean | – | Also include certs covering subdomains (default true) — this is what enables subdomain discovery. |
| limit | number | – | Max certificates to list (1-100, default 30). The discovered-hostnames list is always complete. |
No output schema declared.
No examples provided.
check_availability ~213
Check whether a name is available to register across MULTIPLE TLDs at once — the domain-hunting tool. Pass a base name ("acme") and get .com/.io/.ai/.co/.net/.org/.app/.dev checked in one call (or pass your own tlds list). For each: available true/false (+ expiration if taken). Use for "is X available", "find an open domain for my project", "which TLDs is X free on". Single-domain detail is domain_status; this is the bulk/brainstorm version.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Base name to check, e.g. "acme" (a full "acme.com" is also accepted — the label before the first dot is used). |
| tlds | array | – | TLDs to check (without the dot), e.g. ["com","io","ai"]. Default: com, io, ai, co, net, org, app, dev. Max 15. |
No output schema declared.
No examples provided.
domain_lookup ~69
Get full registration details for a domain. Returns registrar, registrant, registration/expiration dates, nameservers, DNSSEC status, and domain status flags. Works for any TLD.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "google.com", "bbc.co.uk") |
No output schema declared.
No examples provided.
domain_status ~45
Quick check if a domain is registered or available. Returns registration status and expiration date if registered.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to check (e.g., "example.com") |
No output schema declared.
No examples provided.
find_available_domains ~283
Search for AVAILABLE domain names to register from a keyword — the domain name search / brainstorming tool. Pass a keyword ("acme") and get back which domains are actually free to register: the exact name across .com/.io/.ai/.co/.app/.dev, plus creative variations (getacme.com, acmehq.com, tryacme.io, acmeapp.com, …). Use for "find me an available domain for X", "domain name ideas for my startup", "is there an open domain for X", "suggest domain names". Returns available domains ranked (exact match + .com first). Availability is a live registry (RDAP) signal, keyless. For a single specific domain use domain_status; to check one name across TLDs without variations use check_availability.
| Name | Type | Req | Description |
|---|---|---|---|
| include_variations | boolean | – | Also try prefix/suffix variations (get-, try-, -app, -hq, …). Default true. Set false for exact-keyword-only across TLDs. |
| keyword | string | yes | Base keyword or brand name to build domain ideas from, e.g. "acme". |
| tlds | array | – | TLDs to consider (without the dot), e.g. ["com","io","ai"]. Default: com, io, ai, co, app, dev. Max 10. |
No output schema declared.
No examples provided.
How do I install the Domains MCP server?
Domains runs locally as an npm package, launched with npx -y @pipeworx/mcp-domains. 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-domains
claude mcp add pipeworx-io-domains -- npx -y @pipeworx/mcp-domains
What is the Domains MCP server?
Domains is an MCP server listed in the public MCP registry as io.github.pipeworx-io/domains. Domains MCP, domain registration lookup + availability search over live RDAP (ICANN standard… This page covers its npm package (@pipeworx/mcp-domains).
Is the Domains MCP server safe to use?
Domains scores 83 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 Domains MCP server expose?
Domains exposes 5 tools: domain_lookup, domain_status, check_availability, find_available_domains, certificate_search. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
Is the Domains MCP server still maintained?
Domains 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 Domains MCP server under?
Domains declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.