Remote MCP · Endpoint

Civic MCP server

No. Civic answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
75 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 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
1 hour agoHandshake completed75 ms
9 days agoHandshake completed153 ms
9 days agoHandshake completed820 ms
11 days agoHandshake completed1.08 s
12 days agoHandshake completed87 ms
13 days agoHandshake completed174 ms
14 days agoHandshake completed105 ms
15 days agoHandshake completed380 ms
16 days agoHandshake completed343 ms
19 days agoHandshake completed269 ms
22 days agoHandshake completed147 ms
24 days agoHandshake completed94 ms
26 days agoHandshake completed1.26 s
28 days agoHandshake completed140 ms

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