coverage-trigger
Leads of businesses that just legally need commercial insurance: new FMCSA authority + new entities.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"coverage-trigger": {
"url": "https://coverage.dropwatchhq.com/mcp"
}
}
}Remote endpoints
https://coverage.dropwatchhq.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
⚪coverage_trigger_feed(days, sources, coverageLine, state, minLeadValue, ...)
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.
Input Schema
{
"type": "object",
"properties": {
"days": {
"type": "number",
"description": "Lookback window in days (default 7)."
},
"sources": {
"type": "array",
"items": {
"type": "string"
},
"description": "Subset of sources: 'fmcsa', 'ct-sos'. Omit for all."
},
"coverageLine": {
"type": "string",
"description": "Filter to leads needing a line, e.g. 'commercial-auto', 'general-liability', 'surety-bond'."
},
"state": {
"type": "string",
"description": "Two-letter state filter, e.g. 'CT'."
},
"minLeadValue": {
"type": "number",
"description": "Only leads with estLeadValueUsd >= this."
},
"limit": {
"type": "number",
"description": "Max leads (default 100)."
}
}
}⚪coverage_pulse(days, state)
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.
Input Schema
{
"type": "object",
"properties": {
"days": {
"type": "number"
},
"state": {
"type": "string"
}
}
}🟢coverage_sources
List the public trigger-event sources this feed normalizes, their geographic coverage, and the agent buyer each is best for.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence