Skip to content

coverage-trigger MCP server

com.dropwatchhq/coverage-triggerdropwatchhq.comstreamable-httpv1.0.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the coverage-trigger MCP server can do

The coverage-trigger MCP server is published by dropwatchhq.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: coverage_trigger_feed and coverage_pulse), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • coverage_pulseFree 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 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_trigger_feedReturn businesses that JUST legally/practically NEED commercial insurance, drawn from public trigger events (new FMCSA DOT operating authority + newly formed commercial entities).No findings

    Why it is in this group

    • The name "coverage_trigger_feed" says "trigger": a word for a change.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • coverage_sourcesList the public trigger-event sources this feed normalizes, their geographic coverage, and the agent buyer each is best for.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the public trigger-event sources this feed normalizes, their geographic coverage, and the agent buyer each is best for.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://coverage.dropwatchhq.com/mcp: tools/list returned 3 tools to an anonymous client, including coverage_trigger_feed (write), coverage_pulse (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__coverage-trigger__coverage_sources"
    ],
    "ask": [
      "mcp__coverage-trigger__coverage_trigger_feed",
      "mcp__coverage-trigger__coverage_pulse"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as coverage-trigger. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.dropwatchhq/coverage-trigger/verify?hash=67ea17e28f57f1bc7f5ac34e1e1f2b8fad6418431f523c11d927a37389ee9184" | jq -e '.changed == false'

Pinned hash 67ea17e28f57, from Nov 17, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.dropwatchhq/coverage-trigger/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.dropwatchhq/coverage-trigger
[![Anlyon Radar](https://radar.anlyon.com/badge/com.dropwatchhq/coverage-trigger.svg)](https://radar.anlyon.com/servers/com.dropwatchhq/coverage-trigger)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

coverage-trigger MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the coverage-trigger MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the coverage-trigger MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the coverage-trigger MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the coverage-trigger MCP server have?

3 tools: 2 write, 1 read. coverage_trigger_feed, coverage_pulse and coverage_sources.

Does the coverage-trigger MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the coverage-trigger MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the coverage-trigger MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.