
CDC PLACES Health Data
Pull county- and census-tract-level CDC PLACES health outcomes and behaviors to size a geo-targeted wellness or civic app.
Overview
CDC PLACES Health Data is a Validate-phase MCP server that exposes county and tract-level CDC PLACES outcomes, behaviors, and preventive services to coding agents over streamable HTTP.
What is this MCP server?
- CDC PLACES: health outcomes, behaviors, and preventive services at county and tract granularity
- Streamable-http MCP remote v1.0.0 at mcp.olyport.com/cdc-places/mcp
- Geographic health baselines for maps, eligibility rules, and persona research
- Agent-driven queries without standing up a CDC PLACES ETL pipeline
- Complements SVI and WONDER MCP servers for fuller local health pictures
- Server version 1.0.0
- Remote endpoint https://mcp.olyport.com/cdc-places/mcp (streamable-http)
- Granularity: county and census tract per CDC PLACES
What problem does it solve?
Geo-health products stall when founders cannot quickly compare tract-level chronic disease and behavior rates while defining MVP regions and features.
Who is it for?
Solo builders validating localized health, fitness, or benefits ideas that need census-tract and county prevalence context.
Skip if: Products requiring individual patient records, sub-tract clinical feeds, or non-US geographies PLACES does not cover.
What do I get? / Deliverables
Registering the MCP lets your agent pull PLACES baselines into scope docs, map specs, and integration designs for targeted launches.
- Tract and county health baseline tables for MVP geography decisions
- Agent-generated scope notes citing PLACES outcomes and behaviors
- Integration stubs for map or eligibility features using PLACES dimensions
Recommended MCP Servers
Journey fit
PLACES answers whether local prevalence supports your wedge—builders use it when narrowing MVP geography and feature set during validation. Scope subphase needs tract-level baselines so you do not over-build for markets your data cannot support.
How it compares
Small-area CDC PLACES query layer, not a patient portal or claims database.
Common Questions / FAQ
Who is CDC PLACES Health Data for?
Builders and agent users scoping US community health, wellness, or civic apps who need official tract and county health outcome baselines.
When should I use CDC PLACES Health Data?
Use it while validating scope—choosing launch counties, defining map layers, or writing personas backed by local preventive-care and behavior statistics.
How do I add CDC PLACES Health Data to my agent?
Configure your MCP client with remote URL https://mcp.olyport.com/cdc-places/mcp (streamable-http), then call the server tools from your agent session.