Remote MCP · Endpoint

com.dropwatchhq/recall-risk MCP server

No. com.dropwatchhq/recall-risk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cassandra.dropwatchhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.dropwatchhq/recall-risk
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
77 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Check a product's recall risk: score + active CPSC/FDA/NHTSA recalls for a product or brand.
Listing
From the official MCP registry (active).
Recent checks of com.dropwatchhq/recall-risk
CheckedResultHandshake
1 hour agoHandshake completed77 ms
18 hours agoHandshake completed81 ms
2 days agoHandshake completed68 ms
3 days agoHandshake completed52 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed59 ms
6 days agoHandshake completed76 ms
7 days agoHandshake completed292 ms
10 days agoHandshake completed66 ms
13 days agoHandshake completed597 ms
15 days agoHandshake completed88 ms
17 days agoHandshake completed220 ms
19 days agoHandshake completed56 ms
21 days agoHandshake completed50 ms
23 days agoHandshake completed57 ms
25 days agoHandshake completed47 ms
27 days agoHandshake completed66 ms
28 days agoHandshake completed69 ms
29 days agoHandshake completed296 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.

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