Remote MCP · Endpoint

Just Domain MCP server

No. Just Domain answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.justdomain.ai/

The last check completed an MCP handshake.

Registry name
ai.justdomain/just-domain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search domain availability and pricing, and check if a domain can transfer in, from chat.
Listing
From the official MCP registry (active).
Recent checks of Just Domain
CheckedResultHandshake
8 hours agoHandshake completed92 ms
2 days agoHandshake completed94 ms
4 days agoHandshake completed95 ms
5 days agoHandshake completed95 ms
7 days agoHandshake completed114 ms
8 days agoHandshake completed93 ms
9 days agoHandshake completed121 ms
12 days agoHandshake completed97 ms
13 days agoHandshake completed95 ms
15 days agoHandshake completed99 ms
16 days agoHandshake completed117 ms
17 days agoHandshake completed114 ms
18 days agoHandshake completed101 ms
19 days agoHandshake completed110 ms
20 days agoHandshake completed100 ms
21 days agoHandshake completed96 ms
23 days agoHandshake completed93 ms

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

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 Just Domain and makes no claim about it beyond what these checks measured.