ComplyCube MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.0.0Updated Nov 7, 2026

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

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableFinanceSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Hosted ComplyCube connector that lets an assistant list and create clients, run AML screening checks and read check results.

What you can do
  • List and read client records, including contact, personal or company details and metadata
  • Create new person or company client records before running checks
  • List and filter checks by client, type, status or outcome
  • Read a single check's status and result breakdown
  • Start AML screening checks (sanctions, PEP, watchlist) in standard or extensive mode
  • Check monthly usage and manage the subscription plan
When to use it
Useful when you work with ComplyCube for KYC or AML compliance and want to look up clients, create records, launch screening checks or review outcomes from a chat client instead of the ComplyCube portal.
Requirements
Remote MCP endpoint; no local install. Sign-in is via OAuth, and on first connect you supply a ComplyCube API key (test or live) from the ComplyCube portal, which the server stores per user. A ComplyCube account is required; the free plan allows 50 tool calls per month.
Before you install
Creating clients and starting AML checks write data and should be confirmed first; AML checks run in the background and count against the account's monthly check quota. Your ComplyCube API key is handed to a third-party host, which stores it per user. Paid plans are billed through a Stripe checkout link, and cancelling does not refund the current period.

Installation

In SourceWeft

  1. Open ComplyCube MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fcomplycube/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "complycube-by-usefulapi": {
      "type": "http",
      "url": "https://complycube.usefulapi.io/mcp"
    }
  }
}

README

ComplyCube MCP by usefulapi

Use your ComplyCube account from Claude, Cursor, or any MCP client. It lists and creates clients, runs AML screening checks and reads check results. Hosted, no local install: connect with your own credentials.

Live endpoint: https://complycube.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://complycube.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http complycube https://complycube.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "complycube": {      "url": "https://complycube.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your ComplyCube credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/complycube/

On first connect you provide your ComplyCube API key (a test_ or live_ key from Developers → API keys in the ComplyCube portal). The server validates it and stores it per user. No keys go in config files.

Tools

ToolTypeWhat it does
complycube_list_clientsreadList clients
complycube_get_clientreadGet a client
complycube_create_clientwriteCreate a client
complycube_list_checksreadList checks
complycube_get_checkreadGet a check
complycube_create_aml_checkwriteRun an AML screening check
complycube_usage_statusmetaUsage status (free-tier meter)
complycube_request_featuremetaRequest a missing feature
complycube_upgrademetaUpgrade to Pro or Pro+
complycube_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with complycube_upgrade (it returns a Stripe Checkout link). Cancel any time with complycube_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running complycube_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/complycube/README.md at commit 2450437

Tools

6

complycube_list_clients

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.

ParameterspagetypeemailpageSizeexternalIdcreatedAftercreatedBefore

complycube_get_client

Get a client

Get one client by id: type, contact details, personal details or company details, metadata and timestamps. ComplyCube API: GET /v1/clients/{clientId}.

ParametersclientIdrequired

complycube_create_client

Create a 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.

ParameterstyperequiredemailrequiredmobiletelephoneexternalIdjoinedDatepersonDetailscompanyDetails

complycube_list_checks

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.

ParameterspagetypestatusoutcomeclientIdpageSizecreatedAftercreatedBefore

complycube_get_check

Get a 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}.

ParameterscheckIdrequired

complycube_create_aml_check

Run an AML screening 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 API: POST /v1/checks.

ParameterstyperequiredclientIdrequired

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations