Bring Epidemiology
to Cursor
Learn how to connect CDC WONDER (Epidemiologic Data) to Cursor and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the CDC WONDER (Epidemiologic Data) MCP Server?
Connect to the CDC WONDER (Wide-ranging Online Data for Epidemiologic Research) system to query massive public health databases through natural language.
What you can do
- Mortality Data — Query the D76 (Detailed Mortality) and D77 (Underlying Cause of Death) databases for specific timeframes and regions.
- Birth Statistics — Access the D10 (Natality) database to analyze birth rates and maternal health metrics.
- Vaccine Safety — Query the VAERS (Vaccine Adverse Event Reporting System) database for safety monitoring data.
- Structured Queries — Execute complex ad-hoc queries using standard CDC parameters (B_, M_, V_, F_, O_ prefixes) for precise data extraction.
- Epidemiologic Research — Retrieve raw data for analysis in scientific research, public health policy, or educational projects.
How it works
- Subscribe to this server
- Enter your CDC WONDER API Access Token (if required by your proxy) or accept the Data Use Agreement
- Start querying epidemiologic data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Epidemiologists & Researchers — quickly pull mortality and birth statistics without navigating the complex WONDER web interface
- Public Health Officials — monitor health trends and vaccine safety reports directly from an AI assistant
- Data Scientists — fetch structured JSON epidemiologic data for integration into larger analytical workflows
Built-in capabilities (1)
g., D76 for Mortality). Provide the database ID and a JSON object of parameters (B_, M_, V_, F_, O_ prefixes). Query CDC WONDER epidemiologic databases
Why Cursor?
Cursor's Agent mode turns CDC WONDER (Epidemiologic Data) into an in-editor superpower. Ask Cursor to generate code using live data from CDC WONDER (Epidemiologic Data) and it fetches, processes, and writes. all in a single agentic loop. 1 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
CDC WONDER (Epidemiologic Data) in Cursor
CDC WONDER (Epidemiologic Data) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect CDC WONDER (Epidemiologic Data) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for CDC WONDER (Epidemiologic Data) in Cursor
The CDC WONDER (Epidemiologic Data) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
CDC WONDER (Epidemiologic Data) for Cursor
Every tool call from Cursor to the CDC WONDER (Epidemiologic Data) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Which databases can I access using this server?
You can query any database supported by the CDC WONDER API by providing its ID to the query_wonder_database tool. Common IDs include D76 (Detailed Mortality), D10 (Natality), and VAERS (Vaccine Adverse Event Reporting System).
How should I format the parameters for a query?
Parameters should be provided as a JSON object using the standard CDC prefixes: B_ for by-variables, M_ for measures, V_ for values, F_ for filters, and O_ for other options. The query_wonder_database tool handles the XML conversion for you.
Do I need to include the 'accept_datause_restrictions' parameter?
No. The query_wonder_database tool is designed to handle the data use restrictions agreement internally. You only need to provide the specific database ID and the analytical parameters for your search.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Shoplazza / 店匠
10 toolsGlobal E-commerce platform — manage products, orders, and inventory via AI.
ContentKing
10 toolsEnable your AI agent to fetch real-time SEO audit metrics and monitor website changes through ContentKing.
UniCourt
27 toolsAccess real-time legal data and court records — search cases, track updates, and analyze normalized attorney and judge data directly from your AI agent.
Donorbox
10 toolsEquip your AI agent to manage donations, track recurring plans, and monitor fundraising campaigns via the Donorbox API.