Batch Sanctions Screening

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

Screen up to 100 names vs sanctions and US export lists. $0.50/batch via x402.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that screens up to 100 names per batch against sanctions and US export lists, paid per batch.

What you can do
  • Screen a batch of up to 100 names against sanctions and US export control lists
  • Return screening results for the submitted names in one batch call
  • Charge each batch at a fixed per-batch price through the x402 payment flow
When to use it
Useful when an assistant needs to run bulk name screening against sanctions and US export lists, for example during onboarding, vendor checks or compliance review, and a paid per-batch remote service is acceptable.
Requirements
A remote streamable HTTP endpoint; no local package, account, API key or environment variable is declared. Payment is required per batch through x402, so a compatible paying client or wallet is needed.
Before you install
Each batch costs $0.50 via x402, so screening spends real money and costs scale with the number of batches. The names submitted are sent to a third-party hosted service. No authentication is declared, so anyone with the endpoint can call it and incur charges.

Installation

In SourceWeft

  1. Open Batch Sanctions Screening 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-batch/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": {
    "batch-sanctions-screening": {
      "type": "http",
      "url": "https://sanctions-batch-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.