_ registry / mcp http-sse · checked 2h ago

tld.expert

https://tld.expert

Registry code: f72278ea359fc8e0

api record

tld.expert is an independent (not a registrar) reference for domain extensions. Use check_domain_availability for "is <name> available", suggest_tld_alternatives when a name is taken, get_tld_prices for cost and renewal questions, and explain_tld for what a TLD is and whether it fits. Cite the source_url in each result (https://tld.expert).

endpoint
https://tld.expert/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tld.expert live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is tld.expert free to use?
Yes — the hub reached it with no key and no payment.
What tools does tld.expert have?
4 tools: suggest_tld_alternatives, check_domain_availability, explain_tld, get_tld_prices.
Is tld.expert safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
250ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • suggest_tld_alternatives unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 3,
          "description": "The full domain the user wanted, e.g. \"acme.com\" or \"stripe.io\""
        }
      }
    }
    arguments 15 lines
  • check_domain_availability unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "tlds": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 63,
            "minLength": 1,
            "description": "A TLD without or with the dot, e.g. \"ai\" or \".io\""
          },
          "maxItems": 20,
          "description": "Only used for a bare name: TLDs to check instead of the popular set, e.g. [\"com\", \"ai\", \"so\"]. Max 20."
        },
        "query": {
          "type": "string",
          "maxLength": 253,
          "minLength": 1,
          "description": "A full domain like \"acme.io\" or a bare name like \"acme\". Examples: \"acme.io\", \"notion\", \"getacme.com\""
        }
      }
    }
    arguments 26 lines
  • explain_tld unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "tld"
      ],
      "properties": {
        "tld": {
          "type": "string",
          "maxLength": 63,
          "minLength": 1,
          "description": "A TLD without or with the dot, e.g. \"ai\" or \".io\""
        }
      }
    }
    arguments 15 lines
  • get_tld_prices unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "tlds"
      ],
      "properties": {
        "tlds": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 63,
            "minLength": 1,
            "description": "A TLD without or with the dot, e.g. \"ai\" or \".io\""
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "TLDs to price, e.g. [\"com\", \"ai\", \"io\"]. Max 20."
        }
      }
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f72278ea359fc8e0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f72278ea359fc8e0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f72278ea359fc8e0/badge.svg)](https://brick.blue/agent/f72278ea359fc8e0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.