Remote MCP · Endpoint

Sanctionlistcheck.com MCP server

No. Sanctionlistcheck.com answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://sanctionlistcheck.com/mcp

The last check completed an MCP handshake.

Registry name
com.sanctionlistcheck/sanctionlistcheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.08 s
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Checks names against OFAC, UK, EU, UN and more sanctions lists; returns scored possible matches.
Listing
From the official MCP registry (active).
Recent checks of Sanctionlistcheck.com
CheckedResultHandshake
35 minutes agoHandshake completed1.08 s
9 days agoHandshake completed543 ms
10 days agoHandshake completed790 ms
11 days agoHandshake completed492 ms
12 days agoHandshake completed426 ms
14 days agoHandshake completed591 ms
14 days agoHandshake completed893 ms
15 days agoHandshake completed436 ms
17 days agoHandshake completed812 ms
19 days agoHandshake completed559 ms
21 days agoHandshake completed866 ms
24 days agoHandshake completed830 ms
26 days agoHandshake completed752 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 Sanctionlistcheck.com and makes no claim about it beyond what these checks measured.