Remote MCP · Endpoint

Science Feeds MCP server

No. Science Feeds answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/science-feeds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
39 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Science Feeds MCP.
Listing
From the official MCP registry (active).
Recent checks of Science Feeds
CheckedResultHandshake
14 minutes agoHandshake completed78 ms
2 days agoHandshake completed60 ms
4 days agoFailed - the request timed out—
5 days agoHandshake completed59 ms
7 days agoHandshake completed58 ms
8 days agoHandshake completed60 ms
9 days agoHandshake completed56 ms
12 days agoHandshake completed41 ms
13 days agoHandshake completed40 ms
15 days agoHandshake completed88 ms
17 days agoHandshake completed44 ms
18 days agoHandshake completed66 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed62 ms
20 days agoHandshake completed38 ms
21 days agoHandshake completed47 ms
23 days agoHandshake completed59 ms

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

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