mcpbeat

Coverage Trigger MCP Server

com.dropwatchhq/coverage-trigger
answering

Coverage Trigger is answering right now. Last checked 9 min ago. It exposes 3 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
68 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add coverage-trigger --transport http https://coverage.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "coverage-trigger": {
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.coverage-trigger]
url = "https://coverage.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "coverage-trigger": {
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "coverage-trigger": {
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

coverage
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.
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: 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.

Endpoints

URLTransportStateLatencyChecked
https://coverage.dropwatchhq.com/mcp streamable-http answering 55 ms 9 min ago

Coverage Trigger — questions

Answers built from our own checks of this server.

What can Coverage Trigger do?
It exposes 3 tools, read directly from the server on our last check. Among them: coverage_pulse, coverage_sources, coverage_trigger_feed. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Coverage Trigger working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 68 ms. The bar chart above shows every period we have measured.
How do I connect Coverage Trigger?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Coverage Trigger need an API key?
No. Coverage Trigger completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Coverage Trigger?
It answers our handshake in 68 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.