Sanctions Screen (OFAC, EU, UK, UN)

io.github.pcp183Published by GitHub account pcp183v0.2.0Updated Oct 26, 2026

Screen a party vs OFAC, EU and UK sanctions lists before paying. $0.02/call via x402.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant screen a party against OFAC, EU and UK sanctions lists before making a payment.

What you can do
  • Screen a named party against OFAC, EU and UK sanctions lists
  • Run the check as a pre-payment step before sending funds
  • No tool list is published, so the exact operations and inputs are not documented in the supplied material
When to use it
Useful when an assistant handles payments or onboarding and needs a quick sanctions check on a counterparty before money moves. It is a narrow, single-purpose screening service rather than a general compliance suite.
Requirements
A remote streamable HTTP endpoint; no local install, account, API key or environment variables are declared. Each call is billed at $0.02 through x402, so a payment-capable x402 client is needed.
Before you install
Every call costs $0.02 via x402, so automated or repeated screening spends money. The party names you submit are sent to a third-party hosted service. The tool list is not published, so verify inputs and outputs before relying on results for compliance decisions.

Installation

In SourceWeft

  1. Open Sanctions Screen (OFAC, EU, UK, UN) in the dashboard and add it to a workspace.
  2. 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.pcp183%2Fsanctions-screen/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.

{
  "mcpServers": {
    "sanctions-screen-ofac-eu-uk-un": {
      "type": "http",
      "url": "https://sanctions-screen-production.up.railway.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.2.0LatestOct 17, 2026
  2. v0.1.0Oct 16, 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 listedRequired15 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.