Screening, verification sessions, workflows and bank statements normally live in four different corners of a KYC console, and here they answer to the same connection — which is what makes an applicant question answerable in one pass rather than four. Worth knowing before you wire it up: a good half of these tools write. They create records, resend invitations to real people and consume credits, and adverse-media screening comes back as a job you have to poll rather than an answer.
A hosted MCP server for DeepIDV, an identity-verification platform. There is nothing to clone or build — you add `https://mcp.deepidv.com/v1/mcp` as a remote server, sign in through the browser, and the connection is scoped to the DeepIDV organization behind that account.
- Verification sessions end to end: list them with filters, open one in full, read its artifacts and resource links, follow its timeline, create and send a new invitation, mark a session `VERIFIED` or `REJECTED` by hand, or expire it — `list_verification_sessions`, `get_verification_session`, `get_verification_session_artifacts`, `get_session_timeline`, `create_verification_session`, `update_verification_session_status`, `expire_session`
- Applicant lookup across sessions and bank-statement requests, with a consolidated profile and history, plus invitation delivery status and a resend — `search_applicants`, `get_applicant`, `get_invitation_status`, `resend_invitation`
- Reusable workflows built from DeepIDV steps — the step IDs exposed here are `ID_VERIFICATION`, `FACE_LIVENESS`, `AGE_ESTIMATION`, `PEP_SANCTIONS` and `ADVERSE_MEDIA` — `list_workflows`, `get_workflow`, `create_workflow`
- Bank-statement records for the organization, one record with its statement detail, records matched to your own external reference ID, and a new statement request sent to an applicant — `list_bank_statements`, `get_bank_statement`, `list_bank_statements_by_external_id`, `create_bank_statement_request`
- Screening runs: PEP and sanctions and property-title checks return synchronously, adverse media is queued and returns a `job_id` you poll — `run_pep_sanctions_check`, `run_title_check`, `run_adverse_media_check`, `get_async_job`
- Aggregated metrics and trends for verification sessions and for bank statements — `get_session_stats`, `get_bank_statement_stats`
A DeepIDV account with an active user, and your DeepIDV email and password — plus MFA when the account enforces it. Authorization is hosted OAuth 2.0 with PKCE using `S256` against a shared public client: the `client_id` is `deepidv` and no `client_secret` is used. Your MCP client has to support remote HTTP servers with OAuth discovery; most will pick up the metadata from the server URL alone. Requests carry a bearer token and are rate-limited.