Sanctions Screening (OFAC, EU, UK, UN)

io.github.fairqueryPublished by GitHub account fairqueryv1.0.1Updated Oct 25, 2026

Fuzzy-screen people and company names against OFAC SDN, EU, UK and UN sanctions lists.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant fuzzy-screen people and company names against OFAC, EU, UK and UN sanctions lists.

What you can do
Screen personal and company names against the OFAC SDN, EU, UK and UN sanctions lists using fuzzy matching, so near-spellings and variants can be checked rather than only exact matches.
When to use it
Useful for compliance, onboarding or due-diligence checks where an assistant should quickly test a name against major sanctions lists before a manual review.
Requirements
Remote endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Authorization bearer header carrying an Apify API token, or Apify OAuth for clients that support it. Runs are billed to your own Apify account on a pay-per-event basis.
Before you install
The Authorization header carries a secret API token, and usage is charged to your Apify account per event, so costs accrue with use. Names submitted for screening are sent to a third-party service. Fuzzy matches are screening hints, not compliance determinations, and should be verified against official lists.

Installation

In SourceWeft

  1. Open Sanctions Screening (OFAC, EU, UK, UN) 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.fairquery%2Fsanctions-watchlist-screener/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": {
    "sanctions-screening-ofac-eu-uk-un": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=fetch-actor-details,fairquery/sanctions-watchlist-screener"
    }
  }
}

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

2
  1. v1.0.1LatestOct 18, 2026
  2. v1.0.0Oct 17, 2026

Score

60% 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

    Declare a license in the repository or the registry entry.