NestDaddy

Coverage Trigger

com.dropwatchhq/coverage-trigger · v1.0.0

Leads of businesses that just legally need commercial insurance: new FMCSA authority + new entities.

Connect Remote server

Terminal
claude mcp add --transport http coverage-trigger https://coverage.dropwatchhq.com/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "coverage-trigger": {
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "coverage-trigger": {
      "type": "http",
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://coverage.dropwatchhq.com/mcp

Tools 3 found in our last check

  • coverage_trigger_feed

    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:…

  • coverage_pulse

    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.

  • coverage_sources

    List the public trigger-event sources this feed normalizes, their geographic coverage, and the agent buyer each is best for.

Details

Endpointhttps://coverage.dropwatchhq.com/mcp (Streamable HTTP)
First published22 Jun 2026
Last updated22 Jun 2026
Registry namecom.dropwatchhq/coverage-trigger

More marketing and seo servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.