Skip to content
Back to search

solvinghealth-data-tools

Read-only US federal health data (NPI, FDA, trials, CMS hospitals) with the source on every result: HTTP gateway, MCP server and SDKs behind solvinghealth.com

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/blainomd--solvinghealth-data-tools/badge.svg)](/listings/blainomd--solvinghealth-data-tools)

HTML

<a href="/listings/blainomd--solvinghealth-data-tools"><img src="/api/listings/blainomd--solvinghealth-data-tools/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 71 lines
  1. # SolvingHealth data tools
  2. The code behind the public, read-only federal health data lookups at
  3. [solvinghealth.com](https://solvinghealth.com): NPI records, FDA 510(k)
  4. clearances, device recalls and adverse events, drug labels, clinical trials
  5. and CMS hospitals. Every result carries the upstream source URL and the time
  6. it was retrieved, so you can check any fact against the source.
  7. No key. No account. Nothing stored. Send no patient information.
  8. ## Use it
  9. Over MCP (HTTP, nothing to install):
  10. ```bash
  11. claude mcp add --transport http solvinghealth https://solvinghealth.com/api/data-mcp
  12. ```
  13. Or run the MCP server locally (Node 18+, zero dependencies):
  14. ```bash
  15. node public/sdk/mcp-server.mjs
  16. ```
  17. Or call the HTTP API directly:
  18. ```bash
  19. curl "https://solvinghealth.com/api/v1/providers/search?taxonomy=Orthopaedic%20Surgery&postal_code=80303&limit=5"
  20. ```
  21. `GET https://solvinghealth.com/api/v1` lists every endpoint, whether it is
  22. live, and which government dataset it reads.
  23. ## What is here
  24. | Path | What it is |
  25. |---|---|
  26. | `api/v1/[...path].js` | The HTTP gateway. Calls NPPES, openFDA, ClinicalTrials.gov and data.cms.gov, selects fields, and returns them with `source_url` and `retrieved_at`. |
  27. | `api/data-mcp.js` | The same tools over MCP Streamable HTTP. Stateless. |
  28. | `public/sdk/mcp-server.mjs` | The MCP server (stdio), eleven tools. |
  29. | `public/sdk/solvinghealth.mjs`, `solvinghealth.py` | Small clients for JavaScript and Python. |
  30. | `packages/suspension-kit/deadlines.mjs` | Date arithmetic for the `/suspension/deadlines` endpoint, from 42 CFR Part 405 Subpart C. |
  31. ## The tools
  32. `find_providers`, `get_provider`, `search_clearances`, `search_device_recalls`,
  33. `search_adverse_events`, `search_drug_labels`, `search_trials`,
  34. `search_hospitals`, `list_endpoints`, and two that forward to ClinicalSwipe's
  35. family caregiver navigator: `caregiver_questionnaire`, `caregiver_plan`.
  36. ## Honest limits
  37. - This is a convenience layer. The official sources need no key either:
  38. [NPPES NPI Registry API](https://npiregistry.cms.hhs.gov/api-page),
  39. [openFDA](https://open.fda.gov/apis/),
  40. [ClinicalTrials.gov API](https://clinicaltrials.gov/data-api/api),
  41. [CMS Provider Data](https://data.cms.gov/provider-data/).
  42. What this adds is one call shape, the source on every result, and MCP.
  43. - Upstream rate limits and outages pass through.
  44. - Endpoints that cannot be served honestly answer 501 with the reason.
  45. - Not medical, coding, billing or legal advice.
  46. ## Check it
  47. ```bash
  48. node test/smoke.mjs
  49. ```
  50. ## License
  51. Apache-2.0. See `LICENSE`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.