Remote MCP · Endpoint

Space MCP server

Yes, as of 5 hours ago: the hostname does not resolve.

DownLast checked 5 hours ago

Server URL

https://api.getspace.sh/mcp/

The last check failed: the hostname does not resolve.

Registry name
sh.getspace/space
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
One shared memory for all your AI agents: documents, tasks, databases and memories in one workspace
Listing
From the official MCP registry (active).
Recent checks of Space
CheckedResultHandshake
5 hours agoFailed - the hostname does not resolve—
9 days agoCredentials required—
10 days agoCredentials required—
11 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—

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

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