Remote MCP · Endpoint

Synaplan MCP server

No. Synaplan answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://web.synaplan.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.metadist/synaplan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
325 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Self-hosted AI workspace: semantic RAG document search, long-term memory, and AI chat via MCP.
Listing
From the official MCP registry (active).
Recent checks of Synaplan
CheckedResultHandshake
35 minutes agoHandshake completed325 ms
9 days agoHandshake completed375 ms
10 days agoHandshake completed412 ms
11 days agoHandshake completed285 ms
12 days agoHandshake completed276 ms
14 days agoHandshake completed320 ms
14 days agoHandshake completed485 ms
15 days agoHandshake completed298 ms
17 days agoHandshake completed429 ms
19 days agoHandshake completed424 ms
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—

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.

Listing data comes from the official MCP registry. Glide is not affiliated with Synaplan and makes no claim about it beyond what these checks measured.