Snow Leo Risk & Compliance MCP Server

by magzhansan Your server? Claim it

answering

Snow Leo Risk & Compliance is answering right now. Last checked 1 min ago. Last commit 22 Sep 2026.

Screen names against OFAC, EU and UN lists; check CVEs, domain DNS and WHOIS, and public tenders

Uptime history 50 days of history · worst day 97%

50 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

349 ms

Response time

average over 24h

Stars

last commit 22 Sep 2026

Snow Leo Risk & Compliance missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add snowleo-risk --transport http 'https://mcp.apify.com/?actors=snow_leo_data/sanctions-screening-api,snow_leo_data/cve-scraper,snow_leo_data/whois-dns-lookup,snow_leo_data/government-tenders-scraper'

Settings → Connectors → Add custom connector, then paste this address

https://mcp.apify.com/?actors=snow_leo_data/sanctions-screening-api,snow_leo_data/cve-scraper,snow_leo_data/whois-dns-lookup,snow_leo_data/government-tenders-scraper

~/.codex/config.toml

[mcp_servers.snowleo-risk]
url = "https://mcp.apify.com/?actors=snow_leo_data/sanctions-screening-api,snow_leo_data/cve-scraper,snow_leo_data/whois-dns-lookup,snow_leo_data/government-tenders-scraper"

.cursor/mcp.json

{
  "mcpServers": {
    "snowleo-risk": {
      "url": "https://mcp.apify.com/?actors=snow_leo_data/sanctions-screening-api,snow_leo_data/cve-scraper,snow_leo_data/whois-dns-lookup,snow_leo_data/government-tenders-scraper"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "snowleo-risk": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=snow_leo_data/sanctions-screening-api,snow_leo_data/cve-scraper,snow_leo_data/whois-dns-lookup,snow_leo_data/government-tenders-scraper"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com/?actors=snow_leo_data/sanctions-screening-api,snow_leo_data/cve-scraper,snow_leo_data/whois-dns-lookup,snow_leo_data/government-tenders-scraper	streamable-http	needs key	322 ms	1 min ago

Alternatives to Snow Leo Risk & Compliance

same job, measured the same way

OFAC (Sanções EUA)

by mcp-dir

Checks whether a name is on OFAC (US) sanctions lists, including SDN and Non-SDN, for compliance and

7 tools answering

OFAC SDN Screening

by bonissystems

Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.

2 tools answering

FinCEN (EUA)

by mcp-dir

Checks whether a name is on the FinCEN (US financial crimes) lists, for compliance and AML due dilig

7 tools answering

Sanções União Europeia

by mcp-dir

Checks whether a name is on the European Union's financial sanctions list, for compliance and AML du

7 tools answering

Agent Data Tools: Company, compliance and checks

by nutshell2000

50 tools: OFAC sanctions, counterparty checks, company, domain, email. 25 free calls.

59 tools answering

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

by nibiashara

Africa FX, US carrier/broker checks, OFAC name and wallet screens, load-vet pack. Paid via x402.

24 tools answering

Sanções Reino Unido (HM Treasury)

by mcp-dir

Checks whether a name is on the UK's financial sanctions list (HM Treasury), for compliance and AML

7 tools answering

Prove It

by ark-forge

Free public benchmark for AI agents: compliance tasks, every claim checked against signed receipts

121 installs/wk local only

Snow Leo Risk & Compliance — questions

Answers built from our own checks of this server.

Why is there no tool list for Snow Leo Risk & Compliance?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Snow Leo Risk & Compliance working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 349 ms. The bar chart above shows every period we have measured.

How do I connect Snow Leo Risk & Compliance?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does Snow Leo Risk & Compliance need an API key?

Yes. Every time we knock, Snow Leo Risk & Compliance answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Snow Leo Risk & Compliance?

It answers our handshake in 349 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Snow Leo Risk & Compliance open source?

The code is open source: it is published under the MIT licence, written in Shell and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.apify.com, which runs on its operator's own terms.