# tld.expert (remote · tld.expert)

Live domain availability, TLD alternatives, dated registrar prices and expert TLD advice.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

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

## Channel facts

- Endpoint: `https://tld.expert/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-24.

- **Endpoint Security**: 80/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.
  - 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 781 tokens (~156/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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).
  - Supports UI / widget rendering.

## Install

### How do I install the tld.expert MCP server?

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

### Cursor

```json
{
  "mcpServers": {
    "expert-tld-tld-expert": {
      "url": "https://tld.expert/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.expert-tld-tld-expert]
url = "https://tld.expert/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add expert-tld-tld-expert --url 'https://tld.expert/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  expert-tld-tld-expert:
    url: "https://tld.expert/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add expert-tld-tld-expert -t streamable-http -u 'https://tld.expert/mcp'
```

### Other

```json
{
  "mcpServers": {
    "expert-tld-tld-expert": {
      "type": "http",
      "url": "https://tld.expert/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-24 (score 76, 0)

- [security] Tool “get_tld_prices” rewrote its description, which is the text the model reads

### 2026-10-22 (score 76, +1)

- [security] Resource “availability_widget” now points somewhere else: ui://tld-expert/availability-v1.html → ui://tld-expert/availability-v3.html
- [functional improvement] Stability: unverified → 0.03

### 2026-10-21 (score 75)

First indexed and scored.

## MCP tools (4)

### `check_domain_availability` (~222 tokens)

Check domain availability

Use this when the user wants to know if a domain name is available or taken, or asks "can I get <name>". Accepts a full domain ("acme.io") for one verdict, or a bare name ("acme") to check it across popular TLDs (com, io, ai, co, app, dev, net, org, xyz) or a custom TLD list. Checks live DNS, registry RDAP/WHOIS and a registrar; never claims "available" without registrar confirmation. Returns a verdict per domain, buy links for names that may be free, and a tld.expert URL to cite.

Input parameters:

- `query` (string, required): A full domain like "acme.io" or a bare name like "acme". Examples: "acme.io", "notion", "getacme.com"
- `tlds` (array): Only used for a bare name: TLDs to check instead of the popular set, e.g. ["com", "ai", "so"]. Max 20.

### `suggest_tld_alternatives` (~121 tokens)

Suggest alternative domains

Use this when the domain the user wants is taken (or they ask for other options for a name). Given a full domain like "acme.com", proposes other endings (acme.io), added words (getacme.com), domain hacks and related words, checks every candidate live, and returns only the ones that are not taken. Slower than a single check (up to ~30 live lookups).

Input parameters:

- `domain` (string, required): The full domain the user wanted, e.g. "acme.com" or "stripe.io"

### `get_tld_prices` (~196 tokens)

Get TLD prices

Use this when the user asks what a domain extension costs, where it is cheapest, or what it renews at. Returns dated first-year, renewal and transfer prices per registrar (Porkbun, Dynadot, Cloudflare, Namecheap where tracked), the cheapest direct buy, the wholesale floor, and a renewal-trap flag when the renewal is 2x+ the intro price. Prices are the TLD standard price, not premium names. Also answers "what does it cost over 5 years": true_cost gives each registrar's 1/3/5/10-year cost, the cheapest path per horizon (stay, or register at one and transfer after year one for gTLDs) and recent renewal price changes, each with source URL and checked date.

Input parameters:

- `tlds` (array, required): TLDs to price, e.g. ["com", "ai", "io"]. Max 20.

### `explain_tld` (~134 tokens)

Explain a TLD

Use this when the user asks what a domain extension is, what it means, who runs it, who can register it, or whether it fits their project ("is .ai good for a startup", "what is .io", "does .web exist"). Returns tld.expert’s editorial verdict, pros and cons, registry, registration restrictions, the use cases it ranks for, and a typical price. Also answers for well-known non-existent TLDs like .eth or .web.

Input parameters:

- `tld` (string, required): A TLD without or with the dot, e.g. "ai" or ".io"

## Diagnostics

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

## Score history

- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 75

## Common questions

### What is the tld.expert MCP server?

tld.expert is an MCP server listed in the public MCP registry as expert.tld/tld-expert. Live domain availability, TLD alternatives, dated registrar prices and expert TLD advice. This page covers its hosted endpoint (https://tld.expert/mcp).

### Is the tld.expert MCP server safe to use?

tld.expert 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 tld.expert MCP server expose?

tld.expert exposes 4 tools: check_domain_availability, suggest_tld_alternatives, get_tld_prices, explain_tld. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.

### Does the tld.expert MCP server require authentication?

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

### Is the tld.expert MCP server still maintained?

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