hrsa_coveredEntities340b_search — Healthparse Healthcare Data Gateway MCP Tool
hrsa_coveredEntities340b_search
(hrsa covered entities340b search) is one of 42 tools on the
Healthparse Healthcare Data Gateway
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call hrsa_coveredEntities340b_search from your client
- Claude Code Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search run in your project directory
- Claude Desktop Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search ~/.cursor/mcp.json
- VS Code Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search .vscode/mcp.json
- Zed Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search ~/.config/zed/settings.json
- Windsurf Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search ~/.codeium/windsurf/mcp_config.json
- Cline Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search ~/.gemini/settings.json
- Grok Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search .mcp.json (in your project root)
- ChatGPT Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search Settings → Connectors → Advanced → Developer mode
- Claude.ai Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search Settings → Connectors → Add custom connector
- LangChain Healthparse Healthcare Data Gateway hrsa_coveredEntities340b_search pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gateway https://api.healthparse.io/mcpOther tools on this server
- hcris_hospital_search
- hcris_hospital_byCcn
- hcris_asc_search
- hcris_provider_search
- irs990_org_search
- irs990_org_byEin
- irs990_officers_search
- sanctions_leie_search
- oews_wage_search
- carecompare_hospitals_search
- carecompare_hospitals_byCcn
- carecompare_snf_search
- carecompare_snf_byCcn
- carecompare_home-health_search
- carecompare_home-health_byCcn
- carecompare_hospice_search
- carecompare_hospice_byCcn
- carecompare_dialysis_search
- carecompare_dialysis_byCcn
- hpt_rates_search
- sanctions_screen
- hpt_code_stats
- hcris_hospital_financials
- providers_events_feed
- hospitals_capex_signals
- providers_provider360
- manufacturers_search
- manufacturers_openPayments
- hrsa_healthCenters_search
- hrsa_hpsa_search
- nppes_enumeration_search
- prescribers_partDByDrug_search
- prescribers_partDClassYoyDelta_search
- prescribers_partDClassWhitespace_search
- prescribers_partDAtypicalSpecialty_search
- prescribers_partDBrandShareShift_search
- prescribers_lookup_search
- prescribers_partD_search
- openPayments_recipients_search
- openPayments_recipients_yoyIncrease_search
- manufacturers_openPayments_yoyIncrease_search
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.