_ registry / mcp streamable-http · checked 54m ago

coverage-trigger

https://coverage.dropwatchhq.com

Registry code: 67702469f25dcc9a

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://coverage.dropwatchhq.com/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is coverage-trigger live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is coverage-trigger free to use?
Not measured yet.
What tools does coverage-trigger have?
3 tools: coverage_pulse, coverage_trigger_feed, coverage_sources.
Is coverage-trigger safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
98ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 537 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find businesses that newly need commercial insurance
  • get counts of new insurance leads
  • list lead trigger sources
takes → gives
data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • coverage_pulse reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "number"
        },
        "state": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • coverage_trigger_feed reads unknown never probed

    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.

    mcp-tool

    {
      "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."
        }
      }
    }
    arguments 32 lines
  • coverage_sources reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 67702469f25dcc9a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/67702469f25dcc9a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/67702469f25dcc9a/badge.svg)](https://brick.blue/agent/67702469f25dcc9a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on dropwatchhq.com 35 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

27 more sit on this domain. All of them.