com.dropwatchhq/exclude-feed
REMOTE · EXCLUDE.DROPWATCHHQ.COM
Screen a business for federal exclusions & sanctions: OFAC SDN, HHS-OIG LEIE, SAM.gov debarment.
Available components
Last scanned (10 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 658 tokens (~164/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://exclude.dropwatchhq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dropwatchhq.com | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | cbacb5c774fc5bfd13afe0336f3fa0cf |
| SANs: dropwatchhq.com, exclude.dropwatchhq.com, *.exclude.dropwatchhq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of exclude.dropwatchhq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| dropwatchhq.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://exclude.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://exclude.dropwatchhq.com/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
roster_rescreen ~247
Re-screen an ENTIRE ROSTER of employees, contractors, and vendors against the federal exclusion & sanctions lists (HHS-OIG LEIE, OFAC SDN+Consolidated, SAM.gov debarment) in ONE call, and mint a DATED, ed25519-SIGNED COMPLIANCE RECEIPT. This is the OIG-mandated MONTHLY exclusion check for healthcare billing / RCM / compliance teams: OIG guidance says screen every employee, contractor, and vendor against the LEIE each month, because a single excluded person on a claim triggers Civil Monetary Penalties. The signed receipt is your audit artifact — verifiable offline, proving WHO you screened, against WHICH list build, on WHAT date. Returns per-entity verdicts (cleared vs. flagged) plus a verifiable receipt URL.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | – | Your organization name (printed on the compliance receipt). |
| period | string | – | Compliance period as YYYY-MM (defaults to the current month). |
| roster | array | yes | The people/entities to screen. Each is a name string or {name, npi?, uei?, state?} object (max 250). |
No output schema declared.
No examples provided.
screen_batch ~79
Bulk-screen up to 50 entities in one call against all federal exclusion/sanctions lists. Pass an array of names (or {name,npi,state} objects). Returns one verdict per row. Free tool (rate-limited).
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | Array of names or {name,npi,uei,state} objects (max 50). |
No output schema declared.
No examples provided.
screen_exclusion ~235
Screen a business entity / vendor / counterparty for FEDERAL EXCLUSIONS & SANCTIONS before you onboard or pay it. One unified, DEDUPED check across OFAC SDN, OFAC Consolidated (sanctions), HHS-OIG LEIE (healthcare exclusions), SAM.gov (federal contractor debarment/suspension), and publicly-available state debarment lists. Returns match / possible-match / no-match, the matched record(s) with source + exclusion type + dates, and a confidence score. FCRA-SAFE: this is KYB/sanctions compliance for entities — NOT a consumer report, not for credit/employment/insurance/tenancy decisions about individuals.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country to disambiguate. |
| name | string | yes | Legal / business name of the entity to screen. |
| npi | string | – | Optional 10-digit NPI (healthcare) for an exact LEIE match. |
| state | string | – | Optional 2-letter state to disambiguate name matches. |
| uei | string | – | Optional SAM UEI. |
No output schema declared.
No examples provided.
watch_entity ~97
Add an entity to a watchlist that is RE-SCREENED daily. You get alerted (webhook/email) the first time it appears on any federal exclusion or sanctions list. Use for continuous vendor / counterparty monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional email alerted on a new hit. | |
| name | string | yes | – |
| npi | string | – | – |
| webhook | string | – | Optional URL POSTed on a new hit. |
No output schema declared.
No examples provided.
How do I install the com.dropwatchhq/exclude-feed MCP server?
com.dropwatchhq/exclude-feed is a hosted endpoint at https://exclude.dropwatchhq.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · exclude.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-exclude-feed 'https://exclude.dropwatchhq.com/mcp'
What is the com.dropwatchhq/exclude-feed MCP server?
com.dropwatchhq/exclude-feed is an MCP server listed in the public MCP registry as com.dropwatchhq/exclude-feed. Screen a business for federal exclusions & sanctions: OFAC SDN, HHS-OIG LEIE, SAM.gov debarment. This page covers its hosted endpoint (https://exclude.dropwatchhq.com/mcp).
Is the com.dropwatchhq/exclude-feed MCP server safe to use?
com.dropwatchhq/exclude-feed scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.dropwatchhq/exclude-feed MCP server expose?
com.dropwatchhq/exclude-feed exposes 4 tools: screen_exclusion, screen_batch, roster_rescreen, watch_entity. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.
Does the com.dropwatchhq/exclude-feed MCP server require authentication?
No. We connected to com.dropwatchhq/exclude-feed without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.dropwatchhq/exclude-feed MCP server still maintained?
com.dropwatchhq/exclude-feed is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.dropwatchhq/exclude-feed MCP server?
VerifyMCP ran 12 checks on com.dropwatchhq/exclude-feed, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.dropwatchhq/exclude-feed: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.