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.

Findadomain.name

REMOTE · FINDADOMAIN.NAME · SCANNED SEP 20

Find domains and domain hacks with live availability, registrar prices, and keyword search demand.

Available components

+3 this week 71 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 659 tokens (~219/item across 3 items; 3 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 Management37
  • Stability observed for 11 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 3 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 Findadomain.name MCP server?

Findadomain.name is a hosted endpoint at https://findadomain.name/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · findadomain.name

# add to Claude Code
claude mcp add --transport http name-findadomain-domain-finder 'https://findadomain.name/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "name-findadomain-domain-finder": {
      "url": "https://findadomain.name/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "name-findadomain-domain-finder": {
      "type": "http",
      "url": "https://findadomain.name/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.name-findadomain-domain-finder]
url = "https://findadomain.name/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "name-findadomain-domain-finder": {
      "type": "remote",
      "url": "https://findadomain.name/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add name-findadomain-domain-finder --url 'https://findadomain.name/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  name-findadomain-domain-finder:
    url: "https://findadomain.name/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "name-findadomain-domain-finder": {
      "Transport": "http",
      "Url": "https://findadomain.name/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add name-findadomain-domain-finder -t streamable-http -u 'https://findadomain.name/api/mcp'
// mcp.json
{
  "mcpServers": {
    "name-findadomain-domain-finder": {
      "type": "http",
      "url": "https://findadomain.name/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

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

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

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

  • 10 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 9 Sept 26 66

    First indexed and scored.

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 20 Sept 2026 · Probed https://findadomain.name/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=findadomain.name CN=YR2,O=Let's Encrypt,C=US 30 Aug 2026 28 Nov 2026 RSA 2048 SHA256-RSA 57780761befbd811e824d8e951caab264ec
SANs: findadomain.name
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of findadomain.name. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
name. present 34927 13 Verified
findadomain.name. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: data: https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com https://*.elevenlabs.io; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob: data:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://*.elevenlabs.io wss://*.elevenlabs.io https://elevenlabs.io wss://elevenlabs.io; worker-src 'self' blob: data:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com https://elevenlabs.io https://*.elevenlabs.io; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https:/
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://findadomain.name/api/mcp Verified 200
http (plaintext) http://findadomain.name/api/mcp HTTPS enforced 308 https://findadomain.name/api/mcp
MCP tools · 3 exposed · ~527 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_availability ~107

Check availability and real price for a specific list of full domains (e.g. ['acme.com','acme.ai']). Fast, precise lookup for names you already have in mind. Returns availability, the registrar price, and the honest registrar link for each. Up to 25 domains per call.

NameTypeReqDescription
domainsarrayyesFull domain names to check, each including its extension (e.g. ['getacme.com','acme.ai']). Up to 25 at a time.

No output schema declared.

No examples provided.

find_domains ~235

Brainstorm available domain names for an idea, product, or company. Returns brandable names AND domain hacks (a real word spelled across the dot, e.g. 'ope.ninja'), each with real availability, the registrar's real price, and monthly keyword search-volume where available. Unlike GoDaddy or Instant Domain Search, this surfaces domain hacks and real search demand. Prices are real registrar quotes with no markup; each result links to the registrar quoted.

NameTypeReqDescription
descriptionstringOptional. A longer description of the business, for more relevant names and better-fitting extensions.
ideastringyesThe company name, product, or idea to generate domain names for. Example: 'an AI tool that writes SQL'.
purposestringOptional. What the domain is for (e.g. 'startup', 'blog', 'portfolio', 'saas'), to steer the style.
tldsarrayOptional. Restrict results to these TLD extensions without the dot (e.g. ['com','ai','io']). Omit to let the finder pick the best-fitting extensions, including domain hacks.

No output schema declared.

No examples provided.

search_domain ~185

Check exact-name availability and real price for a specific name across many TLD extensions at once. Give a bare label ('acme') to see acme.com, acme.io, acme.ai... or a full domain ('acme.io') to check that one. Returns real availability, the registrar price, a renewal note, and the honest registrar link for each.

NameTypeReqDescription
exact_extensionbooleanOptional. If the name already includes an extension, set true to check only that exact domain instead of expanding across TLDs.
namestringyesThe name to check. A bare label ('acme') is expanded across many TLDs; a full domain ('acme.io') checks that exact domain.
tldsarrayOptional. Limit to these TLD extensions without the dot (e.g. ['com','co','io']).

No output schema declared.

No examples provided.

Common questions

What is the Findadomain.name MCP server?

Findadomain.name is an MCP server listed in the public MCP registry as name.findadomain/domain-finder. Find domains and domain hacks with live availability, registrar prices, and keyword search demand. This page covers its hosted endpoint (https://findadomain.name/api/mcp).

Is the Findadomain.name MCP server safe to use?

Findadomain.name scores 71 out of 100 on VerifyMCP. 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 Findadomain.name MCP server expose?

Findadomain.name exposes 3 tools: find_domains, search_domain, check_availability. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.

Does the Findadomain.name MCP server require authentication?

No. We connected to Findadomain.name without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Findadomain.name MCP server still maintained?

Findadomain.name is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.