Remote MCP · Endpoint

Space Feeds MCP server

No. Space Feeds answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/space-feeds/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/space-feeds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
174 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Space Feeds MCP.
Listing
From the official MCP registry (active).
Recent checks of Space Feeds
CheckedResultHandshake
1 hour agoHandshake completed174 ms
1 day agoHandshake completed196 ms
2 days agoHandshake completed71 ms
3 days agoHandshake completed81 ms
4 days agoHandshake completed84 ms
5 days agoHandshake completed158 ms
6 days agoHandshake completed142 ms
9 days agoHandshake completed186 ms
12 days agoHandshake completed52 ms
14 days agoHandshake completed226 ms
16 days agoHandshake completed70 ms
18 days agoHandshake completed969 ms
20 days agoHandshake completed4.86 s
23 days agoHandshake completed123 ms
25 days agoHandshake completed59 ms
26 days agoHandshake completed64 ms
28 days agoHandshake completed54 ms
29 days agoHandshake completed2.10 s

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

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