ComplyCube MCP by usefulapi

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

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
97%
Qualität der Benennung
80%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,617Tokens (Tool-Definitionen)
~2.2 KBTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (1.26% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "complycube": {
      "url": "https://complycube.usefulapi.io/mcp"
    }
  }
}

Remote-Endpunkte

https://complycube.usefulapi.io/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (6)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢complycube_list_clients(type, email, externalId, createdAfter, createdBefore, ...)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "type": {
      "description": "Only clients of this type.",
      "type": "string",
      "enum": [
        "person",
        "company"
      ]
    },
    "email": {
      "description": "Only clients with this email address.",
      "type": "string"
    },
    "externalId": {
      "description": "Only clients with this external id (your own customer id).",
      "type": "string"
    },
    "createdAfter": {
      "description": "Only clients created after this time (ISO 8601 date-time, for example 2026-11-01T00:00:00Z).",
      "type": "string"
    },
    "createdBefore": {
      "description": "Only clients created before this time (ISO 8601 date-time, for example 2026-11-01T00:00:00Z).",
      "type": "string"
    },
    "page": {
      "description": "Page number (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "pageSize": {
      "description": "Items per page (default 100).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢complycube_get_client(clientId)

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

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "clientId": {
      "type": "string",
      "minLength": 1,
      "description": "The client id."
    }
  },
  "required": [
    "clientId"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴complycube_create_client(type, email, mobile, telephone, externalId, ...)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "person",
        "company"
      ],
      "description": "The type of client."
    },
    "email": {
      "type": "string",
      "minLength": 3,
      "description": "The client's email address (required by ComplyCube)."
    },
    "mobile": {
      "description": "The client's mobile number.",
      "type": "string"
    },
    "telephone": {
      "description": "The client's telephone number.",
      "type": "string"
    },
    "externalId": {
      "description": "Your own id for this client. Uniqueness is not enforced.",
      "type": "string"
    },
    "joinedDate": {
      "description": "The date the client joined (yyyy-mm-dd), for migrated clients.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "personDetails": {
      "description": "Details for a person client.",
      "type": "object",
      "properties": {
        "firstName": {
          "type": "string",
          "description": "First name (required for type person)."
        },
        "middleName": {
          "type": "string"
        },
        "lastName": {
          "type": "string",
          "description": "Last name (required for type person)."
        },
        "dob": {
          "description": "Date of birth (yyyy-mm-dd).",
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "gender": {
          "type": "string",
          "enum": [
            "male",
            "female",
            "other"
          ]
        },
        "nationality": {
          "description": "Two-letter ISO country code.",
          "type": "string",
          "minLength": 2,
          "maxLength": 2
        },
        "birthCountry": {
          "description": "Two-letter ISO country code.",
          "type": "string",
          "minLength": 2,
          "maxLength": 2
        }
      },
      "required": [
        "firstName",
        "lastName"
      ]
    },
    "companyDetails": {
      "description": "Details for a company client.",
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "Company name (required for type company)."
        },
        "website": {
          "type": "string"
        },
        "registrationNumber": {
          "description": "Company registration or incorporation number.",
          "type": "string"
        },
        "incorporationType": {
          "type": "string"
        },
        "incorporationCountry": {
          "description": "Two-letter ISO country code.",
          "type": "string",
          "minLength": 2,
          "maxLength": 2
        }
      },
      "required": [
        "name"
      ]
    }
  },
  "required": [
    "type",
    "email"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢complycube_list_checks(clientId, type, status, outcome, createdAfter, ...)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "clientId": {
      "description": "Only checks for this client id.",
      "type": "string"
    },
    "type": {
      "description": "Only checks of this type, for example standard_screening_check.",
      "type": "string"
    },
    "status": {
      "description": "Only checks with this status.",
      "type": "string",
      "enum": [
        "pending",
        "complete",
        "failed"
      ]
    },
    "outcome": {
      "description": "Only checks with this result outcome.",
      "type": "string",
      "enum": [
        "clear",
        "attention",
        "not_processed",
        "rejected"
      ]
    },
    "createdAfter": {
      "description": "Only checks created after this time (ISO 8601 date-time, for example 2026-11-01T00:00:00Z).",
      "type": "string"
    },
    "createdBefore": {
      "description": "Only checks created before this time (ISO 8601 date-time, for example 2026-11-01T00:00:00Z).",
      "type": "string"
    },
    "page": {
      "description": "Page number (default 1).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "pageSize": {
      "description": "Items per page (default 100).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢complycube_get_check(checkId)

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

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "checkId": {
      "type": "string",
      "minLength": 1,
      "description": "The check id."
    }
  },
  "required": [
    "checkId"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴complycube_create_aml_check(clientId, type)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "clientId": {
      "type": "string",
      "minLength": 1,
      "description": "The client id."
    },
    "type": {
      "type": "string",
      "enum": [
        "standard_screening_check",
        "extensive_screening_check"
      ],
      "description": "standard_screening_check (basic) or extensive_screening_check (full)."
    }
  },
  "required": [
    "clientId",
    "type"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet6 Tools