Vaers MCP server

vaers

VAERS (Vaccine Adverse Event Reporting System) report counts — by vaccine, manufacturer, symptom, year and severity. Fleet #1294.

Part of Pipeworx — an MCP gateway connecting AI agents to 1558+ live data sources.

A VAERS report is not a confirmed adverse event — read this first

Anyone can file a VAERS report — a patient, a parent, a clinician, a manufacturer — and VAERS does not verify what's in it. A rise in report counts for a vaccine can reflect more doses given, more media attention, or a reporting-requirement change just as easily as a real safety signal. CDC and FDA say this about their own data:

The number of reports alone cannot be interpreted as evidence of a causal

association between a vaccine and an adverse event, or as evidence about

the existence, severity, frequency, or rates of problems associated with

vaccines. Reports may include incomplete, inaccurate, coincidental, and

unverified information.

—

Every tool response below carries that disclaimer and a literal iscausal: false field, so a model reading the payload cannot round a report count up into a causal claim. No tool here returns a single report's free text (SYMPTOMTEXT, HISTORY, LABDATA, OTHERMEDS, CUR_ILL, ALLERGIES are not even stored — see the migration comment) — everything is a count, by design.

Tools

Counting convention — read before comparing numbers across tools

A report that names more than one vaccine is counted once per vaccine — the same convention CDC WONDER itself uses for VAERS. So summing reportcount across every vaccine for a year can exceed that year's unique report total (vaerscoverage.totaluniquereports). Symptom counts are mentions: a report naming several symptoms and/or several vaccines contributes to each combination.

Auth

None — no key, no account. This pack answers from pre-aggregated report counts built from the seed described below.

Data source and how it got here

VAERS, co-run by CDC and FDA — public data files at . US federal public-domain data.

Every automated surface CDC exposes for VAERS is closed to a script:

dataset but the endpoint returns HTTP 500 with no error message for every request shape tried — recognized but not enabled, undocumented.

• The bulk-download page is CAPTCHA-gated (image word-verification).
• CDC WONDER's own XML API documents VAERS (database D8) as a live

queryable Socrata datasets.

• data.cdc.gov's two VAERS listings are href pointers back to WONDER, not

Full write-up: docs/vaers-access-finding.md.

So Bruce's ruling (task #1294, 2026-09-07) is seed-plus-manual-refresh: he downloads AllVAERSDataCSVS.zip (the single archive covering every year, 1990-2026, plus non-domestic reports) by hand from the datasets page above, and this pack's loader ingests it. He explicitly did not authorize the outward-facing option (emailing CDC to ask for the API to be enabled) — that still needs his own OK if it's ever pursued.

Storage — why aggregates, not raw rows

Shortened. The full README is on GitHub.