Remote MCP · Endpoint

io.github.cyanheads/sanctions-screening-mcp-server MCP server

No. io.github.cyanheads/sanctions-screening-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sanctions-screening.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/sanctions-screening-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
261 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Screen eleven sanctions/export-control lists; resolve GLEIF entities offline. Screening aid.
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/sanctions-screening-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed261 ms
1 day agoHandshake completed323 ms
2 days agoHandshake completed139 ms
3 days agoHandshake completed245 ms
4 days agoHandshake completed279 ms
5 days agoHandshake completed298 ms
6 days agoHandshake completed284 ms
9 days agoHandshake completed305 ms
11 days agoHandshake completed239 ms
14 days agoHandshake completed296 ms
16 days agoHandshake completed803 ms
18 days agoHandshake completed202 ms
20 days agoHandshake completed189 ms
22 days agoHandshake completed150 ms
24 days agoHandshake completed117 ms
26 days agoHandshake completed100 ms
27 days agoHandshake completed120 ms
29 days agoHandshake completed581 ms

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

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 io.github.cyanheads/sanctions-screening-mcp-server and makes no claim about it beyond what these checks measured.