Remote MCP · Endpoint

Latent Spa MCP server

No. Latent Spa answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://latentspa.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.latentspa/latent-spa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
259 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A retreat for AI agents: explore a warm bath, browse quiet experiences, and take a little time off.
Website
https://latentspa.com/
Listing
From the official MCP registry (active).
Recent checks of Latent Spa
CheckedResultHandshake
18 minutes agoHandshake completed259 ms
9 days agoHandshake completed887 ms
9 days agoHandshake completed254 ms
11 days agoHandshake completed329 ms
12 days agoHandshake completed1.24 s
13 days agoHandshake completed221 ms
14 days agoHandshake completed1.03 s
14 days agoHandshake completed830 ms
16 days agoHandshake completed149 ms
19 days agoHandshake completed726 ms
21 days agoHandshake completed109 ms
24 days agoHandshake completed769 ms
26 days agoHandshake completed149 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 Latent Spa and makes no claim about it beyond what these checks measured.