Remote MCP · Endpoint

Design Feeds MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/design-feeds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Design Feeds MCP.
Listing
From the official MCP registry (active).
Recent checks of Design Feeds
CheckedResultHandshake
1 hour agoHandshake completed173 ms
1 day agoHandshake completed303 ms
2 days agoHandshake completed67 ms
3 days agoHandshake completed94 ms
4 days agoHandshake completed99 ms
5 days agoHandshake completed125 ms
6 days agoHandshake completed122 ms
9 days agoHandshake completed114 ms
12 days agoHandshake completed56 ms
14 days agoHandshake completed58 ms
16 days agoHandshake completed75 ms
18 days agoHandshake completed62 ms
21 days agoHandshake completed62 ms
23 days agoHandshake completed70 ms
25 days agoHandshake completed50 ms
26 days agoHandshake completed83 ms
28 days agoHandshake completed49 ms
29 days agoHandshake completed178 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 Design Feeds and makes no claim about it beyond what these checks measured.