Remote MCP · Endpoint

OpenCancer MCP server

No. OpenCancer answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://opencancer.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.opencancer/opencancer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Cancer patient expert: NCCN-grounded answers with sources, recruiting trials, and expert review.
Listing
From the official MCP registry (active).
Recent checks of OpenCancer
CheckedResultHandshake
1 day agoHandshake completed98 ms
1 day agoHandshake completed172 ms
2 days agoHandshake completed87 ms
4 days agoHandshake completed100 ms
5 days agoHandshake completed80 ms
6 days agoHandshake completed165 ms
7 days agoHandshake completed104 ms
8 days agoHandshake completed118 ms
9 days agoHandshake completed93 ms
12 days agoHandshake completed97 ms
15 days agoHandshake completed148 ms
17 days agoHandshake completed130 ms
19 days agoHandshake completed97 ms
21 days agoHandshake completed161 ms
23 days agoHandshake completed363 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 OpenCancer and makes no claim about it beyond what these checks measured.