Remote MCP · Endpoint

tld.expert MCP server

No. tld.expert answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://tld.expert/mcp

The last check completed an MCP handshake.

Registry name
expert.tld/tld-expert
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
728 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live domain availability, TLD alternatives, dated registrar prices and expert TLD advice.
Listing
From the official MCP registry (active).
Recent checks of tld.expert
CheckedResultHandshake
9 hours agoHandshake completed728 ms
4 days agoHandshake completed91 ms
14 days agoHandshake completed122 ms
15 days agoHandshake completed685 ms
15 days agoHandshake completed89 ms
17 days agoHandshake completed532 ms
18 days agoHandshake completed114 ms
19 days agoHandshake completed210 ms
20 days agoHandshake completed98 ms
21 days agoHandshake completed68 ms
23 days agoHandshake completed119 ms
26 days agoHandshake completed67 ms
28 days agoHandshake completed112 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with tld.expert and makes no claim about it beyond what these checks measured.