ComplyCube MCP by usefulapi

io.usefulapi/complycube · v1.0.1 · sales-and-crm

ComplyCube MCP by usefulapi is healthy: it completed an MCP handshake in 536 ms and exposes 6 tools.

List and create clients, run AML screening checks and read results in ComplyCube.

Endpoint: https://complycube.usefulapi.io/mcp (streamable-http)

Facts

Checked (UTC)	Status	Latency	Error
2026-11-07T21:50:25.739Z	Healthy	536

`complycube_list_clients`	List the clients (people or companies) on the account, newest first. Each client has an id, type, contact details and metadata. Use this to find a client id before running a check. ComplyCube API: GET /v1/clients.
`complycube_get_client`	Get one client by id: type, contact details, personal details or company details, metadata and timestamps. ComplyCube API: GET /v1/clients/{clientId}.
`complycube_create_client`	Create a client record before running checks on it. Give personDetails for type person, or companyDetails for type company. Store only the fields the checks need. The new client id comes back in the reply. ComplyCube API: POST /v1/clients.
`complycube_list_checks`	List checks (identity, document, AML screening and others), newest first. Filter by client, check type, status (pending, complete, failed) or outcome (clear, attention, not_processed, rejected). ComplyCube API: GET /v1/checks.
`complycube_get_check`	Get one check by id: its type, client, status, and the result (outcome and the breakdown of each part). Use it to read the result of a screening check after it completes. ComplyCube API: GET /v1/checks/{checkId}.
`complycube_create_aml_check`	Start an AML screening check for an existing client: sanctions, PEP and watchlist screening. Standard is the basic screen; extensive is the full screen. The check runs in the background and counts against the account's monthly check quota. Read the result later with complycube_get_check. ComplyCube