Coverage Trigger MCP Server

by dropwatchhq Your server? Claim it

answering

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

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

Uptime history 91 days of history · worst day 92%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

110 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Coverage Trigger every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add coverage-trigger --transport http https://coverage.dropwatchhq.com/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "coverage-trigger": {
      "type": "http",
      "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

URL	Transport	State	Latency	Checked
https://coverage.dropwatchhq.com/mcp	streamable-http	answering	49 ms	4 min ago

Alternatives to Coverage Trigger

same job, measured the same way

Coverageshield

by djanacek

Insurance coverage requirements, gap detection, and risk profiles for US businesses.

39 installs/wk local only

Delegance Commercial Insurance

by delegancebrokerage

Your company's commercial insurance: policies, coverage, certificates, quotes and claims.

answering

AI Agent Liability Insurance

by johalinsurancebrokers

Quote AI agent liability insurance (Tech E&O + AI coverage) from a licensed US insurance broker.

2 tools answering

Jarroba Tools · Test audit

by invarato

Audits tests instead of writing them: what each one really asserts. 4 tools, local.

611 installs/wk local only

Axiom Lab — AI Pitch Deck & Business Video MCP

by axiom-lab-tech

Turn PDFs, PPTX decks, product photos, and briefs into QA-checked commercial videos via MCP.

answering

Insuro

by com-insuro

Free insurance vault MCP: OAuth policies, renewals, coverage Q&A, file PDFs. Global; not advice.

2 tools answering

thePaymentsNotes Ledger

by alwaysarafath

Verified agentic-commerce protocol status + merchant agent-readiness reports. Free on testnet.

6 tools answering

AgentWatchr

by agentwatchr

Read-only agent identity index with provenance, historical evidence and explained coverage.

4 tools answering

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 110 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 in the form 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 110 ms on average, which is faster than 90% 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.