PopHIVE for AI agents
PopHIVE is Yale's harmonized US public health surveillance dataset covering disease, vaccination, and health outcome trends. Researchers and public health teams use it to track population health signals. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in PopHIVE.
Check a health trend over time
Pull a trend for a tracked health indicator to see how it has changed over months.
Compare regions on an indicator
Compare health outcome data across regions to spot where a signal is rising fastest.
Get current status read-only
Look up the current status of a tracked disease or vaccination indicator, read-only.
7 PopHIVE actions, graded by risk.
Every PopHIVE action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- pophive.get_mapGet map
- pophive.get_dataGet data
- pophive.get_trendGet trend
- pophive.get_coverageGet coverage
- pophive.get_overviewGet overview
- pophive.get_current_statusGet current status
- pophive.compareCompare
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
PopHIVE in three steps.
- 01Your users connect PopHIVEThey add their PopHIVE no auth on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls PopHIVE through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('pophive', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How PopHIVE connects.
PopHIVE needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
The same PopHIVE connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- No auth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use PopHIVE from any agent.
PopHIVE and Arc0, answered.
Can I use PopHIVE with Claude, ChatGPT or Cursor?
Yes. Connect PopHIVE to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the PopHIVE actions you allow.
How do users connect PopHIVE?
PopHIVE needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
Which PopHIVE actions can my agent take?
7 in total: 7 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in PopHIVE?
Yes. Allow read actions and deny writes in the PopHIVE policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call PopHIVE too?
Yes. The same PopHIVE connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug PopHIVE into your agent.
Your users connect PopHIVE once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan