Remote MCP · Endpoint

dotsy MCP server

No. dotsy answered an MCP handshake 32 minutes ago.

UpLast checked 32 minutes ago

Server URL

https://mcp.dotsy.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.dotsy/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
317 ms
Tools exposed
120 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Build and publish static sites on dotsy with draft-first MCP tools, OAuth Connect, and API keys.
Listing
From the official MCP registry (active).
Recent checks of dotsy
CheckedResultHandshake
32 minutes agoHandshake completed317 ms
3 days agoHandshake completed448 ms
13 days agoHandshake completed528 ms
13 days agoHandshake completed267 ms
15 days agoHandshake completed299 ms
16 days agoHandshake completed373 ms
17 days agoHandshake completed393 ms
18 days agoHandshake completed295 ms
18 days agoHandshake completed282 ms
20 days agoHandshake completed476 ms
22 days agoHandshake completed528 ms
25 days agoHandshake completed247 ms
27 days agoHandshake completed316 ms
30 days agoHandshake completed535 ms

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

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