Skip to main content
Point your client at https://api.compliapi.com/mcp. Three ways to authenticate:
  • OAuth — clients that support remote MCP servers (Claude, ChatGPT, Claude Code) open a browser, you sign in to CompliAPI and approve, and the client is connected. No token to copy.
  • API token — create one on the Tokens page and send it as a bearer header.
  • x402 — skip the account entirely and pay per call.
Authorized OAuth apps are listed under Connected apps on the Tokens page, where you can disconnect any of them.

​
Claude Code

The official plugin bundles the server plus a /compliapi:screen workflow skill:
It picks up your token from COMPLIAPI_API_TOKEN or ~/.compliapi/token (or runs tokenless via x402). To add the bare server instead:

​
JSON configuration

For clients configured via a JSON file (Cursor’s ~/.cursor/mcp.json, Claude Code’s .mcp.json, and most others):
Clients that add remote servers through a UI (custom connectors and similar) only need the URL — https://api.compliapi.com/mcp — plus the Authorization header if the UI supports custom headers.

​
Verify the connection

Ask the agent to list its tools — the seven CompliAPI tools should appear — then try a screen:
Screen the address 0x098B716B8Aaf21512996dC57EB0615e2383E2f96 against the sanctions lists.
The agent should call screen_crypto_address and report a Lazarus Group OFAC hit.

​
Anonymous access

Without an Authorization header the connection still works: initialize and tools/list are free, and each tool call returns an x402 payment challenge until an X-PAYMENT header is supplied. Tool calls made with a valid token are metered against your organization’s quota exactly like REST requests.