Remote MCP · Endpoint

Stable Baseline MCP server

No. Stable Baseline answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.stablebaseline.io/functions/v1/cloud-serve/mcp

The last check completed an MCP handshake.

Registry name
io.stablebaseline/sb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.23 s
Tools exposed
219 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
End-to-end agent-managed company brain. Docs, diagrams, plans, databases, agents, Knowledge Graph.
Listing
From the official MCP registry (active).
Recent checks of Stable Baseline
CheckedResultHandshake
1 hour agoHandshake completed2.23 s
9 days agoHandshake completed861 ms
10 days agoHandshake completed430 ms
11 days agoHandshake completed284 ms
12 days agoHandshake completed295 ms
14 days agoHandshake completed299 ms
14 days agoHandshake completed764 ms
15 days agoHandshake completed742 ms
17 days agoHandshake completed780 ms
19 days agoHandshake completed1.39 s
21 days agoHandshake completed1.06 s
24 days agoHandshake completed899 ms
26 days agoHandshake completed1.86 s
28 days agoHandshake completed3.12 s

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

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