PopHIVE MCP server icon

PopHIVE

by PopHIVE

Healthcare7 toolsNo Auth Required

Query Yale's harmonized US public-health surveillance data from your AI agent. Flu, COVID, RSV, measles, overdose, chronic disease and childhood vaccination coverage by state and county. 7 tools, all read-only, no sign-in.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect PopHIVE via MCP

https://mcp.pophive.org/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

PopHIVE Tools & Capabilities (7)

get_overviewRead-only

Cross-disease situation report for one US state or the nation — what's elevated, rising, declining, or stale across every PopHIVE topic. For straightforward single-slice questions only (e.g. "anything elevated in Connecticut?", "public health sitrep for Florida?"). If the answer needs anything beyond reading one precomputed evidence block, use get_data. Examples: "What's going on health-wise in Texas?", "Public health sitrep for Florida", "Anything elevated in Connecticut?" Not for: a single disease (get_current_status), time series (get_trend), ranking states by one disease (get_map). Call example: get_overview(geography='Texas') Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

get_current_statusRead-only

Current-status verdict for one disease in one US place — level, direction, and risk right now. For straightforward single-slice questions only (e.g. "is flu rising in Texas?", "how bad is COVID nationally?"). If the answer needs anything beyond reading one precomputed evidence block, use get_data. Examples: "Is RSV rising in Connecticut?", "How bad is flu nationally?", "What is the risk of measles in Texas?", "Current COVID situation in New York." Not for: trends over time (get_trend), ranking geographies (get_map), vaccination coverage (get_coverage). Call example: get_current_status(disease='rsv', geography='Connecticut') Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

get_trendRead-only

Trend over time for one disease in one US place — direction, peak, and change, optionally stratified or pinned to one source. For straightforward single-slice questions only (e.g. "how has RSV changed since January?", "flu trend in Ohio"). If the answer needs anything beyond reading one precomputed evidence block, use get_data. Examples: "What are the latest trends in COVID?", "How has flu changed since January?", "Diabetes trend in Ohio over 5 years." season_over_season evidence compares the current season to the immediately prior season only; for older seasons use get_data. Not for: a current-status verdict (get_current_status), ranking geographies (get_map), vaccination coverage (get_coverage). Call example: get_trend(disease='flu', geography='US', period='12w') Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

get_mapRead-only

Geographic ranking — which US states or counties are highest or lowest on one disease, by current level or recent change. For straightforward single-slice questions only (e.g. "which counties have the highest RSV?", "how does Texas rank on flu?"). If the answer needs anything beyond reading one precomputed evidence block, use get_data. Examples: "What parts of the US have the highest rates of flu right now?", "How do diabetes rates differ across the US by county?", "How does Texas rank?", "Which states are improving fastest on opioid overdose?" Not for: trends over time (get_trend), one place's status (get_current_status). Call example: get_map(disease='flu', geo_level='state', top_n=10) Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

compareRead-only

Side-by-side comparison of one disease across 2–5 US places, or agreement between surveillance sources in one place. For straightforward single-slice questions only (e.g. "is RSV worse in CT than NY?", "do wastewater and ED visits agree on COVID?"). If the answer needs anything beyond reading one precomputed evidence block, use get_data. Examples: "Is RSV worse in CT than NY?", "Compare diabetes in Texas vs California", "Do wastewater and ED visits agree on COVID?" Not for: one place's status (get_current_status), ranking many places (get_map). Call example: compare(disease='covid', geographies=['Texas', 'Florida']) Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

get_coverageRead-only

US childhood vaccination coverage — the rate for one vaccine in one place and whether it meets targets. For straightforward single-slice questions only (e.g. "kindergarten MMR rate in Idaho?", "is Texas below 95% MMR?"). If the answer needs anything beyond reading one precomputed evidence block, use get_data. Examples: "Kindergarten MMR rate in Idaho?", "Is Texas below 95% MMR?", "Polio vaccination rate in Connecticut." Not for: disease activity (get_current_status), trends (get_trend), coverage rankings across states (get_map with disease='mmr'). Call example: get_coverage(vaccine='mmr', geography='Idaho') Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

get_dataRead-only

Data catalog and raw-data gateway. The six specialized tools answer single-slice questions — current status, trend, map/ranking, A-vs-B compare, coverage — with server-verified evidence; try them first, escalating here costs one call. Use get_data when evidence can't carry the answer: multi-stratum gaps, history beyond the served window, complete lists, cross-dataset joins, custom math. Flow: (1) catalog, (2) disease='about' for the guide, (3) view schema + data_url, (4) download and compute — results are yours but carry the caveats and aren't server-verified. include_query=true returns a runnable pandas snippet. Topics: adhd, annual_wellness_visit, anxiety, breast_cancer_screening, cardiovascular_screening, cervical_cancer_screening, chlamydia_screening, colorectal_cancer_screening, combined7, covid19, depression, depression_screening, diabetes, diabetes_screening, dtap, firearm_injury, flu_vaccine_adult, heat_illness, hepa, hepb, hib, influenza, injury_deaths, measles, mmr, obesity, opioid_overdose, opioid_use_disorder, pcv, pelvic_exam, pneumococcal_vaccine_adult, polio, prostate_cancer_screening, rotavirus, rsv, vaccine_exemptions, varicella. Examples: "What does PopHIVE track?", "Do you have Lyme disease data?", "Vaccination gaps across insurance types", "Raw RSV data for Connecticut." Not for: 'is flu rising in Texas?' → get_current_status; 'rank states by COVID wastewater' → get_map; 'is RSV worse in CT than NY?' → compare. Call example: get_data(disease='rsv', view='overall_trend') Scope: US-only aggregate surveillance; relay the precomputed evidence, never re-derive numbers.

Read from the server on 2026-08-16, including each tool's own safety annotations.

Limits

  • Not for clinical use. PopHIVE's legal disclaimer states the statistical outputs are research tools for public health and medicine, are not intended for clinical decision making, and are not intended for the diagnosis or treatment of patients. It adds that they do not replace the expertise of healthcare professionals.
  • Aggregate only, never individual. The data is described as public, aggregate and de-identified, containing no PII or PHI. There is no tool that returns a person-level record.
  • United States only. The documentation states the server excludes global estimates, household surveys and modeled burden-of-disease. One forecast product is included: an NWS HeatRisk heat-illness index.
  • County granularity is uneven. get_overview accepts no counties at all, its schema noting most topics are state-level, and get_coverage supports county rankings for MMR only.
  • Rate limited per IP. PopHIVE's troubleshooting documents 403 responses as an AWS WAF per-IP rate limit, and recommends self-hosting for heavy use. No numeric threshold is published.
  • Season-over-season comparison is shallow. The get_trend schema states its season-over-season evidence compares the current season to the immediately prior season only; older seasons require get_data.
  • A known upstream gap. PopHIVE's troubleshooting notes the District of Columbia may be absent from some chronic-disease state comparisons.
  • Downloaded data is not server-verified. Anything you compute from a get_data download falls outside the server-side evidence guarantee and must carry the dataset's caveats.
  • Upstream terms still apply. PopHIVE states that upstream sources retain their own terms, and that Epic Cosmos and Google Health Trends data among others require attribution to those providers.
  • We did not exercise any tool. Our check was a read-only initialize and tools/list handshake. Behaviour above comes from the server's own tool descriptions and PopHIVE's documentation, not from calling anything.

Frequently asked questions

Does the PopHIVE MCP server need an account or API key?

No. PopHIVE's documentation states there is no API key and no OAuth, and that you point a client at the URL. We opened an anonymous handshake against the endpoint on 2026-08-16 and the server returned all seven tools without a credential. PopHIVE's privacy policy adds that the Service has no accounts, logins or session state.

What health topics and geographies does PopHIVE cover?

PopHIVE's documentation states the server exposes 111 datasets across 37 topics through 7 tools. The get_data tool schema lists those topics, including influenza, covid19, rsv, measles, diabetes, obesity, opioid_overdose, firearm_injury, heat_illness, anxiety, depression and adhd. Coverage is the United States only: national, state, county, DC and five territories.

Can PopHIVE give medical advice or data about an individual?

No. PopHIVE's documentation states the data is public, aggregate and de-identified, containing no PII or PHI. Its legal disclaimer says the statistical outputs are research tools, are not intended for clinical decision making, and are not intended for diagnosis or treatment of patients. Every tool returns population-level surveillance figures only.

How current is PopHIVE data, and does it lag?

It varies by dataset rather than being one fixed lag. Every PopHIVE response carries a data_through field giving the latest observation date, plus caveats and provenance, per its documentation. The get_overview tool buckets topics as stale when a signal has not refreshed, so the connector reports its own staleness instead of you having to infer it.

Why does the PopHIVE connector return 403 errors?

You have hit a per-IP rate limit enforced by AWS WAF, according to PopHIVE's troubleshooting table. Its documented fix is to wait a few minutes, or self-host for heavy use. This is a rate limit rather than an authentication failure — the server is a no-auth endpoint and never asks for a credential.

Why does the PopHIVE connector prompt for OAuth or a login?

Because the client probed a discovery path. PopHIVE's troubleshooting notes say it deliberately returns a JSON 404 on the OAuth and OpenID discovery paths under /.well-known/, and that you should leave authentication blank. The documented cause of a genuine connection failure is instead a URL that does not end in /mcp.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Healthcare
Developer
PopHIVE
Tools
7
Domain
mcp.pophive.org

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.