Claude PopHIVE connectorWhat Claude can tell you from Yale's US public health data.
The Claude PopHIVE connector exposes 7 tools: 7 read, 0 write. Yale's server hands Claude ready-computed answers on US disease activity, trends, rankings and childhood vaccine coverage, with no account to open. Here is what each tool covers and where the data stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query PopHIVE
PopHIVE gathers US surveillance signals that usually live in separate places: CDC systems, Epic Cosmos, wastewater monitoring, Google Health Trends. With the connector on, you ask Claude a plain question about a disease and a place, and it answers from figures the Yale server has already computed, with their caveats and sources attached. Nothing here is personal: the data is public, aggregate and de-identified.
Get the picture for one state in a single reply. Ask about one state, or the whole country, and Claude calls get_overview: it comes back with what is running high, rising, falling or out of date across every topic PopHIVE tracks.
Rank places on one disease. get_map ranks US states or counties on a single disease, by current level or by recent change, so the answer starts from a list the server computed with its sources attached.
Check a vaccination target. get_coverage returns the childhood vaccination rate for one vaccine in one place and says whether it meets its target; county detail exists for MMR only.
What it will not do: PopHIVE covers the United States only, with no global estimates, so a question about another country gets no answer from it. None of the 7 tools writes anything, and nothing runs on a schedule: Claude only queries while it is answering you. For a recurring alert when a figure moves, an automation platform is the right tool; our Integrations hub lists them.
Five words before you connect
Claude's vocabulary for this connector, in one minute.
- Connector
- The link you add once between Claude and an outside service, so Claude can draw on it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude chooses the ones it needs by itself; the directory lists them by name.
- Approval
- The confirmation Claude waits for before an action that changes an account. Pure lookups like these rarely need one.
- Directory
- The official catalogue where each connector has its own sheet: publisher, purpose and the list of tools it exposes.
- MCP
- The shared standard connectors rely on, the piece that lets an assistant talk to an outside service such as PopHIVE.
Connect PopHIVE to Claude in three steps
- 01
Find PopHIVE in Claude
Open Claude's settings, go to Customize then Connectors, and look for PopHIVE in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on for the organisation before members can use it.
- 02
Add it from its row
Click Connect on the PopHIVE row; there is no sign-in window to go through after that. If the connection breaks later, use Disconnect and add it again from the same row.
- 03
No sign-in to complete
There is no service account behind this connector. Yale's documentation says the server asks for no API key and no login, so there is no authorization screen to review. Once added, Claude reaches for its tools when a question calls for them.
The 7 tools, sorted by what they do
PopHIVE gives Claude 7 tools: 7 that read your account, 0 that change something in it.
All seven read, and Yale describes every one in its documentation and in the list its server publishes. Six give a verdict on a single question; the seventh opens the raw data. Names stay exactly as Claude shows them.
- 7 read
What Claude reads (7)
7 toolsSeven tools that look up public figures without changing anything.
get_overview
Builds a cross-disease situation report for one US state or for the whole country: which PopHIVE topics are running high, rising, declining or stale. Yale's documentation sets its geography at state, DC, territory or national level, with no county view.
get_current_status
Gives a verdict on one disease in one US place right now: its level compared with the peak of the trailing two years, its direction and the risk. Yale's server computes that verdict itself, with provenance and caveats attached.
get_trend
Traces how one disease moved in one US place over time, with its direction, peak and net movement, and can stratify the results or pin them to a single source. Its season-over-season evidence only sets the current season against the one just before.
get_map
Ranks US states or counties as highest or lowest on a single disease, either by current level or by how it moved lately. Yale's documentation sets the list length at ten places by default, adjustable within a fixed cap.
compare
Puts two to five US places side by side on one disease, or checks whether different surveillance sources agree inside a single place. It is the tool that answers "here or there" and "do the signals match".
get_coverage
Returns the US childhood vaccination rate for one vaccine in one place and says whether it meets its targets. Yale notes that county detail exists for MMR alone; for other vaccines the answer stays at state level.
get_data
Opens the data catalog and the raw datasets for questions the six verdict tools cannot settle: gaps across several strata, history beyond the served window, complete lists, joins across datasets or custom calculations. Yale warns that results built this way are not verified by the server.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. Here that rarely comes up: Yale describes every tool as read-only.
On Team and Enterprise, workspace owners decide whether a member may let some actions through without being asked again. They can also limit what a connector may do across the organisation, and nobody overrides that from their own account. Usually Claude works with the rights of the person who connected; with PopHIVE there is no personal account at all, so everyone sees the same public, aggregate figures. The official read or write labels per tool only appear inside a connected account's settings, not on a public page.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. For PopHIVE, as for every other connector, that answer is published nowhere.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before members can use it. For the current state of this one, check its sheet in the official directory. Worth knowing: only Yale documents this connector; no Claude help article covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it replies to you; nothing fires when a disease starts rising.
A tool list that shows only reading is an observed floor rather than a guarantee. The directory's verification badge is not a security audit, and Anthropic states on every sheet that it does not pick the tools a publisher exposes or vouch that they behave as described. Here the publisher is Yale School of Public Health. Its own documentation adds the limits below, which matter more than anything about permissions.
Need help connecting PopHIVE to Claude?
A person reads every message.
