Remote MCP · Endpoint

Ecosystems MCP server

No. Ecosystems answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/ecosystems/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ecosystems
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
ecosyste.ms Packages MCP.
Listing
From the official MCP registry (active).
Recent checks of Ecosystems
CheckedResultHandshake
1 hour agoHandshake completed117 ms
1 day agoHandshake completed71 ms
2 days agoHandshake completed136 ms
3 days agoHandshake completed174 ms
4 days agoHandshake completed89 ms
5 days agoHandshake completed131 ms
7 days agoHandshake completed215 ms
9 days agoHandshake completed276 ms
11 days agoHandshake completed73 ms
14 days agoHandshake completed105 ms
16 days agoHandshake completed78 ms
18 days agoHandshake completed890 ms
20 days agoHandshake completed90 ms
22 days agoHandshake completed67 ms
24 days agoHandshake completed60 ms
26 days agoHandshake completed50 ms
27 days agoHandshake completed258 ms
29 days agoHandshake completed430 ms

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