Remote MCP · Endpoint

com.dropwatchhq/coverage-trigger MCP server

No. com.dropwatchhq/coverage-trigger answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://coverage.dropwatchhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.dropwatchhq/coverage-trigger
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
62 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Leads of businesses that just legally need commercial insurance: new FMCSA authority + new entities.
Website
https://coverage.dropwatchhq.com/
Listing
From the official MCP registry (active).
Recent checks of com.dropwatchhq/coverage-trigger
CheckedResultHandshake
1 hour agoHandshake completed62 ms
18 hours agoHandshake completed60 ms
2 days agoHandshake completed60 ms
3 days agoHandshake completed44 ms
4 days agoHandshake completed47 ms
5 days agoHandshake completed117 ms
6 days agoHandshake completed135 ms
7 days agoHandshake completed106 ms
10 days agoHandshake completed43 ms
13 days agoHandshake completed511 ms
15 days agoHandshake completed294 ms
17 days agoHandshake completed59 ms
19 days agoHandshake completed200 ms
21 days agoHandshake completed161 ms
23 days agoHandshake completed60 ms
25 days agoHandshake completed44 ms
27 days agoHandshake completed46 ms
28 days agoHandshake completed56 ms
29 days agoHandshake completed267 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.dropwatchhq/coverage-trigger and makes no claim about it beyond what these checks measured.