Identitycheck
IdentityCheck is a verification solution designed to authenticate user identities with precision and speed, utilizing advanced algorithms and comprehensive data sources to ensure accurate validation, mitigate fraud, and enhance security.
Verdict
Common use cases
- Pull failed onboardings from the last 48 hours
- Audit verification attempts by user ID
- List active webhook endpoints for compliance review
- Fetch configuration details before updating settings
- Check API status before running batch queries
Integration
- Vendor
- Identitycheck
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
identitycheck
Tools
- Check API Health
Tool to perform API health check. Use to verify API availability before other operations.
- Delete configurationdestructive
Tool to delete an existing configuration. Use when you need to remove a configuration by its unique code.
- Delete Notification Endpointdestructive
Tool to delete a notification endpoint. Use after confirming the endpoint code exists and you need to remove it.
- Fetch All Configurations
Tool to fetch all existing configurations. Use when you need to list all customer configurations after authentication.
- Fetch all notification endpoints
Tool to fetch all notification endpoints. Use when you need to list all existing notification endpoints.
- Fetch Configuration
Tool to fetch a configuration by its code. Use when you need detailed settings of a specific identity check configuration.
- Fetch Notification Endpoint
Tool to fetch a notification endpoint by its code. Use when you need the current configuration of a specific callback endpoint.
- Fetch Onboardings
Tool to retrieve onboardings. Use when you need to list onboardings with filters like UID, status, date range, etc. Example: List onboardings created since 2023-01-01 with status SUCCESS
- Get Document Content
Tool to retrieve base64-encoded document content. Use when you have an onboarding UID and document code.
- Retrieve Onboarding Status
Tool to retrieve the status of an onboarding. Use after creating an onboarding to check its progress and final result.
- Update Configuration
Tool to update an existing configuration. Use when you need to modify properties of a configuration identified by code.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP integrations panel. 2. Select 'Add MCP' and choose Identitycheck from the directory. 3. Log into your Identitycheck dashboard, navigate to API settings, and generate a new API key with read access to onboardings and configurations. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Return to any Space and type '@Identitycheck check API health' to confirm the connection works. 6. If the health check succeeds, you can now query onboardings, fetch configurations, and manage notification endpoints by @mentioning Identitycheck in any message.
What teammates see: by default, memories from Identitycheck are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Recent Failed Verifications
@Identitycheck fetch onboardings with status FAILED created since seven days ago. Show me the UID, creation date, and any error codes.Open in a Space →
List All Configurations
@Identitycheck fetch all configurations. For each one, show the code, name, and whether it's currently active.Open in a Space →
Audit Webhook Endpoints
@Identitycheck fetch all notification endpoints. Display the endpoint URL, code, and any associated configuration codes.Open in a Space →
User Onboarding Lookup
@Identitycheck fetch onboardings for UID user_12345. Show me the status, creation date, and any linked configuration.Open in a Space →
Health Check Before Batch
@Identitycheck check API health. If the service is up, confirm we're ready to proceed with bulk onboarding queries.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Identitycheck list all onboardings from the past 7 days with status PENDING and summarize what's blocking completion
Found 12 pending onboardings from the past week. Most common blocking factors: 3 users awaiting document upload (passport or driver's license), 5 users with blurry photo submissions requiring retake, 2 users stuck at liveness check, and 2 users who haven't completed the email verification step. Average time in PENDING state is 2.3 days. The onboarding UIDs and specific block reasons are available if you need to follow up individually.
This example shows the MCP's filtering capabilities (date range, status) paired with AI synthesis to surface patterns. Requires API key with read access to onboarding data. Note that the MCP returns raw onboarding records; the AI interprets common failure modes from status fields.
@Identitycheck create a new configuration called 'contractor-verification' requiring passport and proof of address, then give me the configuration code
Created configuration 'contractor-verification' with code CFG_8x4k2p9m. This configuration requires two document types: passport (for identity verification) and proof of address (utility bill or bank statement accepted). Liveness check is enabled by default. Notification webhooks are not yet configured—you'll need to add an endpoint separately if you want real-time status updates.
Demonstrates the MCP's write capability for setting up identity verification workflows. Requires API key with configuration write permissions. The configuration code is essential for linking future onboarding sessions to this ruleset. Side-effect: this configuration is now live and billable per verification attempt.
@Identitycheck check API health and list all notification endpoints, then tell me if we're set up to receive webhook callbacks
API health check passed—all Identitycheck services are operational. Found 2 active notification endpoints: 'prod-webhook' (https://api.yourcompany.com/identity-callbacks) receiving SUCCESS and FAILURE events, and 'slack-alerts' (https://hooks.slack.com/...) receiving only FAILURE events. You're configured to receive real-time callbacks for completed and failed verifications. Both endpoints last received a ping 14 hours ago.
Combines a health check with endpoint discovery to audit integration readiness. Useful before launching a new verification flow. The health check tool is rate-limited (recommended max once per minute). Notification endpoint data includes URL and event filters, but not authentication secrets.
Use-case deep-dives
When Identitycheck fits quarterly KYC compliance reviews
A 6-person fintech startup runs quarterly compliance audits where the CFO and legal counsel need to pull all identity verification records from the last 90 days and confirm webhook delivery. Identitycheck's Fetch Onboardings tool filters by date range and status, so you can script a query that exports SUCCESS and FAILED verifications into a spreadsheet for the auditor. The Delete Notification Endpoint tool lets you rotate webhook URLs after each audit cycle without touching production code. This works cleanly if you're verifying under 500 users per quarter. Above that volume, you'll want a dedicated compliance dashboard instead of ad-hoc MCP queries. If your audit cadence is monthly or you need real-time alerting, set up persistent webhooks and skip the MCP for routine pulls.
Use this MCP to validate identity check flows before launch
A 3-person SaaS team is adding identity verification to their signup flow and needs to test different configuration profiles (strict vs. lenient document checks) in staging before going live. The Fetch All Configurations and Fetch Configuration tools let you inspect each profile's settings in plain text, so you can compare thresholds and required fields without logging into the vendor dashboard. The Delete Configuration tool cleans up test profiles after each sprint. This MCP shines when you're iterating on 2-4 config variants and want to script the comparison. If you're running A/B tests across 10+ profiles or need to version-control config changes, you'll outgrow the MCP and need a proper CI pipeline that hits the API directly. For pre-launch validation and small-batch testing, this MCP saves you 15 minutes per config review.
When support agents need ad-hoc onboarding status checks
A 12-person marketplace has a support team that fields 5-10 tickets per day asking why a seller's identity verification is stuck. The Fetch Onboardings tool filters by UID or status, so an agent can paste the user's email into Switchy and get the verification timeline and failure reason in 10 seconds. The Check API Health tool confirms the service is up before the agent tells the customer to retry. This works when your support volume is under 50 identity-related tickets per week and you don't have a custom admin panel. Above that threshold, you need a proper support dashboard with embedded verification status. If your agents are non-technical or you're handling PII at scale, the MCP's API-key auth becomes a liability—rotate to a scoped service account and build a UI instead.
Frequently asked
What does the Identitycheck MCP do in Switchy?
It connects your team's Switchy workspace to Identitycheck's identity verification API. You can check API health, manage verification configurations, retrieve onboarding records filtered by status or date, and configure notification endpoints for callbacks — all without leaving your AI chat. Useful for compliance teams running KYC workflows who want to query verification data conversationally.
Do I need admin access to connect Identitycheck?
You need an Identitycheck API key with permissions to read configurations and onboardings. If your team wants to delete configurations or notification endpoints through Switchy, the key must have write access too. Check with your Identitycheck account owner to generate a key with the right scopes before connecting.
Can the MCP trigger new identity verifications?
No. The available tools fetch existing onboardings and manage configurations, but they don't initiate new verification sessions. To start a verification, you still use Identitycheck's web dashboard or their direct API. This MCP is for querying results and managing settings after verifications run.
Why use this instead of logging into Identitycheck directly?
If you're already in Switchy discussing a customer case, you can pull their onboarding status or check API health inline without context-switching to another tab. It's faster for ad-hoc queries during support calls. For bulk operations or building verification flows, Identitycheck's native dashboard or API is still the better choice.
Who on the team should connect the Identitycheck MCP?
Whoever handles compliance or customer onboarding queries. They'll need the API key from your Identitycheck account, so coordinate with your admin. Once connected in Switchy, any workspace member can ask questions that trigger the tools, but the connection itself uses one shared API key per workspace.