com.dropwatchhq/coverage-trigger
REMOTE · COVERAGE.DROPWATCHHQ.COM
Leads of businesses that just legally need commercial insurance: new FMCSA authority + new entities.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 3 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 337 tokens (~112/item across 3 items; 3 tools + 0 resources), lean.Pass
- 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 3 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.
- 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
- 27 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
- 26 Jul 26 0
First indexed and scored.
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://coverage.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 | 7ee7aecd19a982d30e2e0e18e71a5d91 |
| SANs: dropwatchhq.com, coverage.dropwatchhq.com, *.coverage.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 coverage.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://coverage.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://coverage.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 →
coverage_pulse ~61
Free aggregate pulse: how many entities newly needed coverage in the window, broken down by source, lead-value tier, and coverage line — with a small redacted sample. No contact data.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
coverage_sources ~32
List the public trigger-event sources this feed normalizes, their geographic coverage, and the agent buyer each is best for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
coverage_trigger_feed ~244
Return businesses that JUST legally/practically NEED commercial insurance, drawn from public trigger events (new FMCSA DOT operating authority + newly formed commercial entities). Each lead is normalized to a NAICS family and a MANDATED-COVERAGE MAP (which policies it now needs: general liability, commercial auto, motor cargo, workers-comp, surety bond, etc.), deduped so one entity hitting multiple triggers = ONE lead, and tiered by lead value. Built for B2B insurance & surety AGENTS sourcing fresh, high-intent commercial leads.
| Name | Type | Req | Description |
|---|---|---|---|
| coverageLine | string | – | Filter to leads needing a line, e.g. 'commercial-auto', 'general-liability', 'surety-bond'. |
| days | number | – | Lookback window in days (default 7). |
| limit | number | – | Max leads (default 100). |
| minLeadValue | number | – | Only leads with estLeadValueUsd >= this. |
| sources | array | – | Subset of sources: 'fmcsa', 'ct-sos'. Omit for all. |
| state | string | – | Two-letter state filter, e.g. 'CT'. |
No output schema declared.
No examples provided.
How do I install the com.dropwatchhq/coverage-trigger MCP server?
com.dropwatchhq/coverage-trigger is a hosted endpoint at https://coverage.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 · coverage.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-coverage-trigger 'https://coverage.dropwatchhq.com/mcp'
What is the com.dropwatchhq/coverage-trigger MCP server?
com.dropwatchhq/coverage-trigger is an MCP server listed in the public MCP registry as com.dropwatchhq/coverage-trigger. Leads of businesses that just legally need commercial insurance: new FMCSA authority + new entities. This page covers its hosted endpoint (https://coverage.dropwatchhq.com/mcp).
Is the com.dropwatchhq/coverage-trigger MCP server safe to use?
com.dropwatchhq/coverage-trigger scores 69 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/coverage-trigger MCP server expose?
com.dropwatchhq/coverage-trigger exposes 3 tools: coverage_trigger_feed, coverage_pulse, coverage_sources. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Does the com.dropwatchhq/coverage-trigger MCP server require authentication?
No. We connected to com.dropwatchhq/coverage-trigger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.dropwatchhq/coverage-trigger MCP server still maintained?
com.dropwatchhq/coverage-trigger 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/coverage-trigger MCP server?
VerifyMCP ran 12 checks on com.dropwatchhq/coverage-trigger, 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/coverage-trigger: 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.