Remote MCP · Endpoint

Zovo Sanctions Screening MCP server

No. Zovo Sanctions Screening answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://ofac-screening.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/ofac-screening
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
164 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Run an ofac search on business names and get a dated XLSX screening log.
Listing
From the official MCP registry (active).
Recent checks of Zovo Sanctions Screening
CheckedResultHandshake
44 minutes agoHandshake completed164 ms
3 days agoHandshake completed206 ms
13 days agoHandshake completed260 ms
13 days agoHandshake completed296 ms
15 days agoHandshake completed361 ms
15 days agoHandshake completed183 ms
17 days agoHandshake completed178 ms
18 days agoHandshake completed203 ms
18 days agoHandshake completed160 ms
20 days agoHandshake completed252 ms
22 days agoHandshake completed278 ms
25 days agoHandshake completed155 ms
27 days agoHandshake completed216 ms

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

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 Zovo Sanctions Screening and makes no claim about it beyond what these checks measured.