Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.sonwr/domain-radar

NPM · MCP-DOMAIN-RADAR · SCANNED SEP 22

MCP server that checks domain availability in real-time during brand naming

Available components

0 this week 86 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 396 tokens (~99/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 Management97
  • Stability observed for 29 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 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
Install

How do I install the io.github.sonwr/domain-radar MCP server?

io.github.sonwr/domain-radar runs locally as an npm package, launched with npx -y mcp-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 · mcp-domain-radar

# add to Claude Code
claude mcp add sonwr-domain-radar -- npx -y mcp-domain-radar
// .cursor/mcp.json
{
  "mcpServers": {
    "sonwr-domain-radar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-domain-radar"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sonwr-domain-radar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-domain-radar"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sonwr-domain-radar -- npx -y mcp-domain-radar
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sonwr-domain-radar": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-domain-radar"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sonwr-domain-radar --command npx --arg -y --arg mcp-domain-radar
# ~/.hermes/config.yaml
mcp_servers:
  sonwr-domain-radar:
    command: "npx"
    args: ["-y", "mcp-domain-radar"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sonwr-domain-radar": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-domain-radar"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sonwr-domain-radar -t stdio -c npx -a -y mcp-domain-radar
// mcp.json
{
  "mcpServers": {
    "sonwr-domain-radar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-domain-radar"
      ]
    }
  }
}
Changelog

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.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 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.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 13 Sept 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.

Diagnostics

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 22 Sept 2026 · Analysed npm/mcp-domain-radar@0.1.2

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~396 tokens

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 →

Tool Tokens
check_brand_domains ~145

Check domain availability for a single brand name across many popular TLDs at once. Default TLDs: .com .io .dev .app .ai .co .so .me .xyz .tech .net .sh .run .cloud .to .gg .cc Supports 30+ TLDs including trending ones like .ai, .gg, .so, .lol, .wtf, .cool.

NameTypeReqDescription
namestringyesBrand / product / service name without TLD, e.g. "nexflow"
tldsarrayCustom list of TLDs to check. Omit to use the default popular set.

No output schema declared.

No examples provided.

check_domains ~78

Check availability of specific domain names. Use this when you already have exact domain names to verify (e.g. "mybrand.com", "mybrand.ai"). Checks via DNS + WHOIS for accurate results.

NameTypeReqDescription
domainsarrayyesFull domain names including TLD, e.g. ["cool.ai", "cool.com", "cool.dev"]

No output schema declared.

No examples provided.

list_supported_tlds ~28

List all TLDs that this server can check via WHOIS, grouped by category.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

suggest_and_check_domains ~145

Generate brand-name variations from keywords, then check domain availability for each. Creates variations using prefixes (get-, try-, my-…), suffixes (-hq, -lab, -flow…), compounds (keyword1+keyword2), and portmanteau blends. Great for brainstorming when obvious names are taken.

NameTypeReqDescription
keywordsarrayyesRoot keywords to generate variations from, e.g. ["pulse", "data"]
max_variationsnumberMax name variations to generate & check. Default: 20
tldsarrayTLDs to check per variation. Default: com, io, ai, dev, app, co

No output schema declared.

No examples provided.

Common questions

What is the io.github.sonwr/domain-radar MCP server?

io.github.sonwr/domain-radar is an MCP server listed in the public MCP registry as io.github.sonwr/domain-radar. MCP server that checks domain availability in real-time during brand naming. This page covers its npm package (mcp-domain-radar).

Is the io.github.sonwr/domain-radar MCP server safe to use?

io.github.sonwr/domain-radar scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 io.github.sonwr/domain-radar MCP server expose?

io.github.sonwr/domain-radar exposes 4 tools: check_domains, check_brand_domains, suggest_and_check_domains, list_supported_tlds. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

Is the io.github.sonwr/domain-radar MCP server still maintained?

io.github.sonwr/domain-radar is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.sonwr/domain-radar MCP server under?

io.github.sonwr/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.