Remote MCP · Endpoint

GoMain MCP server

No. GoMain answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://gomain.hottub.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
ai.gomain/domains
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Domain availability and prices from 40+ registrars, name checks, DNS setup, and a domain broker
Listing
From the official MCP registry (active).
Recent checks of GoMain
CheckedResultHandshake
6 hours agoHandshake completed292 ms
9 days agoHandshake completed897 ms
10 days agoHandshake completed254 ms
11 days agoHandshake completed728 ms
12 days agoHandshake completed211 ms
14 days agoHandshake completed665 ms
15 days agoHandshake completed218 ms
15 days agoHandshake completed241 ms
17 days agoHandshake completed358 ms
19 days agoHandshake completed178 ms
22 days agoHandshake completed497 ms
24 days agoHandshake completed924 ms
26 days agoHandshake completed272 ms
28 days agoHandshake completed463 ms

The last 14 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 GoMain and makes no claim about it beyond what these checks measured.