SanctionScreen MCP MCP server

SanctionScreen provides an MCP server that enables AI agents to perform sanctions screening and company enrichment. It offers two primary tools: screen_counterparty to check names against OFAC and UK FCDO sanctions lists with cited confidence scores, and enrich_company to retrieve structured legal and operational details for a given domain. The service ensures compliance by providing full citations and source tracing for every data point returned.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by SanctionScreen

MCP endpoint (Streamable HTTP)

https://api.sanctionsscreen.io/mcp

Vendor documentation

What you can do with it

Screen counterparty names against OFAC and UK sanctions lists
Enrich company profiles using domain names
Verify identity with confidence scores and citations
Integrate compliance checks into AI agent workflows

Tools advertised by the last live check:

screen_counterparty
enrich_company

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http sanctionscreen-mcp https://api.sanctionsscreen.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add sanctionscreen-mcp --url https://api.sanctionsscreen.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable sanctionscreen-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "sanctionscreen-mcp": {
      "url": "https://api.sanctionsscreen.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "sanctionscreen-mcp": {
      "type": "streamableHttp",
      "url": "https://api.sanctionsscreen.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start sanctionscreen-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "sanctionscreen-mcp": {
      "type": "http",
      "url": "https://api.sanctionsscreen.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http sanctionscreen-mcp https://api.sanctionsscreen.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "sanctionscreen-mcp": {
      "url": "https://api.sanctionsscreen.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "sanctionscreen-mcp": {
      "serverUrl": "https://api.sanctionsscreen.io/mcp"
    }
  }
}

See all 1,583

Do you run SanctionScreen MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing