
Wraps the disease.sh API to give you COVID-19 statistics without needing authentication. You get access to pandemic data through Pipeworx's gateway, which hosts this alongside 673+ other data sources. The repo doesn't list specific tools, but disease.sh typically offers endpoints for global stats, country breakdowns, historical data, and vaccination numbers. Useful if you're building dashboards, doing epidemiological analysis, or need to pull pandemic metrics into reports. Runs over streamable HTTP, so no local installation needed. Part of the broader Pipeworx ecosystem where you can ask questions in plain English and let the gateway route to the right API automatically.
Disease MCP — wraps disease.sh API (COVID-19 statistics, no auth required)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_global_stats | Check worldwide COVID-19 totals. Returns cumulative cases, deaths, recovered, active cases, plus today's new cases and deaths. |
get_country_stats | Check COVID-19 stats for a specific country (e.g., "US", "India", "GB"). Returns cases, deaths, recovered, active cases, today's change, and population. |
get_historical | Get daily COVID-19 timeline for a country or globally. Returns historical progression of cases, deaths, and recoveries by date. |
get_vaccine_stats | Check COVID-19 vaccination progress for a country or globally. Returns cumulative doses administered daily over the past 30 days. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"disease": {
"url": "https://gateway.pipeworx.io/disease/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/disease/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Disease data" })
The gateway picks the right tool and fills the arguments automatically.
MIT