AI Agent Integration (MCP Server)

​

Overview

Connect the power of deepidv to your AI workflows. The deepidv hosted MCP server lets your organization securely use deepidv from compatible AI clients. Once an account member authorizes access through OAuth, the client can interact with deepidv tools and perform supported actions with that member’s permissions. With this integration, you can:

• Search applicants and inspect invitation status
• List, inspect, create, and manage verification sessions
• Create and reuse workflows with deepidv verification steps
• List bank statement records and send bank statement requests
• Run PEP/sanctions, title-check, and adverse-media screening tools

​

Requirements

You’ll need the following before connecting a client:

• An active deepidv account
• Your deepidv login credentials
• Your MFA device or authentication method, if enabled
• An MCP client that supports remote HTTP servers with OAuth 2.0 Authorization Code + PKCE

​

Server details

​

Connection model

Most clients only need the MCP server URL. deepidv exposes:

• mcp.json discovery metadata
• OAuth protected-resource metadata
• a fixed shared OAuth client ID: deepidv

In practice, the happy path is:

1. Add https://mcp.deepidv.com/v1/mcp as a remote MCP server.
2. Let the client discover the OAuth metadata automatically.
3. If the client explicitly asks for client_id, enter deepidv.
4. Do not provide a client_secret.
5. Complete the browser-based deepidv sign-in flow.

​

Setup by Client

​

Any compatible remote MCP client

Use these steps for clients that support remote MCP servers with OAuth discovery.

​

Redirect URIs currently supported by the hosted OAuth server

deepidv currently allows connector-native redirect URIs for these client families:

• Claude web/desktop callbacks
• Cursor
• VS Code
• ChatGPT connectors

If your client uses a different fixed redirect URI, contact deepidv support before rollout.

​

Authentication Model

deepidv uses hosted OAuth 2.0 with PKCE for MCP access. The browser approval flow authenticates the end user directly against deepidv’s hosted login screens:

• client_id is the fixed shared public client ID: deepidv
• client_secret is not used
• token exchange uses PKCE with S256
• the user signs in with their deepidv email and password
• MFA is enforced when required by the account

Access is scoped to the authenticated deepidv user and organization. Each tool call is validated against active account state before it runs.

​

Available Tools

deepidv currently exposes the following MCP tools.

​

Applicants

​

Verification

​

Workflows

Current workflow step IDs exposed through MCP:

• ID_VERIFICATION
• FACE_LIVENESS
• AGE_ESTIMATION
• PEP_SANCTIONS
• ADVERSE_MEDIA

​

Financial

​

Silent Screening

​

Example Prompts

Once the server is connected, prompts like these should work:

• “List my latest verification sessions.”
• “Find the applicant with email jane@example.com.”
• “Show the artifacts for verification session SESSION_ID.”
• “Create a workflow named Standard KYC with ID verification and face liveness.”
• “List my bank statement requests from the last 30 days.”
• “Run a PEP and sanctions check for Jane Doe born 1980-05-12.”
• “Queue an adverse media check for Jane Doe in the US, then poll the job.”

​

Troubleshooting

​

401 Unauthorized or invalid_token

• Re-run the OAuth flow
• Confirm the client is pointing at https://mcp.deepidv.com/v1/mcp
• If the client asks for client_id, confirm you entered deepidv
• Confirm the deepidv user and organization are active

​

The client asks for a client_secret

deepidv’s hosted MCP flow does not use a client_secret. If the client refuses to proceed without one, use a client that supports public OAuth + PKCE for remote MCP servers.

​

Redirect URI not registered or not allowed

Your MCP client may be using a redirect URI that is not currently allowed by the deepidv hosted OAuth server. Use a client with standard remote MCP OAuth support, or contact deepidv support.

​

Opening the server URL shows an auth error

That is expected. POST /v1/mcp is protected and requires a bearer token issued through OAuth. Use the docs page, mcp.json, or your client’s connector flow for discovery.

​

The client tries to install a local package or run a local server

deepidv should connect as a hosted remote MCP server and should not require a local deepidv server package for Claude Web, Claude Desktop, Claude Code, or Cursor.

​

Security Notes

• All MCP requests use bearer-token authentication
• Access is limited to the authenticated deepidv organization and user
• Tool calls are rate-limited
• State-changing tools may create records, resend applicant invites, or consume credits
• Verification artifacts and returned links should be treated as sensitive customer data

​

Related Links