# NameHound (remote · namehound.app)

Is a brand name free as a .com/.net/.org/.app domain and as a Bluesky, Mastodon, npm or PyPI handle?

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `namehound.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/app-namehound-namehound/namehound.md), [page](https://verifymcp.io/servers/app-namehound-namehound/namehound)

## Channel facts

- Endpoint: `https://namehound.app/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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 417 tokens (~417/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the NameHound MCP server?

NameHound is a hosted endpoint at https://namehound.app/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 app-namehound-namehound 'https://namehound.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-namehound-namehound": {
      "url": "https://namehound.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-namehound-namehound": {
      "type": "http",
      "url": "https://namehound.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-namehound-namehound]
url = "https://namehound.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-namehound-namehound": {
      "type": "remote",
      "url": "https://namehound.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-namehound-namehound --url 'https://namehound.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-namehound-namehound:
    url: "https://namehound.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-namehound-namehound": {
      "Transport": "http",
      "Url": "https://namehound.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-namehound-namehound -t streamable-http -u 'https://namehound.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-namehound-namehound": {
      "type": "http",
      "url": "https://namehound.app/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-10-23 (score 76, +1)

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

### 2026-10-21 (score 75, +1)

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

### 2026-10-19 (score 74, +1)

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

### 2026-10-17 (score 73, +1)

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

### 2026-10-15 (score 72, +1)

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

### 2026-10-12 (score 71, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 70)

First indexed and scored.

## MCP tools (1)

### `check_name_availability` (~275 tokens)

Check a name: domains, handles and Brand Name Score

Use this when someone asks whether one specific brand, business, product or project name is free as a domain name (.com, .net, .org, .app) and as a handle on Bluesky, Mastodon, GitLab, npm and PyPI, and wants the NameHound Brand Name Score (0-100) for it. Send one name per call, for example "Blue Fern Studio". The name is made into a handle (lowercase letters and numbers). Returns up to 4 rows, each with the check time, the official source and a link to the NameHound page for that name. Results are a snapshot: availability can change, the registrar or platform has the final say, and this is not legal or trademark advice (the score leaves out the trademark part until the person runs the free USPTO search themselves). Do not use it to brainstorm names, to check a list of names, for trademark clearance, or for Instagram, X, TikTok, YouTube, GitHub or other platforms it does not check. It has a small daily limit, so call it only for names the person actually cares about.

Input parameters:

- `name` (string, required): A specific name, e.g. "Blue Fern Studio". 2-40 characters. Wildcards and "all" are not accepted.

Output parameters:

- `attribution` (string)
- `more_available` (boolean)
- `more_info` (string)
- `note` (string)
- `result_count` (integer)
- `results` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-namehound-namehound/namehound#diagnostics

## Score history

- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-10: 70

## Common questions

### What is the NameHound MCP server?

NameHound is an MCP server listed in the public MCP registry as app.namehound/namehound. Is a brand name free as a .com/.net/.org/.app domain and as a Bluesky, Mastodon, npm or PyPI handle? This page covers its hosted endpoint (https://namehound.app/mcp).

### Is the NameHound MCP server safe to use?

NameHound scores 76 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 NameHound MCP server expose?

NameHound exposes 1 tool: check_name_availability. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.

### Does the NameHound MCP server require authentication?

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

### Is the NameHound MCP server still maintained?

NameHound is still listed as active in the MCP registry. We last reached this channel on 23 October 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://namehound.app/mcp
- Website: https://namehound.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-namehound-namehound/namehound.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-namehound-namehound/namehound.json
- HTML version of this page: https://verifymcp.io/servers/app-namehound-namehound/namehound