Security & Testing

compliapi.com

MCP server for screening crypto addresses, emails, websites, government IDs, and countries against sanctions and crime lists.

x402 supported1 endpoint7 known toolsFirst detected August 9, 2026Last detected August 12, 2026

ENDPOINT 1

https://api.compliapi.com/mcp

No auth detected

MCP server metadata

Name: CompliAPI
Version: 3.4.3

Capabilities

experimentalloggingprompts.listChangedresources.listChangedtools.listChangedextensions.io.modelcontextprotocol/ui

Server instructions

Sanctions and financial-crime screening. Screen crypto addresses, emails, websites, and government IDs across multiple source lists — US OFAC SDN, FBI Lazarus Group addresses, Israel NBCTF seizures, the French Trésor register, Japan MOF sanctions, the EU consolidated list, the UK Sanctions List (FCDO), ransomwhe.re ransomware addresses, and Tornado Cash association lists (depositors/relayers, plus an opt-in withdrawal-recipient list). Every match names its list; `sanctioned` means a government sanctions list matched, `flagged` also covers crime-intelligence and risk-exposure lists. Country designations are OFAC-curated today; VPN detection and IP geolocation are utilities.

Known tools 7

screen_crypto_address

Screen a crypto address on any chain (or an ENS name, e.g.

Inferred read-only

screen_email

Screen an email address across the enabled sanctions and crime lists.

Potential side effects

screen_website

Screen a website or domain across the enabled sanctions and crime lists.

Inferred read-only

screen_government_id

Screen a government-issued ID (passport, tax ID, …) across the enabled lists (fuzzy matching).

Inferred read-only

screen_country

Check whether a country or region carries sanctions designations (OFAC-curated today).

Inferred read-only

detect_vpn

Detect whether an IP address is using a VPN.

Inferred read-only

geolocate_ip

Geolocate an IP address and flag whether it is in a sanctioned country.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.compliapi]
url = "https://api.compliapi.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "compliapi": {
      "type": "http",
      "url": "https://api.compliapi.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: compliapi
Remote MCP URL: https://api.compliapi.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "compliapi": {
      "url": "https://api.compliapi.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "compliapi": {
      "type": "http",
      "url": "https://api.compliapi.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "compliapi",
  "transport": "streamable-http",
  "url": "https://api.compliapi.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.