Health Intel is an MCP server with 4 tools an agent can call, among them fda_enforcement, new_exclusions, provider_lookup. It answers at https://health.dropwatchhq.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
Healthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
fda_enforcement | Return recent FDA enforcement/recall actions tied to a device/drug firm (openFDA). A manufacturer-risk layer for procurement and payor teams. Inputs: firm |
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. Inputs: state, specialty, limit |
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 Inputs: npi, name, specialty, state, city, limit |
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 allegati Inputs: npi, name, state |
Every block below points at https://health.dropwatchhq.com/mcp. Pick your client and copy.
claude mcp add --transport http health-intel https://health.dropwatchhq.com/mcp
{
"mcpServers": {
"health-intel": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://health.dropwatchhq.com/mcp"]
}
}
}{
"mcpServers": {
"health-intel": {
"url": "https://health.dropwatchhq.com/mcp"
}
}
}{
"servers": {
"health-intel": {
"type": "http",
"url": "https://health.dropwatchhq.com/mcp"
}
}
}{
"context_servers": {
"health-intel": {
"url": "https://health.dropwatchhq.com/mcp"
}
}
}{
"mcpServers": {
"health-intel": {
"serverUrl": "https://health.dropwatchhq.com/mcp"
}
}
}{
"mcpServers": {
"health-intel": {
"url": "https://health.dropwatchhq.com/mcp"
}
}
}name: health-intel
version: 0.0.1
schema: v1
mcpServers:
- name: health-intel
type: streamable-http
url: https://health.dropwatchhq.com/mcp{
"mcpServers": {
"health-intel": {
"httpUrl": "https://health.dropwatchhq.com/mcp"
}
}
}{
"mcpServers": {
"health-intel": {
"type": "http",
"url": "https://health.dropwatchhq.com/mcp"
}
}
}{
"mcpServers": {
"health-intel": {
"url": "https://health.dropwatchhq.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fhealth.dropwatchhq.com%2Fmcp&type=streamable_http&id=health-intel&name=health-intel
It answered our last check on 18 October 2026 in 138 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by dropwatchhq.com and served from health.dropwatchhq.com, the vendor's own domain: https://health.dropwatchhq.com/mcp.
4, as returned by the server's own tools/list on 10 September 2026: fda_enforcement, new_exclusions, provider_lookup, screen_exclusion.
It answered our last check on 18 October 2026 in 138 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://health.dropwatchhq.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.dropwatchhq. Endpoint host: health.dropwatchhq.com. ARD identifier: urn:air:com.dropwatchhq:mcp:health-intel.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.