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.seomarlboro/domain-check-skills-mcp

NPM · DOMAIN-CHECK-SKILLS-MCP

World's fastest domain check. Or the second — dispute it. 50+ TLDs, 6 registrars, no API key.

0 this week 79 Trust /100

Last scanned (23 hours ago)

Scores higher than 61% of npm servers

Category E-commerce

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 706 tokens (~176/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 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
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.

  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 26 0
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Package version: 1.2.2 → 1.2.12 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
    • Stability: 0.97 → pass security
  • 23 Oct 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.

  • 22 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 18 Oct 26 0
    • Package version: 1.2.2 → 1.2.12 functional
  • 17 Oct 26 +5
    • Source repository: unverified → pass ▲ security
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 4 Nov 2026 · Analysed npm/domain-check-skills-mcp@1.2.12

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~706 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_domain ~226

Check if ONE specific domain (e.g. acme.io) is registrable right now. Use for a single fully-qualified name; to test one word across many extensions, use search_domains instead. Returns an availability verdict, the cheapest registrar and its buy link, the first-year price, and — for taken names — the registration year. Availability is confirmed by RDAP + DNS-over-HTTPS, authoritative for most TLDs; ambiguous names (premium suspects, trademark-blocked names, and zones with no reliable RDAP such as .co/.me) are additionally cross-checked against a third signal (Fastly Domain Research). When no source is authoritative or they disagree, the verdict comes back as uncertain rather than guessed — treat uncertain as 'unknown, NOT available', and note that price may be absent for such names.

NameTypeReqDescription
domainstringyesA single fully-qualified domain including its TLD, e.g. 'acme.io'. URLs and 'www.' prefixes are stripped automatically. Not a bare word — use search_domains to test a word across multiple TLDs.

No output schema declared.

No examples provided.

compare_registrars ~155

Compare what 6 registrars (Namecheap, Cloudflare, Porkbun, GoDaddy, Spaceship, OVHcloud) charge for a given TLD — first-year registration, renewal, and 3-year total — exposing the renewal traps that cheap first-year promos hide. Use for pricing a TLD you already intend to buy; this does NOT check whether a specific domain is free (use check_domain for that). Returns per-registrar rows with buy links, or a notice if no fresh cached pricing exists for that TLD.

NameTypeReqDescription
tldstringyesA single TLD WITHOUT the leading dot, e.g. 'com', 'io', 'ai'. A leading dot is stripped if present.

No output schema declared.

No examples provided.

get_domain_age ~125

Return the registration (creation) year and expiration date of a TAKEN domain, via RDAP. Use to gauge how long a name has been held or when it may expire; it does NOT report availability (use check_domain for that). Returns a 'could not determine' notice for names with no RDAP creation record (some ccTLDs, e.g. .co).

NameTypeReqDescription
domainstringyesA fully-qualified domain including its TLD, e.g. 'acme.com'. Meaningful only for taken/registered domains; available names have no registration date.

No output schema declared.

No examples provided.

search_domains ~200

Check ONE name across MANY TLDs in a single call (e.g. 'acme' → com, io, ai …). Use when comparing extensions for the same word; for a single known domain use check_domain instead. Results are grouped AVAILABLE / TAKEN / UNKNOWN, each carrying cheapest price, buy link, and (for taken names) registration year. Names whose availability cannot be confirmed appear under UNKNOWN and must NOT be treated as available (honest 'unverified' state, never a guess).

NameTypeReqDescription
querystringyesThe name WITHOUT any TLD, e.g. 'acme' (not 'acme.com'). This single word is tested against each TLD in the tlds list.
tldsstring–Optional comma-separated TLDs without dots, e.g. 'com,io,ai'. Omit to use a curated default set of 11 popular TLDs. Whitespace is ignored.

No output schema declared.

No examples provided.

Install

How do I install the io.github.seomarlboro/domain-check-skills-mcp server?

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

# add to Claude Code
claude mcp add seomarlboro-domain-check-skills-mcp -- npx -y domain-check-skills-mcp
Common questions

What is the io.github.seomarlboro/domain-check-skills-mcp server?

io.github.seomarlboro/domain-check-skills-mcp is listed in the public MCP registry as io.github.seomarlboro/domain-check-skills-mcp. World's fastest domain check. Or the second, dispute it. 50+ TLDs, 6 registrars, no API key. This page covers its npm package (domain-check-skills-mcp).

Is the io.github.seomarlboro/domain-check-skills-mcp server safe to use?

io.github.seomarlboro/domain-check-skills-mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 io.github.seomarlboro/domain-check-skills-mcp server expose?

io.github.seomarlboro/domain-check-skills-mcp exposes 4 tools: check_domain, search_domains, compare_registrars, get_domain_age. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.

Is the io.github.seomarlboro/domain-check-skills-mcp server still maintained?

io.github.seomarlboro/domain-check-skills-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.seomarlboro/domain-check-skills-mcp server under?

io.github.seomarlboro/domain-check-skills-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.