CDC PLACES Health Data
REMOTE · MCP.OLYPORT.COM · SCANNED SEP 24
County and tract-level health outcomes, behaviors, and preventive services from CDC PLACES
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 641 tokens (~128/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CDC PLACES Health Data MCP server?
CDC PLACES Health Data is a hosted endpoint at https://mcp.olyport.com/cdc-places/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.olyport.com
claude mcp add --transport http com-olyport-cdc-places 'https://mcp.olyport.com/cdc-places/mcp'
{
"mcpServers": {
"com-olyport-cdc-places": {
"url": "https://mcp.olyport.com/cdc-places/mcp"
}
}
} {
"servers": {
"com-olyport-cdc-places": {
"type": "http",
"url": "https://mcp.olyport.com/cdc-places/mcp"
}
}
} [mcp_servers.com-olyport-cdc-places] url = "https://mcp.olyport.com/cdc-places/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-olyport-cdc-places": {
"type": "remote",
"url": "https://mcp.olyport.com/cdc-places/mcp",
"enabled": true
}
}
} openclaw mcp add com-olyport-cdc-places --url 'https://mcp.olyport.com/cdc-places/mcp' --transport streamable-http
mcp_servers:
com-olyport-cdc-places:
url: "https://mcp.olyport.com/cdc-places/mcp" {
"McpServers": {
"com-olyport-cdc-places": {
"Transport": "http",
"Url": "https://mcp.olyport.com/cdc-places/mcp"
}
}
} assistant mcp add com-olyport-cdc-places -t streamable-http -u 'https://mcp.olyport.com/cdc-places/mcp'
{
"mcpServers": {
"com-olyport-cdc-places": {
"type": "http",
"url": "https://mcp.olyport.com/cdc-places/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 77
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.olyport.com/cdc-places/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.olyport.com | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6ab1c2dfb0fcb68c1046393bb51c5b1117b |
| SANs: mcp.olyport.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.olyport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| olyport.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.olyport.com/cdc-places/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.olyport.com/cdc-places/mcp | HTTPS enforced | 308 | https://mcp.olyport.com/cdc-places/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_counties ~138
Compare specific CDC PLACES measures across multiple counties. Returns a side-by-side comparison of selected health measures for the given counties. Useful for benchmarking one county against peers. Args: fips_list: List of 5-digit county FIPS codes (e.g. ['53033', '53053', '06037']). Maximum 10 counties per request. measures: List of PLACES measure IDs to compare (e.g. ['DIABETES', 'OBESITY']). Maximum 10 measures per request.
| Name | Type | Req | Description |
|---|---|---|---|
| fips_list | array | yes | – |
| measures | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_county_measures ~140
Get all CDC PLACES health measures for a county. Returns up to 36 measures including health outcomes (diabetes, obesity, heart disease, etc.), health behaviors (smoking, binge drinking), preventive services (checkups, screenings), and health status indicators. Args: county_fips: 5-digit county FIPS code (e.g. '53033' for King County, WA). Must be a string, not an integer. year: Optional release year to filter by. Omit for the most recent data.
| Name | Type | Req | Description |
|---|---|---|---|
| county_fips | string | yes | – |
| year | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_measure_by_state ~135
Get one CDC PLACES measure for all counties in a state. Useful for comparing a specific health metric (e.g. DIABETES, OBESITY) across all counties within a state. Returns the most recent data year. Args: state_abbr: Two-letter state abbreviation (e.g. 'WA', 'CA'). measure_id: PLACES measure ID (e.g. 'DIABETES', 'OBESITY', 'BPHIGH'). Use search_measures to find valid IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| measure_id | string | yes | – |
| state_abbr | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_tract_measures ~133
Get all CDC PLACES health measures for a census tract. Returns tract-level estimates for health outcomes, behaviors, preventive services, and health status indicators. Tract-level data uses small area estimation and may have wider confidence intervals than county data. Args: tract_fips: 11-digit census tract FIPS code (e.g. '53033005300'). Must be a string, not an integer. year: Optional release year to filter by. Omit for the most recent data.
| Name | Type | Req | Description |
|---|---|---|---|
| tract_fips | string | yes | – |
| year | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_measures ~95
Search available CDC PLACES measures by name or category. Returns matching measure IDs, names, and categories. Use this to find the correct measure_id for other tools. Categories: Health Outcomes, Health Behaviors, Prevention, Health Status. Args: keyword: Search term (e.g. 'diabetes', 'smoking', 'prevention', 'heart').
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the CDC PLACES Health Data MCP server?
CDC PLACES Health Data is an MCP server listed in the public MCP registry as com.olyport/cdc-places. County and tract-level health outcomes, behaviors, and preventive services from CDC PLACES. This page covers its hosted endpoint (https://mcp.olyport.com/cdc-places/mcp).
Is the CDC PLACES Health Data MCP server safe to use?
CDC PLACES Health Data scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CDC PLACES Health Data MCP server expose?
CDC PLACES Health Data exposes 5 tools: get_county_measures, get_tract_measures, get_measure_by_state, search_measures, compare_counties. Their descriptions and schemas cost roughly 641 tokens of context every time the server is loaded.
Does the CDC PLACES Health Data MCP server require authentication?
No. We connected to CDC PLACES Health Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CDC PLACES Health Data MCP server still maintained?
CDC PLACES Health Data is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.