Remote MCP · Endpoint

Dotsy MCP server

No. Dotsy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
476 ms
Tools exposed
105 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.
Website
https://dotsy.ai/
Listing
From the official MCP registry (active).
Recent checks of Dotsy
CheckedResultHandshake
1 hour agoHandshake completed476 ms
2 days agoHandshake completed528 ms
4 days agoHandshake completed247 ms
6 days agoHandshake completed316 ms
9 days agoHandshake completed535 ms
11 days agoHandshake completed314 ms
13 days agoHandshake completed489 ms
15 days agoHandshake completed424 ms
17 days agoHandshake completed328 ms
19 days agoHandshake completed254 ms
20 days agoHandshake completed270 ms
22 days agoHandshake completed440 ms
23 days agoHandshake completed584 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.