SolvingHealth federal health data
Read-only US federal health data lookups for NPI, FDA clearances, recalls and trials
- Pricing
- Open source
- Platforms
- API, CLI, Web
- Runs
- Remotely
- Version
- 1.1.0
- Listing updated
- today
Similar MCP servers
About SolvingHealth federal health data
SolvingHealth federal health data is an open-source MCP server for health and science. It runs as a hosted remote server, so there is nothing to install locally.
The README says this server wraps public US federal health datasets behind one call shape: NPI provider records, FDA 510(k) clearances, device recalls and adverse events, drug labels, clinical trials and CMS hospital records. Each result carries the upstream source URL and the time it was retrieved, so a figure can be checked against the original government source.
The server is exposed over MCP Streamable HTTP and can be added to Claude Desktop through mcp-remote, or used through a keyless public REST API and a zero-dependency stdio server in the repository. No account or key is required, and the project states that nothing is stored.
The project is aimed at developers and researchers building tools on federal health data, and at people doing lookups who want sourced results. It is explicitly not a source of medical, coding, billing or legal advice, and patient information must not be sent to it.
Install
Run in a terminal
claude mcp add --transport http solvinghealth-data-tools https://solvinghealth.com/api/data-mcpAdd to Settings → Connectors → Add custom connector
https://solvinghealth.com/api/data-mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"solvinghealth-data-tools": {
"url": "https://solvinghealth.com/api/data-mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"solvinghealth-data-tools": {
"type": "http",
"url": "https://solvinghealth.com/api/data-mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"solvinghealth-data-tools": {
"serverUrl": "https://solvinghealth.com/api/data-mcp"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://solvinghealth.com/api/data-mcpEnter a Name (for example "SolvingHealth federal health data"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"solvinghealth-data-tools": {
"type": "http",
"url": "https://solvinghealth.com/api/data-mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (11)
Taken from the project documentation; the running server may differ.
- find_providers
- Search NPI provider records.
- get_provider
- Retrieve a single provider record.
- search_clearances
- Search FDA 510(k) clearances.
- search_device_recalls
- Search FDA device recalls.
- search_adverse_events
- Search FDA adverse event reports.
- search_drug_labels
- Search drug label records.
- search_trials
- Search ClinicalTrials.gov records.
- search_hospitals
- Search CMS hospital records.
- list_endpoints
- List available API endpoints and their status.
- caregiver_questionnaire
- Forwards to the ClinicalSwipe caregiver navigator questionnaire.
- caregiver_plan
- Forwards to the ClinicalSwipe caregiver navigator plan.
What it does
- Federal provider lookups
- Searches NPI registry records and retrieves individual provider details by taxonomy and location.
- FDA device clearance search
- Queries FDA 510(k) clearances and related device recall and adverse event records.
- Drug label and trial search
- Finds drug labels and clinical trial records from openFDA and ClinicalTrials.gov.
- Hospital records from CMS
- Searches CMS hospital provider data through the same call shape as other lookups.
- Source and timestamp on results
- Every result includes the upstream source URL and retrieval time for verification.
- No key or account needed
- Works over MCP or plain HTTP without registration, and the README says no data is stored.
Good for
- Look up an NPI record for a provider from an AI assistant
- Check whether a medical device has an FDA 510(k) clearance
- Review recent device recalls or adverse event reports for a product
- Search clinical trials by condition from within an MCP client
- Pull CMS hospital records for comparison or research
Pricing
Open source
Free public API and Apache-2.0 open source code; no paid plan mentioned.
Prices change. Check solvinghealth.com before you buy.
SolvingHealth federal health data FAQ
Does it require an API key or account?
No. The README states there is no key and no account, and the HTTP API can be called directly with curl.
Can I send patient information to it?
No. The README and website both say not to send patient information to the server or any endpoint on the site.
How do I add it to Claude Desktop?
The website gives a config block that runs mcp-remote against the server URL, after which Claude Desktop must be fully quit and reopened.
What is the license?
The README says the code is licensed under Apache-2.0.
Is SolvingHealth federal health data free?
Yes. SolvingHealth federal health data is open source, so you can use and self-host it for free.
How do I add SolvingHealth federal health data to Claude Code?
Run this command in your terminal: claude mcp add --transport http solvinghealth-data-tools https://solvinghealth.com/api/data-mcp
What are the best alternatives to SolvingHealth federal health data?
The closest alternatives to SolvingHealth federal health data are Pharma, FDA & ClinicalTrials.gov Intelligence MCP, Public Health, Meddata, ClinX open data: 340B and health centers and US Healthcare Provider (NPI) Lookup MCP.
Where this comes from
- Description: written from the project's README, the project's website and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.
