mcpbeat

Health Intel MCP Server

com.dropwatchhq/health-intel
answering

Health Intel is answering right now. Last checked 7 min ago. It exposes 4 tools.

Healthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
68 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add health-intel --transport http https://health.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "health-intel": {
      "url": "https://health.dropwatchhq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.health-intel]
url = "https://health.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "health-intel": {
      "url": "https://health.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "health-intel": {
      "url": "https://health.dropwatchhq.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fda
fda_enforcement
Return recent FDA enforcement/recall actions tied to a device/drug firm (openFDA). A manufacturer-risk layer for procurement and payor teams.
new
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.
provider
provider_lookup
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
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.

Endpoints

URLTransportStateLatencyChecked
https://health.dropwatchhq.com/mcp streamable-http answering 70 ms 7 min ago

Health Intel — questions

Answers built from our own checks of this server.

What can Health Intel do?
It exposes 4 tools, read directly from the server on our last check. Among them: fda_enforcement, new_exclusions, provider_lookup, screen_exclusion. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Health Intel working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 68 ms. The bar chart above shows every period we have measured.
How do I connect Health Intel?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Health Intel need an API key?
No. Health Intel completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Health Intel?
It answers our handshake in 68 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.