SolvingHealth federal health data
● Activeio.github.blainomd/solvinghealth-data-tools
Read-only US federal health data with sources: NPI, FDA 510(k), recalls, trials, hospitals.
Connect this server
One click to install, or copy the config below. Suits: Cursor · HTTP clients.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"solvinghealth-data-tools": {
"url": "https://solvinghealth.com/api/data-mcp"
}
}
}claude mcp add --transport http solvinghealth-data-tools https://solvinghealth.com/api/data-mcpcode --add-mcp '{"name":"solvinghealth-data-tools","type":"http","url":"https://solvinghealth.com/api/data-mcp"}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Health & Science
- Version
- 1.1.0
- Registry
- active
- Published
- 11/19/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Looks healthy: SolvingHealth federal health data is maintained, open source, hosted endpoint answering without a key.
- Maintained
- Active
- Last commit 3 days ago (Nov 19, 2026), 0 open issues.
- Official registry
- Active
- Published as io.github.blainomd/solvinghealth-data-tools in the official MCP registry, version 1.1.0.
- Source
- Open source, Apache-2.0
- Public repository under the Apache-2.0 licence, 0 stars, 0 forks.
- Runs
- Hosted by the publisher
- Your client talks to solvinghealth.com: prompts and tool arguments leave your machine for that host.
- Credentials
- None needed to connect
- The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.
Live check
checked Nov 22, 2026, 07:08 UTCStatus history & uptime →The endpoint answered the MCP handshake as "solvinghealth" and listed 12 tools. Answering since Nov 21, 2026.
Context cost ≈ 1.8k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 12 tools.
Tools (12)
find_providers8 paramsSearch the CMS NPPES NPI registry for clinicians or organizations. Use for "find orthopedic surgeons in Colorado", "orthopaedic surgeons in ZIP 80303", verifying a practice name, or listing a taxonomy in a city. Returns NPI, name, credential, taxonomies with state licenses, addresses and secondary practice locations.
Show parametersHide parameters
statestringTwo-letter state code, e.g. COcitystringCity namepostal_codestring5-digit US ZIP code (or ZIP+4). Matches practice-location addresses, including secondary practice locationstaxonomystringSpecialty as NPPES words it, e.g. "Orthopaedic Surgery" (British spelling)first_namestringGiven name of an individual providerlast_namestringFamily name of an individual providerorganizationstringOrganization namelimitintegerMax results, 1-50 (default 10)
- get_provider1 param
Look up one provider by 10-digit NPI. Use to verify an NPI is real, active, and matches the specialty you expect.
Show parametersHide parameters
npistringrequiredThe 10-digit NPI
search_clearances4 paramsSearch FDA 510(k) device clearances (openFDA). Use to check whether a device type has been cleared, who cleared it, and when — e.g. "is there a cleared knee goniometer", "what did Stryker clear since 2024".
Show parametersHide parameters
qstringDevice name to match, e.g. "knee"applicantstringCompany name, e.g. "Stryker"sincestringEarliest decision date, YYYYMMDDlimitintegerMax results, 1-50
search_device_recalls2 paramsSearch FDA device recall records. Use for safety history on an implant or device family before citing it.
Show parametersHide parameters
qstringProduct description to matchlimitintegerMax results, 1-50
search_adverse_events2 paramsSearch FDA MAUDE device adverse event reports. Use for real-world failure modes reported for a device type.
Show parametersHide parameters
qstringGeneric device name, e.g. "knee prosthesis"limitintegerMax results, 1-50
search_drug_labels4 paramsSearch FDA structured drug labeling (SPL) for indications and boxed warnings. Use to check what a drug is labeled for.
Show parametersHide parameters
qstringBrand or generic namebrandstringBrand namegenericstringGeneric namelimitintegerMax results, 1-50
search_trials5 paramsSearch ClinicalTrials.gov (API v2) for registered studies. Use for "what is recruiting for knee OA", evidence landscape questions, or checking whether a claimed trial exists.
Show parametersHide parameters
conditionstringCondition, e.g. "knee osteoarthritis"interventionstringIntervention or drug/device namelocationstringWhere the study runs: a state, city or country, e.g. "Colorado"statusstringOverall status, e.g. RECRUITING, COMPLETEDlimitintegerMax results, 1-50
search_hospitals4 paramsSearch the CMS Hospital General Information file: ownership, type, emergency services, and overall star rating.
Show parametersHide parameters
statestringTwo-letter state codecitystringCity namenamestringPartial facility namelimitintegerMax results, 1-50
suspension_deadlines2 paramsMedicare payment suspension: the 15-day rebuttal deadline and the CMS determination deadline from the date on the notice, with the 42 CFR 405.370-405.375 rules quoted from eCFR. A pure calculation; nothing is stored.
Show parametersHide parameters
noticestringrequiredDate on the suspension notice, YYYY-MM-DDrebuttal_receivedstringDate CMS received the rebuttal, YYYY-MM-DD (optional)
List every API endpoint, whether it is live, and which government dataset it reads. Call this first if unsure what data is available — it also names what is deliberately NOT implemented and why, and lists open endpoints that run elsewhere, such as the family caregiver navigator.
caregiver_questionnaire1 paramGet the questions for ClinicalSwipe's family caregiver navigator: who is being cared for, their coverage, family doctor, what is going on, military service, money and state. Returns each question with its answer codes, plus the full resource catalog, each resource with its official source URL and the date it was checked. format "fhir" returns the FHIR R4 Questionnaire instead. Call this before caregiver_plan so the answers use the codes it lists.
Show parametersHide parameters
formatstring"json" (default): plain questions and the catalog. "fhir": the FHIR R4 Questionnaire.
caregiver_plan3 paramsBuild a family caregiver's plan with ClinicalSwipe's navigator: public programs first, then what to ask the family doctor, then neighbor help, then what is not open yet, labeled as such. Every step names its source page and the date it was checked. A step that needs a clinician says who, what and why, and signs: true marks only the steps a program requires a clinician to sign or certify. General information from official program pages, not medical, legal or financial advice; each program decides its own eligibility. The answers go to clinicalswipe.com, which does not store or log them. Send no names or identifiers.
Show parametersHide parameters
answersobjectPlain answers keyed by the questionnaire's question ids, using the codes caregiver_questionnaire lists, e.g. {"coverage":"medicare","doctor":"yes","state":"CO",questionnaire_responseobjectA FHIR R4 QuestionnaireResponse to the navigator questionnaire, instead of answers.formatstring"json" (default) or "fhir" for a FHIR R4 CarePlan. A QuestionnaireResponse always gets a CarePlan.
Checked by Serverdex with a plain initialize + tools/list call to solvinghealth.com/api/data-mcp, no credentials, about once a day. A failed check is never a removal.
On GitHub
read Nov 21, 2026- Stars
- 0
- Forks
- 0
- Last push
- Nov 19, 2026
- License
- Apache-2.0
JavaScriptai-agentsclinicaltrialscmshealthcaremcpnpiopenfda
From the README
SolvingHealth data tools The code behind the public, read-only federal health data lookups at solvinghealth.com: NPI records, FDA 510(k) clearances, device recalls and adverse events, drug labels, clinical trials and CMS hospitals. Every result carries the upstream source URL and the time it was retrieved, so you can check any fact against the source. No key. No account. Nothing stored. Send no patient information. Use it Over MCP (HTTP, nothing to install): Or run the MCP server locally (Node 18+, zero dependencies): Or call the HTTP API directly: GET https://solvinghealth.com/api/v1 lists every endpoint, whether it is live, and which government dataset it reads. What is here The tools findproviders, getprovider, searchclearances, searchdevice_recalls, searchadverseevents, searchdruglabels, search_trials, searchhospitals, listendpoints, and two that forward to ClinicalSwipe's family caregiver navigator: caregiverquestionnaire, caregiverplan. Honest limits • This is a convenience layer. The official sources need no key either: NPPES NPI Registry API, openFDA, ClinicalTrials.gov API, CMS Provider Data. What this adds is one call shape, the source on every result, and MCP. • Upstream rate limits and outages pass through. • Endpoints that cannot be served honestly answer 501 with the reason. • Not medical, coding, billing or legal advice. Check it License Apache-2.0. See LICENSE.
Read the full README on GitHub →Remotes
- streamable-http
https://solvinghealth.com/api/data-mcp
Alternatives to SolvingHealth federal health data
All SolvingHealth federal health data alternatives →Best Health & Science servers →The most-starred Health & Science servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| Arxiv MCP Server | 3,284 | Nov 2026 | Local / not checked |
| com.medplum MCP | 2,802 | Nov 2026 | Needs sign-in |
| Tooluniverse | 1,791 | Nov 2026 | Local / not checked |
| Mirobody | 1,639 | Nov 2026 | Local / not checked |
| Tavotto | 728 | Nov 2026 | Local / not checked |
SolvingHealth federal health data: questions people ask
- Is SolvingHealth federal health data a remote or a local MCP server?
- According to its entry in the official MCP registry, SolvingHealth federal health data ships as a hosted endpoint (streamable-http) that your client connects to by URL.
- Does SolvingHealth federal health data need an API key?
- Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
- Is SolvingHealth federal health data safe to use?
- Looks healthy: SolvingHealth federal health data is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, Apache-2.0; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- Is SolvingHealth federal health data still maintained?
- Active: the repository's last commit 3 days ago. Last push Nov 19, 2026, 0 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 21, 2026.
- What tools does SolvingHealth federal health data expose?
- 12 tools as listed by the server itself during the live check, including find_providers, get_provider, search_clearances, search_device_recalls, search_adverse_events. The full list with parameters is in the Live check section above.
- How do I add SolvingHealth federal health data to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Health & Science servers
Browse all Health & Science →Arxiv MCP Server
blazickjp
Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
U2 MCP Server
bpamiri
Connect AI assistants to Rocket Universe/UniData MultiValue databases via MCP.
Flit Physics
brashler
Tiny sphere-physics engine for three.js games: spawn, step, raycast, InstancedMesh-ready positions
Totem
briangaoo
Totem — talk to your wearables with AI. Today: full Whoop access (48 tools).
Whoop MCP
briangaoo
Full read + write access to your Whoop fitness data via the private iOS API. 48 tools.
mathguard
C0MaE
Verify maths from language models: identities, derivations, calculus, solutions, units, answers.
Add the badge to your site
Show visitors that SolvingHealth federal health data is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-blainomd-solvinghealth-data-tools?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="SolvingHealth federal health data — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-blainomd-solvinghealth-data-tools?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-blainomd-solvinghealth-data-tools) [](https://serverdex.io/install/vscode/io-github-blainomd-solvinghealth-data-tools) [](https://serverdex.io/install/claude-code/io-github-blainomd-solvinghealth-data-tools)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/io-github-blainomd-solvinghealth-data-tools"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-blainomd-solvinghealth-data-tools"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-blainomd-solvinghealth-data-tools"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).