Batch Sanctions Screening MCP Server

by pcp183 Your server? Claim it

not responding

Batch Sanctions Screening is listed as active in the registry but did not answer our last check. It exposes 1 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 23 days of history · worst day 0%

23 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

192 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct a tool description was rewritten batch_sanctions_screen

Batch Sanctions Screening does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add sanctions-batch --transport http https://sanctions-batch-production.up.railway.app/mcp

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

https://sanctions-batch-production.up.railway.app/mcp

~/.codex/config.toml

[mcp_servers.sanctions-batch]
url = "https://sanctions-batch-production.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "sanctions-batch": {
      "url": "https://sanctions-batch-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "sanctions-batch": {
      "type": "http",
      "url": "https://sanctions-batch-production.up.railway.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

batch

batch_sanctions_screen

Re-screen a whole customer, supplier or payee list against sanctions and US export-control lists in one call. Up to 100 names vs OFAC, EU and UK lists (UN via EU/UK) and optionally the US Consolidated Screening List. Per name: no_match, possible_match, confirmed_match or unable_to_determine with confidence, sources and top matches. Name-only matching: review every match. Use for onboarding backlogs or periodic re-screening. $0.50 per batch of up to 100 names, USDC on Base (x402).

Endpoints

URL	Transport	State	Latency	Checked
https://sanctions-batch-production.up.railway.app/mcp	streamable-http	answering	192 ms	10 min ago

Alternatives to Batch Sanctions Screening

same job, measured the same way

OFACScreen Sanctions Screening

by ofacscreen

Screen names and addresses on US, UN, EU, UK and other sanctions and export-control lists. Free.

5 tools answering

GCC Sanctions & Terror-List Screener

by noahsarch

Screen names vs OFAC, UN, EU, UK and UAE terrorist lists with Arabic-aware matching.

5 tools answering

Sanctions Screening (OFAC, EU, UK, UN)

by fairquery

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

answering

UK Sanctions Screening MCP

by donniertf-hub

Screen names vs the UK Sanctions List (FCDO/OFSI) plus OFAC crypto address checks.

12 tools answering

PayPerScreen

by tonythetiger22

Sanctions, crypto wallet, email and IP screening for agents. Pay per check in USDC via x402.

135 installs/wk local only

Sanctions

by ohmyfin

Sanctions and export-control screening for AI agents: 320+ watchlists, transliteration, HS and ECCN.

34 tools answering

Sanctions Screening

by hatchloop

Screen a name or entity against OFAC SDN, the EU Consolidated list and the UK list.

8 tools answering

Ofac Sanctions MCP

by mrfentmen

OFAC sanctions screening: search the SDN and consolidated lists by name, program or entity type and.

179 installs/wk local only

Batch Sanctions Screening — questions

Answers built from our own checks of this server.

What can Batch Sanctions Screening do?

It exposes 1 tools, read directly from the server on our last check. Among them: batch_sanctions_screen. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Batch Sanctions Screening working right now?

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

Is Batch Sanctions Screening still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Batch Sanctions Screening as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Batch Sanctions Screening?

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.

Does Batch Sanctions Screening need an API key?

No. Batch Sanctions Screening completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.