Available MCP tools and their arguments
Updated
CompliAPI exposes eight tools through its MCP server: six for screening entities against sanctions and crime lists, and two for network checks. Every tool returns the same JSON envelope as its REST counterpart and is metered against your organization's monthly quota. Without a token, each tool call accepts an x402 micropayment per call.
Screening tools
The five list-screening tools each accept the value to screen plus an optional lists argument — a comma-separated set of source list slugs that narrows the check to specific lists. Unknown slugs produce a tool error. Responses follow the standard screening envelope: sanctioned is true only for government sanctions-list hits, flagged is true for any hit (including crime-intelligence and risk-exposure lists), and matches names the specific list behind each hit.
| Tool | Arguments | What it screens |
|---|---|---|
screen_crypto_address | address, lists? | A crypto address on any chain; ENS names (e.g. vitalik.eth) are resolved before screening |
screen_email | email, lists? | An email address |
screen_website | website, lists? | A website or domain |
screen_government_id | government_id, lists? | A government-issued ID (passport, tax ID, etc.), fuzzy-matched |
screen_country | country, lists? | A country or region's sanctions designations |
screen_pep is the sixth screening tool and works differently from the others. It proxies the OpenSanctions politically exposed persons (PEP) dataset and takes three arguments — name (required), birth_date (optional), and country (optional). It does not accept a lists argument, and its response follows the /screen/pep shape rather than the standard screening envelope. It is also priced higher than the other screening tools because its upstream dataset is metered per query.
Network tools
| Tool | Arguments | What it returns |
|---|---|---|
detect_vpn | ip_address | Whether the IP is using a VPN — same shape as GET /vpn |
geolocate_ip | ip_address | The IP's city, region, and country, flagging whether that country is sanctioned — same shape as GET /geo |
Error behavior
Over-quota calls return a tool error; if x402 is enabled, the error's structured content contains the payment challenge instead. Invalid arguments — an unrecognized lists slug, a malformed IP address — also come back as tool errors rather than protocol-level failures, so your agent can read the error message, correct its input, and retry without the whole session breaking.