Remote MCP · Endpoint

Ena MCP server

No. Ena answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ena
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
European Nucleotide Archive (ENA) — EMBL-EBI's public record of raw sequencing runs, assemblies…
Listing
From the official MCP registry (active).
Recent checks of Ena
CheckedResultHandshake
1 hour agoHandshake completed64 ms
2 days agoHandshake completed54 ms
4 days agoHandshake completed54 ms
6 days agoHandshake completed336 ms
8 days agoHandshake completed54 ms
9 days agoHandshake completed66 ms
10 days agoHandshake completed187 ms
11 days agoHandshake completed61 ms
14 days agoHandshake completed48 ms
16 days agoHandshake completed51 ms
17 days agoHandshake completed94 ms
19 days agoHandshake completed55 ms
20 days agoHandshake completed761 ms
21 days agoHandshake completed56 ms
22 days agoHandshake completed46 ms
22 days agoHandshake completed1.64 s

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

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