Remote MCP · Endpoint

Cdc MCP server

No. Cdc answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/cdc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
120 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
CDC MCP — wraps CDC open data via Socrata API (data.cdc.gov)
Listing
From the official MCP registry (active).
Recent checks of Cdc
CheckedResultHandshake
1 hour agoHandshake completed120 ms
1 day agoHandshake completed59 ms
2 days agoHandshake completed120 ms
3 days agoHandshake completed90 ms
4 days agoHandshake completed104 ms
5 days agoHandshake completed751 ms
7 days agoHandshake completed318 ms
8 days agoHandshake completed155 ms
11 days agoHandshake completed56 ms
14 days agoHandshake completed234 ms
16 days agoHandshake completed804 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed99 ms
22 days agoHandshake completed60 ms
24 days agoHandshake completed55 ms
26 days agoHandshake completed47 ms
27 days agoHandshake completed99 ms
29 days agoHandshake completed48 ms

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