Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-disease What are the current COVID-19 stats for the US?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| Check worldwide COVID-19 totals. Returns cumulative cases, deaths, recovered, active cases, plus today's new cases and deaths. |
| 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 daily COVID-19 timeline for a country or globally. Returns historical progression of cases, deaths, and recoveries by date. |
| Check COVID-19 vaccination progress for a country or globally. Returns cumulative doses administered daily over the past 30 days. |
Related MCP server: opendota-mcp-server
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
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
WHO ICD-10/ICD-11 diagnosis codes. Lookup, search, chapters via official WHO API.
The adaptive health-messaging engine for apps and agents. Federally-sourced. Not medical advice.
Query site stats, realtime visitors, breakdowns and goals from Plausible Analytics.
Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-disease'
If you have feedback or need assistance with the MCP directory API, please join our Discord server