MewCP LogoAStheTech
MCPs
Use Cases

Use cases by category

Productivity & InboxInbox, calendar, and daily flowEngineering & DevOpsShip, debug, and run on-callSales & CRMPipeline, outreach, and dealsMarketing & GrowthCampaigns, SEO, and growthSupport & SuccessTriage tickets, keep customers happyFinance & OpsClose, reconcile, and expensesCreative & ContentGenerate assets and contentPeople & HiringHiring, onboarding, and HRResearch & DataSynthesize data and insights
See all use cases
Resources
BlogsProduct updates and storiesArticlesIntegration guides and code examples
PricingDocsSign in
MewCP Logo

Infrastructure You Can Trust for Agentic Products

X

Categories

  • Productivity & Docs
  • Developer Tools
  • CRM & Sales
  • Finance & Commerce
  • Data & Analytics
  • Marketing & SEO
  • Search & Web
  • Communication
  • View All Servers →

Resources

  • Blog
  • Docs
  • Privacy Policy
  • Terms of Service

Blogs

  • View All Blogs →

Articles

  • View All Articles →
Browse Servers|Pricing|Contact

Browse by Category

Productivity & Docs

  • Gmail
  • Google Drive
  • YouTube
  • Google Calendar
  • Google People
  • Google Classroom
  • Notion
  • ClickUp
  • Figma
  • Google Tasks
  • Cal
  • Monday
  • Luma
  • Notion MCP
  • Mem MCP
  • Linear MCP
  • Calendly MCP
  • Consensus MCP
  • Craft MCP
  • Close MCP
  • Dice MCP
  • Lumin PDF MCP
  • Develop21 MCP
  • Granola MCP
  • Lucid MCP
  • Mermaid Chart MCP
  • Fireflies MCP
  • ClickUp MCP
  • Miro MCP
  • Llamaindex MCP
  • Otter MCP
  • Mobbin MCP
  • Descript MCP
  • ToDoist MCP
  • SlidesGPT MCP

Developer Tools

  • Gemini
  • Veo
  • ClickUp
  • Firecrawl
  • Vercel
  • Apify
  • Github
  • Chef
  • Scientific Calculator
  • Figma
  • HTTP
  • Perplexity
  • Apify MCP
  • Hugging Face Hub MCP
  • Buildkite MCP
  • Cloudflare MCP
  • Context7 MCP
  • Ahrefs MCP
  • Sentry MCP
  • Brevo Docs MCP
  • X Docs MCP
  • Jev
  • Linear MCP
  • Calendly MCP
  • Craft MCP
  • DeepWiki MCP
  • Inspo MCP
  • Kernel MCP
  • Malwarebytes MCP
  • Mermaid Chart MCP
  • Supabase MCP
  • Microsoft Learn MCP
  • Webflow MCP
  • Scalar Docs MCP
  • Oneuptime MCP
  • Redocly MCP
  • Reducto Docs MCP
  • Llamaindex Docs MCP
  • B12 MCP
  • Lucid Docs MCP
  • Airwallex Docs MCP
  • Langfuse Docs MCP
  • Glen Docs MCP
  • AgentMail
  • Gogs Docs MCP
  • Netlify MCP
  • Neon MCP
  • Minlify Admin MCP
  • Mintlify Index MCP
  • Fern Docs MCP
  • Greptile MCP
  • Statssif Docs MCP
  • Scorecard MCP
  • Railway MCP

CRM & Sales

  • Google People
  • OneSignal MCP
  • Brevo Docs MCP
  • Brevo
  • Brevo MCP
  • Carbon Voice MCP
  • Clay MCP
  • Close MCP
  • Attio MCP
  • Clarify MCP
  • Hunter.io
  • Plain MCP
  • Modem MCP
  • Whats MCP

Finance & Commerce

  • Kite
  • Razorpay
  • Polymarket
  • Stripe
  • Binance
  • Upstox
  • Aiwyn MCP
  • Era-Context-MCP
  • Granted MCP
  • XDC AI MCP
  • Agentery MCP
  • Agent Embassy
  • Quick Commerce MCP
  • Longbridge MCP
  • Mercury MCP
  • Blockscout MCP
  • Octagon AI MCP
  • Stripe MCP
  • Taskrabbit MCP
  • SeatGeek MCP
  • Clarity AI MCP

Data & Analytics

  • Apify MCP
  • Cloudflare MCP
  • Ahrefs MCP
  • Candid MCP
  • Consensus MCP
  • Contentsquare MCP
  • Era-Context-MCP
  • Instinct MCP
  • legal Data Hunter MCP
  • Marcopolo MCP
  • Mixpanel MCP
  • MOSPI MCP
  • Hex MCP
  • OpenRevenue MCP
  • Statsig MCP
  • Synthesize Bio MCP
  • PostHog MCP
  • PopHIVE MCP

Marketing & SEO

  • YouTube
  • Google Business
  • Mailchimp
  • Google Search Console
  • OneSignal MCP
  • Cloudflare MCP
  • Brevo Docs MCP
  • Brevo
  • Brevo MCP
  • AirOps MCP
  • Clay MCP
  • Contentsquare MCP
  • Reelsmith MCP
  • GoDaddy MCP
  • Metricool MCP
  • Webflow MCP
  • Windsor MCP
  • Commonroom MCP
  • B12 MCP
  • Hunter.io
  • Get MCP Ads
  • Minlify Admin MCP
  • Zernio MCP

Search & Web

  • Web Scrapper
  • Firecrawl
  • Apify
  • Perplexity
  • Context.dev
  • Exa
  • Brave Search
  • Apify MCP
  • Ahrefs MCP
  • DeepWiki MCP
  • Dice MCP
  • GoDaddy MCP
  • Granted MCP
  • Microsoft Learn MCP
  • Viator MCp
  • Scholargateway MCP
  • Parallel MCP
  • Mintlify Index MCP
  • OpenWeather MCP
  • Simplescraper MCP
  • SearchApi MCP

Communication

  • Gmail
  • Google Meet
  • Google Calendar
  • Mailchimp
  • WhatsApp
  • Slack
  • OneSignal MCP
  • Brevo Docs MCP
  • Carbon Voice MCP
  • Hunter.io
  • Outlook
  • Nylas MCP
  • Resend MCP
  • Read AI MCP
  • Whats MCP

© 2026 MewCP. All rights reserved.

  1. Home
  2. MCPs
  3. PopHIVE MCP
PopHIVE MCP

PopHIVE MCP Integration for AI Agents

PopHIVE provides AI agents with access to community-level U.S. public health data, enabling them to explore disease trends, compare health indicators across states and counties, analyze vaccination rates and chronic conditions, and investigate social determinants of health using data from multiple sources.

v2.0.07 toolsNo auth
Open in ChatGPTChatGPT
Open in ClaudeClaude
Playground
VS CodeVS Code
Connected to PopHIVE MCP via MewCP.

Encrypted at rest, isolated from the model

Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.

Try asking

Everything PopHIVE MCP can do

Tools7

get_overview

read

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_status

read

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_trend

read

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_map

read

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.

compare

read

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_coverage

read

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_data

read

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: annual_wellness_visit, antimicrobial_resistance, babesiosis, breast_cancer_screening, campylobacter, cardiovascular_screening, census, cervical_cancer_screening, chlamydia_screening, colorectal_cancer_screening, combined7, community_health, copd, covid19, dengue, depression_screening, diabetes, diabetes_screening, diarrhea, dtap, ehrlichiosis, enteric_disease, firearm_injury, flu_vaccine_adult, haemophilus_influenzae, healthcare_access, heat_illness, hepa, hepb, hib, infant_mortality, influenza, injury_deaths, low_birth_weight, malaria, maternal_health, maternal_mortality, measles, mmr, obesity, opioid_overdose, opioid_use_disorder, pcv, pelvic_exam, pertussis, pneumococcal_vaccine_adult, polio, prostate_cancer_screening, rotavirus, rsv, salmonella, shigella, stec, strep, teen_births, vaccine_exemptions, varicella, vector_borne, west_nile, youth_wellbeing. 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.

Connect PopHIVE MCP to your agent

One endpoint, the same key, whichever client you use.

Apps

SDKs

Claude Desktop

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization: Bearer API_KEY"
      ]
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

  1. 01Open Claude Desktop → Settings → Developer → "Edit Config"
  2. 02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
  3. 03Save the file and restart Claude Desktop
  4. 04Start a new conversation — your tool will be available

One endpoint. Every service.

VS CodeAny agent
One Gateway

Apify MCP

OAuth

Consensus MCP

OAuth

legal Data Hunter MCP

OAuth

PopHIVE MCP

No auth

Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you

Separate connections░░░░░░░░░░░░░░░░░░░░░░░░░░░░27 tool definitions ~8.0k tokensWith MewCP░░░░░░░░░░░░░░░░░░░░░░░░░░░░4 meta-tools ~4.0k tokens

Built for AI agents

PopHIVE MCP runs through a gateway that holds the credentials, scopes the access and records every call.

Nothing to connect

  • PopHIVE MCP needs no credential, so there is no key to issue, store or rotate.
  • Add it to a toolset and start calling tools.

Credentials stay out of context

  • PopHIVE MCP credentials are resolved at the gateway and attached to the outbound call.
  • The agent sees tool results, never a token.

Ready to connect PopHIVE MCP?

Managed auth, hosted MCP servers, and every Gmail tool your agent needs.

Free to start.

  • Revoke an account and the next call stops working — no redeploy.
  • Scoped access, fully logged

    • Choose exactly which PopHIVE MCP tools an agent is allowed to call.
    • Every call is logged with its outcome, latency and which account it ran as.
    • Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

    One endpoint for every server

    • Reach PopHIVE MCP through the same MCP endpoint as the rest of your toolset.
    • Tools are discovered on demand, so 7 tools do not fill the context window.
    • Stateless: no sessions to keep alive and no reconnect logic.