Lets an assistant look up US healthcare providers in the public NPPES registry and screen them against federal exclusion lists and FDA enforcement actions.
What you can do
It exposes four tools over a remote endpoint. provider_lookup finds providers by NPI or by specialty plus state, returning name, specialty, license, location and an OIG-LEIE exclusion flag. screen_exclusion checks a provider or organization against the HHS-OIG LEIE list, and SAM.gov if configured, with exact NPI matching and flagged name matches. new_exclusions lists providers newly added to the exclusion list, and fda_enforcement returns recent FDA recall or enforcement actions for a device or drug firm.
When to use it
Useful for credentialing, payment-integrity and procurement checks where an assistant should pull public provider records or verify exclusion status. Also suited to monitoring newly excluded providers by state or specialty and to adding manufacturer-risk context from FDA enforcement data.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account or API key is declared. Network access to the endpoint is needed, and SAM.gov screening only works if that source is configured on the server side.
Before you install
Results are public-data facts with a disclaimer, not allegations; name matches are flagged and identity-cautious, so verify before acting. Exclusion and enforcement findings can affect real credentialing or payment decisions, so confirm against the official sources.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.dropwatchhq%2Fhealth-intel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersnpicitynamelimitstatespecialty
screen_exclusion
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.
Parametersnpinamestate
new_exclusions
Return providers newly added to the OIG-LEIE exclusion list, optionally scoped by state and/or specialty. The credentialing / payment-integrity alert feed.
Parameterslimitstatespecialty
fda_enforcement
Return recent FDA enforcement/recall actions tied to a device/drug firm (openFDA). A manufacturer-risk layer for procurement and payor teams.
Parametersfirmrequired
Version history
1
v1.0.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.