US Export Control Screening (CSL) MCP Server

by pcp183 Your server? Claim it

not responding

US Export Control Screening (CSL) is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Screen a party vs the US Consolidated Screening List before export. $0.02/call 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

183 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 screen_export_control

US Export Control Screening (CSL) 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 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add export-screen --transport http https://export-screen-production.up.railway.app/mcp

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

https://export-screen-production.up.railway.app/mcp

~/.codex/config.toml

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

.cursor/mcp.json

{
  "mcpServers": {
    "export-screen": {
      "url": "https://export-screen-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "export-screen": {
      "type": "http",
      "url": "https://export-screen-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.

screen

screen_export_control

Screen a buyer or consignee against US export-control lists before selling or shipping. Matches a name against the official US Consolidated Screening List (11 lists incl. BIS Entity List, Denied Persons, ITAR Debarred, SDN). Returns no_match, possible_match, confirmed_match or unable_to_determine with confidence, sources and coverage_limitations. No EU/UK lists; not legal advice. Use when a deal may involve US-origin items or technology. $0.02 per call, USDC on Base (x402).

Endpoints

URL	Transport	State	Latency	Checked
https://export-screen-production.up.railway.app/mcp	streamable-http	answering	183 ms	9 min ago

Alternatives to US Export Control Screening (CSL)

same job, measured the same way

Sanctions & PEP Screening

by macaroonnetwork

Screen a name in one call against US OFAC SDN, the EU Consolidated Financial Sanctions List, UK…

96 installs/wk local only

Sanctions Screening

by hatchloop

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

8 tools answering

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

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

Endpoint Diligence

by x402supply

Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.

3 tools answering

Sanctions Screening MCP Server

by cyanheads

Screen eleven sanctions/export-control lists; resolve GLEIF entities offline. Screening aid.

499 installs/wk 7 tools answering

Rugsight

by workers-rugsight-rugsight

Solana token rug-risk scores. Free basic score; full report pay-per-call via x402 (0.03 USDC).

2 tools answering

Frisk

by tryfrisk

Screen the counterparty of an x402 payment before an agent pays it. Runs offline by default.

47 installs/wk local only

US Export Control Screening (CSL) — questions

Answers built from our own checks of this server.

What can US Export Control Screening (CSL) do?

It exposes 1 tools, read directly from the server on our last check. Among them: screen_export_control. 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 US Export Control Screening (CSL) 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 183 ms. The bar chart above shows every period we have measured.

Is US Export Control Screening (CSL) 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 US Export Control Screening (CSL) 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 US Export Control Screening (CSL)?

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 US Export Control Screening (CSL) need an API key?

No. US Export Control Screening (CSL) 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.