surf.insight/domain-radar
NPM · DOMAIN-RADAR
High-Speed Domain Keyword Matrix, TLD Coverage & RDAP Availability Radar (Powered by insight.surf)
Available components
Last scanned (26 minutes ago)
Scores higher than 65% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 640 tokens (~160/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
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 4 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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 20 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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/domain-radar@1.2.0
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 →
find_available_combinations Legacy Combinations Alias ~40
Backward-compatible alias for search_keyword_domains.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | – |
| keyword | string | yes | – |
| position | string | – | – |
No output schema declared.
No examples provided.
scan_keyword_tlds Scan Keyword TLD Coverage Matrix ~148
Audits a core keyword across major authoritative RDAP registries (supports 1,200+ global TLDs: .com, .net, .org, .ai, .io, .xyz, .tech, .app, .cloud, etc.) to report commercial registration density and probe live web activity for taken domains.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | The root keyword to audit across TLD extensions (e.g. weddingshoes, permafrost, agent) |
| tlds | array | – | List of TLDs to scan. Defaults to premier 11: com, net, org, ai, io, xyz, tech, app, cloud, co, de |
No output schema declared.
No examples provided.
search_keyword_combinations Search Keyword Combinations (Alias) ~66
Alias for search_keyword_domains.
| Name | Type | Req | Description |
|---|---|---|---|
| extensions | array | – | – |
| include_alphabets | boolean | – | – |
| include_digits | boolean | – | – |
| include_hyphens | boolean | – | – |
| keyword | string | yes | – |
| position | string | – | – |
No output schema declared.
No examples provided.
search_keyword_domains DotDB-Style Keyword Domain Intelligence ~386
Full DotDB-style domain search engine. Supports keyword placement (beginning/prefix, end/suffix, any/contains), character inclusion toggles (alphabets, digits, hyphens), site status filtering (Active in use, Parked for sale, Inactive/dormant, and Unregistered available), and extension filtering across 1,200+ IANA TLDs.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | string | – | Substring or word to exclude from generated candidates |
| extensions | array | – | List of TLD extensions to check (e.g. ['com', 'net', 'ai', 'io', 'xyz']). Defaults to ['com']. |
| include_alphabets | boolean | – | Include word/alphabet combinations. Set to false if searching purely numeric variants. |
| include_digits | boolean | – | Include numeric digits (0-9, 24, 365, etc.). When false, enforces pure letter-only domains. |
| include_hyphens | boolean | – | Include hyphenated domain variants. When false, enforces strictly unhyphenated domains. |
| industry | string | – | Target industry dictionary for word pairings |
| keyword | string | yes | The core keyword to search/audit (e.g. weddingshoes, permafrost, agent) |
| max_length | integer | – | Maximum character length (excluding extension) |
| min_length | integer | – | Minimum character length (excluding extension) |
| position | string | – | Keyword position: 'beginning' (starts with keyword), 'end' (ends with keyword), or 'any' (keyword anywhere) |
| site_status_filter | array | – | Filter returned results by site status: 'active' (live site in use), 'parked' (for sale/parking), 'inactive' (dormant/no DNS), 'unregistered' (available in registry), or 'all' |
No output schema declared.
No examples provided.
How do I install the surf.insight/domain-radar MCP server?
surf.insight/domain-radar runs locally as an npm package, launched with npx -y domain-radar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · domain-radar
claude mcp add surf-insight-domain-radar -- npx -y domain-radar
What is the surf.insight/domain-radar MCP server?
surf.insight/domain-radar is an MCP server listed in the public MCP registry as surf.insight/domain-radar. High-Speed Domain Keyword Matrix, TLD Coverage & RDAP Availability Radar (Powered by insight.surf). This page covers its npm package (domain-radar).
Is the surf.insight/domain-radar MCP server safe to use?
surf.insight/domain-radar scores 80 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 surf.insight/domain-radar MCP server expose?
surf.insight/domain-radar exposes 4 tools: search_keyword_domains, scan_keyword_tlds, search_keyword_combinations, find_available_combinations. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Is the surf.insight/domain-radar MCP server still maintained?
surf.insight/domain-radar 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 surf.insight/domain-radar MCP server under?
surf.insight/domain-radar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.