Remote MCP · Endpoint

Dev Feeds MCP server

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

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/dev-feeds
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
Developer Feeds MCP.
Listing
From the official MCP registry (active).
Recent checks of Dev Feeds
CheckedResultHandshake
1 hour agoHandshake completed117 ms
1 day agoHandshake completed306 ms
2 days agoHandshake completed79 ms
3 days agoHandshake completed93 ms
4 days agoHandshake completed734 ms
5 days agoHandshake completed277 ms
6 days agoHandshake completed164 ms
9 days agoHandshake completed978 ms
12 days agoHandshake completed55 ms
14 days agoHandshake completed55 ms
16 days agoHandshake completed111 ms
18 days agoHandshake completed72 ms
21 days agoHandshake completed183 ms
23 days agoHandshake completed65 ms
25 days agoHandshake completed50 ms
26 days agoHandshake completed75 ms
28 days agoHandshake completed64 ms
29 days agoHandshake completed205 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 Dev Feeds and makes no claim about it beyond what these checks measured.