Remote MCP · Endpoint

Ncbi Variation MCP server

No. Ncbi Variation answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ncbi-variation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
dbSNP refSNP records and HGVS/SPDI/rsID normalization for human genetic variants, from NCBI…
Listing
From the official MCP registry (active).
Recent checks of Ncbi Variation
CheckedResultHandshake
42 minutes agoHandshake completed79 ms
9 days agoHandshake completed107 ms
10 days agoHandshake completed114 ms
11 days agoHandshake completed104 ms
12 days agoHandshake completed68 ms
14 days agoHandshake completed168 ms
14 days agoHandshake completed101 ms
15 days agoHandshake completed112 ms
17 days agoHandshake completed142 ms
19 days agoHandshake completed189 ms
21 days agoHandshake completed71 ms
24 days agoHandshake completed81 ms
26 days agoHandshake completed53 ms
28 days agoHandshake completed86 ms

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