OFAC SDN Screening MCP Server

com.bonissystems/ofac-sdn-screening

answering

OFAC SDN Screening is answering right now. Last checked 2 min ago. It exposes 2 tools.

Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.

Uptime history 39 hours of history

39 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

254 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ofac-sdn-screening --transport http https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ofac-sdn-screening": {
      "url": "https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.ofac-sdn-screening]
url = "https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ofac-sdn-screening": {
      "url": "https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "ofac-sdn-screening": {
      "url": "https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp"
    }
  }
}

Available tools 2

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

screen

screen_sdn

Screen a name against the public OFAC SDN list. Returns a verdict (no-match / potential-match) and ranked matches with the OFAC list entry and the field that matched. The query is NOT stored or anchored on this path. A potential match requires human review — it is information, not a legal or compliance determination.

sdn

get_sdn_list_meta

Return the provenance of the loaded OFAC SDN list: source URL, publish date, record count, fetch time, and the source + index content hashes. No input, no PII. Use this to confirm which list version a screening ran against.

Endpoints

URL	Transport	State	Latency	Checked
https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp	streamable-http	answering	220 ms	2 min ago

OFAC SDN Screening — questions

Answers built from our own checks of this server.

What can OFAC SDN Screening do?

It exposes 2 tools, read directly from the server on our last check. Among them: get_sdn_list_meta, screen_sdn. 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 OFAC SDN Screening working right now?

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

How do I connect OFAC SDN Screening?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does OFAC SDN Screening need an API key?

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

How fast is OFAC SDN Screening?

It answers our handshake in 254 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.