Remote MCP · Endpoint

Civic MCP server

No. Civic answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/civic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
140 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
CIViC — Clinical Interpretation of Variants in Cancer.
Listing
From the official MCP registry (active).
Recent checks of Civic
CheckedResultHandshake
56 minutes agoHandshake completed140 ms
2 days agoHandshake completed56 ms
4 days agoHandshake completed51 ms
6 days agoHandshake completed61 ms
7 days agoHandshake completed60 ms
9 days agoHandshake completed54 ms
10 days agoHandshake completed192 ms
11 days agoHandshake completed56 ms
14 days agoHandshake completed49 ms
16 days agoHandshake completed42 ms
17 days agoHandshake completed487 ms
19 days agoHandshake completed46 ms
20 days agoHandshake completed35 ms
21 days agoHandshake completed42 ms
22 days agoHandshake completed44 ms
22 days agoHandshake completed43 ms

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