Overview

The Dataspike MCP Server exposes the Dataspike API to AI agents over the Model Context Protocol (MCP). Once connected, an LLM host — Claude Code, Cursor, and other MCP-capable clients — can run compliance tasks for you in natural language, without writing any integration code. Through the server an agent can:

AML screening — screen people and organizations against sanctions, PEP, and watchlists, and pull past results.
Applicants — look up applicant profiles and their latest AML reports.
Verifications — inspect KYC verification sessions and their event timelines.
KYB — poll business-verification results.
KYT — retrieve crypto-wallet check reports.
Email verification — fetch email-check results.
Deepfake detection — run authenticity analysis on selfie and ID-document images.

See the full list on the Tools page.

How it works

An MCP host connects to the server over HTTP and discovers the tools it exposes. The model decides which tool to call, and with what arguments, based on your request — you just describe the task. Results come back as structured data the agent can reason over and summarize. The managed server is available at:

https://mcp.dataspike.io/mcp

Authentication

The server authenticates to Dataspike with your API key, passed once in the client configuration as a bearer token:

Authorization: Bearer <YOUR_API_KEY>

You configure this in your MCP client settings (see below) — there’s no need to include the key in your messages. Generate an API key in the Dataspike Dashboard.

One tool, list_aml_sources, queries a public catalog endpoint and does not require an API key. Every other tool calls the authenticated Dataspike API.

Connect your client

Claude Desktop
Claude Code
Cursor
Codex CLI

Claude Desktop connects over OAuth as a custom connector — no manual header; you authorize once with your Dataspike API key. (Custom connectors are in beta — Free, Pro, Max, Team, and Enterprise.)

Open connector settings

In Claude Desktop, go to Customize → Connectors.

Add a custom connector

Click +, then Add custom connector, and enter the URL:

https://mcp.dataspike.io/mcp

Leave Advanced settings empty — the server registers your client automatically. Click Add.

Authorize with your API key

Click Connect. A Dataspike sign-in page opens — paste your Dataspike API key and authorize. The connector shows as connected and the Dataspike tools become available in chat.

On Team / Enterprise, an owner first adds the connector under Organization settings → Connectors → Add → Custom → Web; members then Connect it from Customize → Connectors.

Add to .claude/settings.json in your project root:

{
  "mcpServers": {
    "dataspike": {
      "type": "http",
      "url": "https://mcp.dataspike.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Open Settings → MCP → Add server and configure:

URL: https://mcp.dataspike.io/mcp
Header: Authorization: Bearer <YOUR_API_KEY>

Edit ~/.codex/config.toml (or .codex/config.toml in a trusted project). Codex reads the bearer token from an environment variable and sends it as Authorization: Bearer <token>:

[mcp_servers.dataspike]
url = "https://mcp.dataspike.io/mcp"
bearer_token_env_var = "DATASPIKE_API_KEY"

Then export your key before launching Codex:

export DATASPIKE_API_KEY="<YOUR_API_KEY>"

Example prompt

Once connected, just ask in plain language:

Check John Smith for AML, country United Kingdom

The agent picks the right tool (search_aml), fills in the arguments, and reports the risk level and matches.

How it works

Authentication

Connect your client

Example prompt

Next steps

Tools

API Reference

​How it works

​Authentication

​Connect your client

​Example prompt

​Next steps

Tools

API Reference

How it works

Authentication

Connect your client

Example prompt

Next steps