Remote MCP · Endpoint

Ghosty Studio docs MCP server

No. Ghosty Studio docs answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.ghosty.studio/mcp/docs

The last check completed an MCP handshake.

Registry name
studio.ghosty/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
293 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Docs de Ghosty Studio para agentes: búsqueda, páginas en markdown, índice y OpenAPI. Sin auth.
Listing
From the official MCP registry (active).
Recent checks of Ghosty Studio docs
CheckedResultHandshake
2 hours agoHandshake completed293 ms
2 days agoHandshake completed310 ms
4 days agoHandshake completed314 ms
7 days agoHandshake completed348 ms
9 days agoHandshake completed292 ms
11 days agoHandshake completed292 ms
13 days agoHandshake completed306 ms
15 days agoHandshake completed313 ms
16 days agoHandshake completed300 ms
18 days agoHandshake completed313 ms
19 days agoHandshake completed316 ms
20 days agoHandshake completed306 ms
23 days agoHandshake completed312 ms
24 days agoHandshake completed309 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 Ghosty Studio docs and makes no claim about it beyond what these checks measured.