mcp server
health-intel
Healthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement.
Description as published by the maintainer. Source
- version 1.0.0
- active
- security
active — Registry entry last updated 2026-06-21. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
fda_enforcement(firm)- Return recent FDA enforcement/recall actions tied to a device/drug firm (openFDA). A manufacturer-risk layer for procurement and payor teams. Required: firm.
new_exclusions(limit, state, specialty)- Return providers newly added to the OIG-LEIE exclusion list, optionally scoped by state and/or specialty. The credentialing / payment-integrity alert feed.
provider_lookup(npi, city, name, limit, state, specialty)- Look up US healthcare providers from the public CMS NPPES registry by NPI, or search by specialty + state (+ optional name/city). Returns NPI, name, specialty, license, location, and an OIG-LEIE exclusion flag on each. Public data only — no PHI.
screen_exclusion(npi, name, state)- Screen a provider/organization against the federal exclusion lists (HHS-OIG LEIE, and SAM.gov if configured). NPI match is exact; name match is flagged and identity-cautious. Returns sourced findings + a disclaimer. Facts, never an allegation.
Last successful function declaration observed on . Source: https://health.dropwatchhq.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://health.dropwatchhq.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-21 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-21 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | health.dropwatchhq.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | health.dropwatchhq.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json