Sumsub MCP for AI. Manage KYC/AML identity checks from your chat client.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Sumsub integrates identity verification (KYC/AML) directly into your AI workflow. Use this server to create new applicants, upload required documents like passports or IDs, and track verification status—all without leaving your agent's chat window.
It handles the technical heavy lifting of compliance checks so you can focus on onboarding.
What AI agents can do with Sumsub Automation
Add document
Uploads a document (like an ID or passport) to an existing applicant's profile.
Create applicant
Creates and registers a brand new Sumsub applicant, defining the required KYC/AML level.
Generate access token
Generates a secure WebSDK access token for your users to integrate Sumsub into their own web apps.
Starts a new applicant profile in Sumsub, specifying the required KYC or AML verification level.
Retrieves the current compliance status of an applicant based on their unique ID.
Attaches identity documents (e.g., passports, IDs) to a specific applicant profile using base64 encoding.
Fetches the full profile data for an existing Sumsub applicant ID.
Creates a secure, time-limited access token necessary for integrating Sumsub's web SDK into client applications.
Ask an AI about this
Waiting for input…
What AI agents can do with Sumsub: 5 Tools for Compliance & Onboarding
These tools let your AI client manage the entire applicant lifecycle—from initial profile creation to final document verification status.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Sumsub on VinkiusAdd Document
Uploads a document (like an ID or passport) to an existing applicant's profile.
Create Applicant
Creates and registers a brand new Sumsub applicant, defining the required KYC/AML...
Generate Access Token
Generates a secure WebSDK access token for your users to integrate Sumsub into their...
Get Applicant Status
Checks the real-time verification status of a specific applicant against compliance...
Get Applicant
Retrieves all available profile data for an existing applicant ID.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Sumsub integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Sumsub, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Sumsub. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 5 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Compliance checks shouldn't require logging into five different dashboards., Solved with Vinkius AI Gateway
Today, verifying an applicant means jumping between the Sumsub dashboard, your internal CRM to pull user IDs, and then potentially opening a document management system just to upload a passport copy. You spend more time managing tabs than actually processing compliance.
With this MCP server, you tell your agent: 'Run KYC for User X.' The agent handles calling `create_applicant`, using that ID to run `get_applicant_status`, and then running `add_document`—all in sequence. You get the final status report without ever leaving your terminal.
Sumsub MCP Server: Manage identity verification from chat.
The manual process requires you to copy the applicant ID, then navigate back to the platform to check if documents were received. This is slow and prone to human error when dealing with high volumes of onboarding records.
Now, your agent uses `get_applicant` or `add_document`. It takes the data directly from your conversation context and executes the precise API call. The difference isn't convenience; it's reliability.
What your AI can actually do with this
You’re connecting your Sumsub account so your AI client can handle identity verification and compliance checks right in the chat window. Forget logging into a separate dashboard; you manage entire KYC/AML flows using natural language commands. This server handles all the technical heavy lifting required for onboarding, letting you focus on what matters.
When you need to get started with a new user, you'll use create_applicant. This tool registers a brand-new profile in Sumsub and lets you define the specific KYC or AML verification level that’s required. If you already have an applicant ID, you can check their current compliance status instantly by calling get_applicant_status.
You immediately know if they're pending review, if documents are missing, or if a requirement failed.
To get the full picture of any user, you fetch all available profile data using get_applicant with the existing Sumsub ID. This gives your agent everything it needs to move forward. If that isn’t enough, you'll use add_document. This tool uploads required identity proofs—like passports or driver's licenses—and attaches them directly to a specific applicant's profile using base64 encoding.
For building out external client applications, you need secure credentials. You generate these by calling generate_access_token, which creates a time-limited WebSDK access token. This is what your end-users use to initialize the Sumsub client directly within their own web app environment.
Essentially, this server gives your agent control over the entire identity verification lifecycle: creating the record, uploading all necessary documents, pulling the full profile data, checking the real-time compliance status, and even generating tokens so you can build out seamless integration into other systems. You've got everything needed to manage complex regulatory requirements without leaving your chat session.
019ea609-c3b1-7200-bf26-a8b0c64f0fba 
Here's how it actually works
The bottom line is: your AI client acts like an internal compliance assistant that executes complex API calls without you needing to touch a web dashboard.
First, subscribe to this server and provide your Sumsub App Token and Secret Key credentials.
Next, prompt your AI agent with a specific task (e.g., 'Check status for ID 123').
The agent runs the required tool, sends the data to the Sumsub API, and reports the result back directly.
Who is this actually for?
Compliance officers and operations teams who spend too much time clicking through dashboards are the primary users. If your job requires verifying identity or managing onboarding documents, this tool saves you from manual API calls.
Checks applicant statuses and verifies required documentation details without having to leave their workflow terminal.
Tests the full lifecycle—from creating an applicant record via create_applicant to generating a client token using generate_access_token—directly from their IDE or test environment.
Automates the intake of identity documents and tracks onboarding progress for large groups of new users in bulk.
What Changes When You Connect
Checks status instantly. Instead of manually logging into the Sumsub dashboard, you can call get_applicant_status and get the real-time compliance state right in your agent's response.
Automates document collection. Use add_document to upload passports or IDs directly from your workflow, associating them immediately with a specific applicant ID.
Builds client integrations faster. The generate_access_token tool gives you the necessary WebSDK token without any manual API playground steps.
Manages user records cleanly. Start profiles using create_applicant and retrieve everything later by calling get_applicant, all in one conversation thread.
Stops redundant checks. You don't need multiple tools for basic data; get_applicant gives you the full profile, saving time compared to piecing together separate pieces of data.
See it in action
Onboarding a New Client
A new user signs up. Your agent first calls create_applicant for the correct KYC level. Then, it prompts the user to upload their ID using add_document. Finally, it runs get_applicant_status repeatedly until Sumsub confirms approval.
Troubleshooting a Failed Check
An applicant's status is 'pending'. Instead of waiting for an email, your agent calls get_applicant to pull the full profile. This reveals which specific document (e.g., utility bill) was missing or flagged, allowing immediate follow-up.
Integrating into a Web App
Your development team needs Sumsub verification in a client portal. The agent runs generate_access_token to get the secure key, which they plug directly into their code base—no manual secret management needed.
Bulk Compliance Audit
The compliance team needs to audit 20 users. Instead of running 20 dashboard reports, your agent uses get_applicant_status iteratively for each ID, summarizing the entire group's compliance health in minutes.
The honest tradeoffs
Treating tools as separate APIs
A user thinks they have to run get_applicant, then copy the ID, and finally paste it into a different tool call for add_document. This is clunky.
Don't treat them separately. Run your workflow conversationally: 'First, use create_applicant for User X. Then, using that new ID, run get_applicant_status and finally attach the doc with add_document.' The AI handles the piping.
Checking status manually
Opening the Sumsub dashboard every hour to check if a file was accepted. This is time-consuming, requires switching contexts, and isn't scalable.
Just use get_applicant_status. Tell your agent: 'Check ID 123 status.' It gives you the current state immediately without leaving your terminal.
Ignoring token generation
Trying to embed Sumsub features into a custom web app by hardcoding credentials or using outdated keys. This is insecure and breaks often.
Always use generate_access_token first. Get the fresh, secure key that your AI agent runs for you before building anything.
When It Fits, When It Doesn't
Use this server if your workflow requires tracking identity verification status or handling document uploads for KYC/AML compliance. If you need to manage applicant records end-to-end—creation, data retrieval (get_applicant), status checks (get_applicant_status), and resource attachment (add_document)—this is the single point of truth.
Don't use this if your goal is simply general user authentication (use a standard OAuth flow) or if you only need to send basic messages. If all you need is to confirm an email address, don't bother with create_applicant; just check that data elsewhere. This server is for high-compliance identity management; it’s not a universal API gateway.
Questions you might have
How do I use Sumsub MCP Server to create a new applicant? +
You run create_applicant and specify the user details and the required KYC/AML level. The server returns the unique Sumsub Applicant ID, which you need for all subsequent steps.
Does `get_applicant_status` show if my documents were uploaded? +
It shows the verification status (e.g., 'pending' or 'approved'). To confirm document upload, use add_document first and then verify the record using get_applicant.
What is the best way to integrate Sumsub into my custom app? +
You must run generate_access_token. This tool creates a secure WebSDK token that your developers can safely embed in their code, rather than handling raw credentials.
Which tool should I use to get all data on an applicant? +
Use get_applicant. It pulls the full profile record and is better than calling multiple smaller tools because it gathers comprehensive data in one go.
How does using the `generate_access_token` tool handle security for my client calls? +
The token acts as a scoped key. You must generate this specific access token first, then pass it to other tools like get_applicant. This limits what your agent can do if any single endpoint is compromised.
What format must I use when calling the `add_document` tool? +
You need to provide the document data as a base64 encoded string. The tool requires this specific encoding for all identity documents, including passports and ID cards.
If I use `get_applicant_status`, what should I do if the status indicates an error? +
The response payload includes a dedicated error code. Your agent must read this specific code (e.g., INVALID_KYC) to know exactly why verification failed or what data is missing.
Does `get_applicant` support fetching multiple records at once, or am I limited? +
The tool supports pagination for large datasets. If your request exceeds the default batch size, you must pass a cursor or page number in subsequent calls to retrieve all applicant data.
Can I check if a specific user has passed their KYC verification? +
Yes. Use the get_applicant_status tool with the Applicant ID. The AI will return the current verification stage and whether they are approved, pending, or rejected.
How do I provide a verification link to my users? +
You can use the generate_access_token tool. It provides the necessary token to initialize the Sumsub WebSDK for a specific User ID and verification level.
Is it possible to upload a user's ID document directly through the agent? +
Yes, by using the add_document tool. You will need the Applicant ID, the document type (like PASSPORT), the country code, and the base64 encoded content of the file.
We've already built the connector for Sumsub. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 5 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.