tld.expert
REMOTE · TLD.EXPERT
Live domain availability, TLD alternatives, dated registrar prices and expert TLD advice.
Available components
Last scanned (2 hours ago)
Scores higher than 70% of remote servers
Reachable. Last reached 24 Oct 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 24 Oct 26 0
- Tool “get_tld_prices” rewrote its description, which is the text the model reads security
- 22 Oct 26 +1
- Resource “availability_widget” now points somewhere else: ui://tld-expert/availability-v1.html → ui://tld-expert/availability-v3.html security
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 75
First indexed and scored.
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 24 Oct 2026 · Probed https://tld.expert/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.tld.expert | CN=YR2,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 604bfcecb1e17f9361b6f0dfbbfecbd8cf5 |
| SANs: *.tld.expert, tld.expert | ||||||
| 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 tld.expert. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| expert. | present | 35986 | 8 | Verified |
| tld.expert. | 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=63072000 |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), 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://tld.expert/mcp | Verified | 200 | |
| http (plaintext) | http://tld.expert/mcp | HTTPS enforced | 308 | https://tld.expert/mcp |
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 →
check_domain_availability Check domain availability ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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. |
No output schema declared.
No examples provided.
explain_tld Explain a TLD ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tld | string | yes | A TLD without or with the dot, e.g. "ai" or ".io" |
No output schema declared.
No examples provided.
get_tld_prices Get TLD prices ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tlds | array | yes | TLDs to price, e.g. ["com", "ai", "io"]. Max 20. |
No output schema declared.
No examples provided.
suggest_tld_alternatives Suggest alternative domains ~121
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The full domain the user wanted, e.g. "acme.com" or "stripe.io" |
No output schema declared.
No examples provided.
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.
remote · tld.expert
claude mcp add --transport http expert-tld-tld-expert 'https://tld.expert/mcp'
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.