Remote MCP · Endpoint

Ncbi Eutils MCP server

No. Ncbi Eutils answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/ncbi-eutils/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ncbi-eutils
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
NCBI E-utilities MCP — federated Entrez search/fetch.
Listing
From the official MCP registry (active).
Recent checks of Ncbi Eutils
CheckedResultHandshake
1 hour agoHandshake completed284 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed54 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed2.69 s
9 days agoHandshake completed65 ms
12 days agoHandshake completed38 ms
14 days agoHandshake completed1.30 s
15 days agoHandshake completed82 ms
17 days agoHandshake completed59 ms
18 days agoHandshake completed34 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed34 ms
20 days agoHandshake completed45 ms
22 days agoHandshake completed58 ms
23 days agoHandshake completed44 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Ncbi Eutils and makes no claim about it beyond what these checks measured.