NestDaddy

SanctionScreen

io.sanctionsscreen/sanctionscreen · v1.0.0

Screen counterparties and enrich companies for AI agents — sanctions checks, cited sources.

Connect Remote server

Terminal
claude mcp add --transport http sanctionscreen https://api.sanctionsscreen.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "sanctionscreen": {
      "url": "https://api.sanctionsscreen.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sanctionscreen": {
      "type": "http",
      "url": "https://api.sanctionsscreen.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://api.sanctionsscreen.io/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 2 found in our last check

  • screen_counterparty

    Screen a counterparty name against the indexed sanctions lists (OFAC SDN, UK FCDO consolidated). What it does: normalizes the query (Unicode NFKD fold, punctuation strip, lowercase, Cyrillic/Greek transliteration; tolerant to token order e.g. "Putin Vladimir" vs "Vladimir Putin"…

  • enrich_company

    Resolve a company domain or legal name to structured company facts via the free public GLEIF LEI registry. Inputs: {domain? e.g. "apple.com", name? e.g. "Apple Inc.", request_id? (idempotency)}. At least one of domain/name is required. v1 boundaries (returned honestly, never inv…

Headers

NameDescription
Authorization
Required, secret
SanctionScreen API key (cs_live_…), sent as Bearer token

Details

Endpointhttps://api.sanctionsscreen.io/mcp (Streamable HTTP)
First published26 Sep 2026
Last updated26 Sep 2026
Registry nameio.sanctionsscreen/sanctionscreen

More ai and media servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.