mcp-registry/com.dropwatchhq/health-intel · v1.0.0
As of 2026-10-22 16:57 UTC, the Dropwatchhq Health Intel MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Healthcare provider & compliance intel: NPPES lookup, OIG/SAM exclusion screening, FDA enforcement.
Claude Code
claude mcp add --transport http dropwatchhq-health-intel-mcp-server https://health.dropwatchhq.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"dropwatchhq-health-intel-mcp-server": {
"type": "http",
"url": "https://health.dropwatchhq.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
6 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.dropwatchhq%2Fhealth-intel/fixes
{
"name": "provider_lookup",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"npi": {
"type": "string",
"description": "Exact 10-digit NPI for a single provider."
},
"city": {
"type": "string"
},
"name": {
"type": "string",
"description": "Provider or organization name substring."
},
"limit": {
"type": "number",
"description": "Max results (default 50)."
},
"state": {
"type": "string",
"description": "Two-letter state, e.g. 'TX'."
},
"specialty": {
"type": "string",
"description": "Taxonomy/specialty, e.g. 'Cardiology'."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.dropwatchhq/health-intel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.dropwatchhq/health-intel"}) over MCP.
provider_lookup ~208 tokensscreen_exclusion ~114 tokensnew_exclusions ~99 tokensfda_enforcement ~92 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.dropwatchhq%2Fhealth-intel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.dropwatchhq%2Fhealth-intel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.dropwatchhq%2Fhealth-intel.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.dropwatchhq%2Fhealth-intel.svg :target: https://glimind.com/server/mcp-registry%2Fcom.dropwatchhq%2Fhealth-intel?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e99bc65db2c8f3cf…, first seen 2026-10-17, included at leaf 8009 of 47,105. Version history · verify what your client received.
Compare: most reliable search servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 16:57 UTC, the Dropwatchhq Health Intel MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Dropwatchhq Health Intel MCP server advertises 4 tools, including fda_enforcement, new_exclusions, provider_lookup, screen_exclusion.
Point your MCP client at this streamable-http endpoint: https://health.dropwatchhq.com/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.