ComplyCube MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/complycube and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 7 Nov 2026. Not supplied by the maker.

• 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

• 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 r

• 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). Compl

• 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/check

• 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 aga