Snow Leo Risk & Compliance

io.github.MagzhanSanPublished by GitHub account MagzhanSanv1.0.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant screen names against OFAC, EU and UN sanctions lists and run CVE, DNS, WHOIS and public tender checks.

What you can do
Screen names against OFAC, EU and UN sanctions and watchlists for compliance checks. Look up CVEs to check known vulnerabilities. Inspect domain DNS records and WHOIS registration details. Search public tender listings.
When to use it
Useful for compliance, risk and due-diligence work where an assistant should check people or organizations against sanctions lists, or verify a domain and its vulnerabilities before a deal or onboarding.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com; OAuth authentication is required. No local package, environment variables or headers are declared.
Before you install
Requires an OAuth sign-in to the remote service, so queries and screened names are sent to that third party. Screening results are informational and should not be treated as a definitive compliance determination.

Installation

In SourceWeft

  1. Open Snow Leo Risk & Compliance in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.MagzhanSan%2Fsnowleo-risk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "snow-leo-risk-compliance": {
      "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"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

70% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts