Koskamo

Coverage Trigger MCP

An MCP server providing an agent-payable feed of businesses that legally need commercial insurance, such as new FMCSA authority or new entities. It normalizes data to mandated coverage lines like GL and commercial-auto, deduplicates leads, and supports payment via x402 standard using USDC on Base.

Visit DropWatch

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Coverage Trigger MCP logo, by DropWatchVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by DropWatch
MCP endpoint (Streamable HTTP)
https://coverage.dropwatchhq.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (3)

3 of 3 have a description · 0 of 3 declare behavior hints · 1 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to dropwatchhq.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve deduped leads of new businesses needing commercial insurance
  • Aggregate demand by source, tier, and coverage line
  • List public trigger-event sources for insurance leads

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.dropwatchhq/coverage-trigger@1.0.0Project website

Protocol and capabilities

Server
coverage-trigger 1.0.0
MCP protocol negotiated in check
2024-11-05
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

3 advertised

coverage_trigger_feed
Advertised by the server during the last successful anonymous check.

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.

coverage_trigger_feed input schema
{
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "description": "Lookback window in days (default 7)."
    },
    "limit": {
      "type": "number",
      "description": "Max leads (default 100)."
    },
    "state": {
      "type": "string",
      "description": "Two-letter state filter, e.g. 'CT'."
    },
    "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'."
    },
    "minLeadValue": {
      "type": "number",
      "description": "Only leads with estLeadValueUsd >= this."
    }
  }
}
coverage_pulse
Advertised by the server during the last successful anonymous check.

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_pulse input schema
{
  "type": "object",
  "properties": {
    "days": {
      "type": "number"
    },
    "state": {
      "type": "string"
    }
  }
}
coverage_sources
Advertised by the server during the last successful anonymous check.

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

coverage_sources input schema
{
  "type": "object",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
145 ms
95th percentile latency
145 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 145 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http coverage-trigger-mcp https://coverage.dropwatchhq.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add coverage-trigger-mcp --url https://coverage.dropwatchhq.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable coverage-trigger-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "coverage-trigger-mcp": {
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "coverage-trigger-mcp": {
      "type": "streamableHttp",
      "url": "https://coverage.dropwatchhq.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start coverage-trigger-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "coverage-trigger-mcp": {
      "type": "http",
      "url": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http coverage-trigger-mcp https://coverage.dropwatchhq.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://coverage.dropwatchhq.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "coverage-trigger-mcp": {
      "serverUrl": "https://coverage.dropwatchhq.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Coverage Trigger MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,916

Do you run Coverage Trigger MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing