# Findadomain.name (remote · findadomain.name)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `findadomain.name`: 71/100 (this document), [markdown](https://verifymcp.io/servers/name-findadomain-domain-finder/api-mcp.md), [page](https://verifymcp.io/servers/name-findadomain-domain-finder/api-mcp)

## Channel facts

- Endpoint: `https://findadomain.name/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http name-findadomain-domain-finder 'https://findadomain.name/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "name-findadomain-domain-finder": {
      "url": "https://findadomain.name/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "name-findadomain-domain-finder": {
      "type": "http",
      "url": "https://findadomain.name/api/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add name-findadomain-domain-finder --url 'https://findadomain.name/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  name-findadomain-domain-finder:
    url: "https://findadomain.name/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "name-findadomain-domain-finder": {
      "Transport": "http",
      "Url": "https://findadomain.name/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add name-findadomain-domain-finder -t streamable-http -u 'https://findadomain.name/api/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 71, +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.

### 2026-09-17 (score 70, +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.

### 2026-09-15 (score 69, +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.

### 2026-09-13 (score 68, +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.

### 2026-09-11 (score 67, +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.

### 2026-09-10 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-09 (score 66)

First indexed and scored.

## MCP tools (3)

### `find_domains` (~235 tokens)

Find brandable names and domain hacks

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.

Input parameters:

- `description` (string): Optional. A longer description of the business, for more relevant names and better-fitting extensions.
- `idea` (string, required): The company name, product, or idea to generate domain names for. Example: 'an AI tool that writes SQL'.
- `purpose` (string): Optional. What the domain is for (e.g. 'startup', 'blog', 'portfolio', 'saas'), to steer the style.
- `tlds` (array): Optional. 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.

### `search_domain` (~185 tokens)

Check one name across many extensions

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.

Input parameters:

- `exact_extension` (boolean): Optional. If the name already includes an extension, set true to check only that exact domain instead of expanding across TLDs.
- `name` (string, required): The name to check. A bare label ('acme') is expanded across many TLDs; a full domain ('acme.io') checks that exact domain.
- `tlds` (array): Optional. Limit to these TLD extensions without the dot (e.g. ['com','co','io']).

### `check_availability` (~107 tokens)

Check a specific list of domains

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.

Input parameters:

- `domains` (array, required): Full domain names to check, each including its extension (e.g. ['getacme.com','acme.ai']). Up to 25 at a time.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/name-findadomain-domain-finder/api-mcp#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 66
- 2026-09-09: 66

## 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.

## Links

- Remote endpoint: https://findadomain.name/api/mcp
- Website: https://findadomain.name/?utm_source=mcp-registry&utm_medium=listing&utm_campaign=mcp-launch-sep09
- Changelog RSS feed: https://verifymcp.io/servers/name-findadomain-domain-finder/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/name-findadomain-domain-finder/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/name-findadomain-domain-finder/api-mcp