AI Agent Integration (MCP Server)

Overview

deepidv’s hosted MCP server lets you connect any compatible AI client to your deepidv account. Once you add the server and complete OAuth, the client can call deepidv tools on behalf of the authenticated user in your organization. With this integration, you can:

List and inspect verification sessions
Retrieve verification artifacts and supporting links
Create and manage workflows with deepidv verification steps
List bank statement records and send bank statement requests

Requirements

Before you connect a client, make sure you have:

A deepidv account with an active user
An API key owned by that user
An MCP client that supports remote HTTP servers with OAuth

Server details

Setting	Value
Transport	Streamable HTTP
Server URL	`https://mcp.deepidv.com/v1/mcp`
Auth	OAuth 2.0 authorization code with PKCE
Local runtime required	No

Setup by Client

Claude Web

Use Claude’s connectors UI to add deepidv as a remote MCP server.

Open Connectors

In Claude on the web, open Settings and then Connectors.

Add a custom remote MCP server

Create a new custom MCP connector and use https://mcp.deepidv.com/v1/mcp as the server URL.

Use the full /v1/mcp path exactly as shown. Do not append any additional path after it.

Enter your deepidv credentials

If Claude requests static OAuth credentials, use:

client_id: your deepidv user ID
client_secret: any active deepidv API key owned by that same user

You can retrieve your API key from API Authentication.

Complete OAuth in the browser

Claude can discover deepidv’s OAuth metadata from the MCP server URL. Complete the browser-based approval flow when prompted.

Verify the installation

Ask Claude to list tools, list workflows, or list verification sessions.

Claude Code

Claude Code can connect directly to deepidv over remote MCP using HTTP.

claude mcp add --transport http \
  --client-id YOUR_deepidv_USER_ID --client-secret --callback-port 8787 \
  deepidv https://mcp.deepidv.com/v1/mcp

After adding the server:

Enter your active deepidv API key when Claude Code prompts for the client secret.
Run /mcp inside Claude Code.
Complete the browser-based OAuth flow.

Use callback port 8787 so the OAuth redirect matches deepidv’s hosted OAuth configuration.

Cursor

Cursor supports remote MCP servers through .cursor/mcp.json.

{
  "mcpServers": {
    "deepidv": {
      "url": "https://mcp.deepidv.com/v1/mcp",
      "auth": {
        "CLIENT_ID": "your-deepidv-user-id",
        "CLIENT_SECRET": "your-active-api-key"
      }
    }
  }
}

After saving the file, let Cursor open the OAuth flow and complete approval.

Claude Desktop

Claude Desktop can use the same connectors flow as Claude Web for a smoother setup experience.

Open Connectors

In Claude Desktop, open Settings and then Connectors.

Add a custom remote MCP server

Create a new custom MCP connector and use https://mcp.deepidv.com/v1/mcp as the server URL.

Use the full /v1/mcp path exactly as shown. Do not append any additional path after it.

Enter your deepidv credentials

If Claude Desktop requests static OAuth credentials, use:

client_id: your deepidv user ID
client_secret: any active deepidv API key owned by that same user

You can retrieve your API key from API Authentication.

Complete OAuth in the browser

Claude Desktop can discover deepidv’s OAuth metadata from the MCP server URL. Complete the browser-based approval flow when prompted.

Verify the installation

Ask Claude to list tools, list workflows, or list verification sessions.

Authentication Model

deepidv uses hosted OAuth 2.0 with PKCE for MCP access. The browser approval flow does not replace your credentials. client_id and client_secret are still required for MCP access:

client_id is your deepidv user ID
client_secret is an active deepidv API key owned by that same user

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

Available Tools

Verification

Tool	What it does
`list_verification_sessions`	List verification sessions with optional filters such as date range, workflow, or external ID.
`get_verification_session`	Retrieve the full details for a verification session.
`get_verification_session_artifacts`	Retrieve analysis data and resource links for a verification session.
`create_verification_session`	Create and send a new verification invitation.
`update_verification_session_status`	Manually mark a session as `VERIFIED` or `REJECTED`.

Workflows

Tool	What it does
`list_workflows`	List workflows available to the authenticated organization.
`get_workflow`	Retrieve one workflow and its configured steps.
`create_workflow`	Create a reusable workflow with one or more deepidv verification steps.

Current workflow step IDs exposed through MCP:

ID_VERIFICATION
FACE_LIVENESS
AGE_ESTIMATION
PEP_SANCTIONS
ADVERSE_MEDIA

Financial

Tool	What it does
`list_bank_statements`	List bank statement records for the authenticated organization.
`get_bank_statement`	Retrieve a bank statement record and statement details when available.
`list_bank_statements_by_external_id`	Retrieve bank statement records that match your external reference ID.
`create_bank_statement_request`	Create and send a new bank statement request invitation.

Example Prompts

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

“List my latest verification sessions.”
“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.”

Troubleshooting

`401 Unauthorized` or `invalid_token`

Re-run the OAuth flow
Confirm the client_id is your deepidv user ID
Confirm the API key used as client_secret belongs to that same user
Confirm the deepidv user and organization are active

Redirect URI not registered

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.

The client tries to install a local package

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
Verification artifacts and returned links should be treated as sensitive customer data

Agent Skills Repository

Browse the public repository for deepidv agent skills and MCP documentation.

MCP Server Docs

Read the public MCP server documentation and installation notes.

API Authentication

Find your API key and review how deepidv authentication works.

Support

Contact deepidv if you need help with client compatibility or credentials.

Documentation Index

​Overview

​Requirements

​Server details

​Setup by Client

​Claude Web

​Claude Code

​Cursor

​Claude Desktop

​Authentication Model

​Available Tools

​Verification

​Workflows

​Financial

​Example Prompts

​Troubleshooting

​401 Unauthorized or invalid_token

​Redirect URI not registered

​The client tries to install a local package

​Security Notes

​Related Links

Agent Skills Repository

MCP Server Docs

API Authentication

Support

Overview

Requirements

Server details

Setup by Client

Claude Web

Claude Code

Cursor

Claude Desktop

Authentication Model

Available Tools

Verification

Workflows

Financial

Example Prompts

Troubleshooting

`401 Unauthorized` or `invalid_token`

Redirect URI not registered

The client tries to install a local package

Security Notes

Related Links