Skip to main content
The Didit MCP exposes 115 tools over the hosted OAuth endpoint (121 in the full self-hosted catalogue). Each calls a single Didit REST endpoint and returns the JSON response verbatim, so anything in the verification API or auth API is reachable from a prompt. Tools are typed so your client can group and gate them:
The didit_verify_* standalone tools are billable POST actions — they consume credits even though some read like a query (e.g. face_search, kyb_search).

Discovery & cross-app

Start here. These span every organization and application you can access in a single call, each result tagged with its org/app.

Sessions (KYC & KYB)

Bulk import

Workflows & questionnaires

Branching / graph workflows — for conditional routing, Document-AI steps, and decline/decision nodes (see Advanced → Branching workflows):

Verification APIs (standalone)

No session required — single billable calls. Great for one-off checks and pipelines.

Transaction monitoring (AML)


Travel Rule

The FATF / EU TFR managed exchange: settings, the VASP directory, the wallet address book, transfer actions, and wallet-ownership proofs.

Marketplace


Vendor users & businesses


Lists, blocklist & allowlist


Cases (investigations)


Reports, audit & alerts


Webhooks


Workspace: account, organization & billing

The didit_account_* tools are available only on the local stdio server (npx @didit-protocol/mcp-server), where they bootstrap your first credentials. The hosted connector authenticates with OAuth, so it never asks for account credentials in the conversation and does not expose these four tools.

Examples

Prompts and end-to-end conversations.

Advanced

Scopes, cross-app behavior, response shape, webhooks.