- 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.
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:Authentication
The server authenticates to Dataspike with your API key, passed once in the client configuration as a bearer token: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
Point your client athttps://mcp.dataspike.io/mcp and add the Authorization header with your API key.
- Claude Code
- Cursor
- Codex CLI
Add to
.claude/settings.json in your project root:Example prompt
Once connected, just ask in plain language:Check John Smith for AML, country United KingdomThe agent picks the right tool (
search_aml), fills in the arguments, and reports the risk level
and matches.
Next steps
Tools
Browse every tool the server exposes, grouped by domain, with parameters.
API Reference
The underlying Dataspike endpoints, request/response schemas, and parameters.