All servers · Company & business data · Maps, location & weather
com.dropwatchhq/coverage-trigger
com.dropwatchhq/coverage-trigger · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2024-11-05 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Leads of businesses that just legally need commercial insurance: new FMCSA authority + new entities.
Connect
streamable-http · https://coverage.dropwatchhq.com/mcp
claude mcp add --transport http coverage-trigger https://coverage.dropwatchhq.com/mcp{
"mcpServers": {
"coverage-trigger": {
"url": "https://coverage.dropwatchhq.com/mcp"
}
}
}Tools as reported by the server
coverage_trigger_feedReturn 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, ccoverage_pulseFree 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.coverage_sourcesList the public trigger-event sources this feed normalizes, their geographic coverage, and the agent buyer each is best for.
Website · JSON · Text for agents · Registry updated 2026-06-22