Remote MCP · Endpoint

com.dropwatchhq/exclude-feed MCP server

No. com.dropwatchhq/exclude-feed answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://exclude.dropwatchhq.com/mcp

The last check completed an MCP handshake.

Registry name
com.dropwatchhq/exclude-feed
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
178 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Screen a business for federal exclusions & sanctions: OFAC SDN, HHS-OIG LEIE, SAM.gov debarment.
Listing
From the official MCP registry (active).
Recent checks of com.dropwatchhq/exclude-feed
CheckedResultHandshake
1 hour agoHandshake completed178 ms
18 hours agoHandshake completed202 ms
2 days agoHandshake completed145 ms
3 days agoHandshake completed115 ms
4 days agoHandshake completed155 ms
5 days agoHandshake completed268 ms
6 days agoHandshake completed221 ms
7 days agoHandshake completed202 ms
10 days agoHandshake completed178 ms
13 days agoHandshake completed522 ms
15 days agoHandshake completed108 ms
17 days agoHandshake completed117 ms
19 days agoHandshake completed136 ms
21 days agoHandshake completed224 ms
23 days agoHandshake completed223 ms
25 days agoHandshake completed375 ms
27 days agoHandshake completed169 ms
28 days agoHandshake completed176 ms
29 days agoHandshake completed308 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/exclude-feed and makes no claim about it beyond what these checks measured.