Remote MCP · Endpoint

dotsweep MCP server

No. dotsweep answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://dotsweep.com/mcp

The last check completed an MCP handshake.

Registry name
com.dotsweep/dotsweep
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Domain availability across 1,200+ TLDs, with renewal price, minimum term and eligibility
Listing
From the official MCP registry (active).
Recent checks of dotsweep
CheckedResultHandshake
9 hours agoHandshake completed79 ms
2 days agoHandshake completed110 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed64 ms
7 days agoHandshake completed776 ms
8 days agoHandshake completed116 ms
9 days agoHandshake completed103 ms
12 days agoHandshake completed79 ms
13 days agoHandshake completed68 ms
15 days agoHandshake completed102 ms
16 days agoHandshake completed72 ms
17 days agoHandshake completed40 ms
19 days agoHandshake completed67 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed48 ms
21 days agoHandshake completed67 ms
22 days agoHandshake completed45 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 dotsweep and makes no claim about it beyond what these checks measured.