NCHS - Leading Causes of Death: United States — cdc health mcp server MCP Resource

NCHS - Leading Causes of Death: United States is one of 3 resources on the cdc health mcp server MCP server. Connect the server and your client can attach it as context.

by client

How to attach NCHS - Leading Causes of Death: United States from your client

• Claude Code cdc health mcp server Resource/NCHS - Leading Causes of Death: United States run in your project directory
• Claude Desktop cdc health mcp server Resource/NCHS - Leading Causes of Death: United States ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor cdc health mcp server Resource/NCHS - Leading Causes of Death: United States ~/.cursor/mcp.json
• VS Code cdc health mcp server Resource/NCHS - Leading Causes of Death: United States .vscode/mcp.json
• Zed cdc health mcp server Resource/NCHS - Leading Causes of Death: United States ~/.config/zed/settings.json
• Windsurf cdc health mcp server Resource/NCHS - Leading Causes of Death: United States ~/.codeium/windsurf/mcp_config.json
• Cline cdc health mcp server Resource/NCHS - Leading Causes of Death: United States ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI cdc health mcp server Resource/NCHS - Leading Causes of Death: United States ~/.gemini/settings.json
• Grok cdc health mcp server Resource/NCHS - Leading Causes of Death: United States .mcp.json (in your project root)
• ChatGPT cdc health mcp server Resource/NCHS - Leading Causes of Death: United States Settings → Connectors → Advanced → Developer mode
• Claude.ai cdc health mcp server Resource/NCHS - Leading Causes of Death: United States Settings → Connectors → Add custom connector
• LangChain cdc health mcp server Resource/NCHS - Leading Causes of Death: United States pip install langchain-mcp-adapters

Other resources on this server

• CDC Dataset Catalog
• Provisional COVID-19 Deaths by Sex and Age

cdc health mcp server also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.