Remote MCP · Endpoint

Cybergenic MCP server

No. Cybergenic answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cybergenic.im/mcp?via=mcpregistry

The last check completed an MCP handshake.

Registry name
im.cybergenic/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Cancer gene co-occurrence and exclusivity in tumour cohorts, with confound controls and exact tests.
Listing
From the official MCP registry (active).
Recent checks of Cybergenic
CheckedResultHandshake
1 hour agoHandshake completed119 ms
2 days agoHandshake completed101 ms
4 days agoHandshake completed674 ms
6 days agoHandshake completed105 ms
8 days agoHandshake completed1.12 s
10 days agoHandshake completed100 ms
12 days agoHandshake completed148 ms
13 days agoHandshake completed183 ms
14 days agoHandshake completed103 ms
16 days agoHandshake completed132 ms
18 days agoHandshake completed144 ms
20 days agoHandshake completed107 ms
21 days agoHandshake completed104 ms
23 days agoHandshake completed130 ms
24 days agoHandshake completed128 ms

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

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