MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

ComplyCube MCP by usefulapi

By usefulapi.io Verified namespace

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

WebsiteSource code
Connect to ComplyCube MCP by usefulapi
Checks passed
14 / 22

0 failed · 8 not measured

Median response
212 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
6

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 212 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name complycube-mcp.

  • Pass
    Lists tools

    tools/list returned 6 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 212 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 212 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    35 of 39 parameters have a description (90%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:35:16.674425Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using ComplyCube MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http complycube-mcp-by-usefulapi https://complycube.usefulapi.io/mcp

Capabilities

Tools 6

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 API: POST /v1/checks.

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

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

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

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

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

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected212 ms6

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to ComplyCube MCP by usefulapi