Skip to main content
The hosted server at https://mcp.didit.me/mcp gives a signed-in user 169 tools: 80 read, 62 write and 27 destructive. The 17 Investigator tools are listed too, but they only work once the Investigator is enabled for your organization. Two more (didit_org_top_up and didit_org_reveal_application_api_key) are hidden from every OAuth-authenticated catalog and only appear on a local stdio server, which also adds five account-setup tools (see self-hosting). This page is generated from the tool registry in didit-protocol/mcp (src/index.ts, the version the hosted server reports in serverInfo). Names, types and required arguments come from the server’s own tools/list response; the role permission comes from src/permissions.ts.

How to read the table

Every tool accepts optional organization_id and application_id to pin a scope. With a single org and app they are resolved for you; with several, the *_search tools and didit_analytics span all of them and the per-app *_list tools do the same when you pass no scope.
didit_session_delete and didit_session_batch_delete refuse to run without confirm: true in their arguments, as do the Investigator decision tools (accept, override, batch_accept, rereview, question_answer, question_dismiss) and the local-only didit_org_reveal_application_api_key. didit_case_manage needs it when filing a SAR, and didit_vendor_user_delete and didit_vendor_business_delete need it when delete_all is true.

Discovery and cross-app

These span every organization and application you can access in a single call; each row is tagged with its org and app.

Sessions (KYC and KYB)


Workflows

Simple workflows are a flat feature list; graph workflows add branches, conditions and Document AI steps. See Advanced: branching workflows.

Compliance assistant

Build a workflow from your regulatory profile: an adaptive interview, the obligations that apply to you with citations, and a generated multi-country workflow.

Questionnaires


Standalone verification APIs

Single billable calls with no session. Every one of them is a POST that consumes credits, even the ones that read like a query (kyb_search, face_search).

Transaction monitoring


Travel Rule


Vendor users and businesses


Lists, blocklist and allowlist


Cases


Fraud networks


Investigator

These tools appear in tools/list for every signed-in user, but they only work once the Investigator is enabled for your organization.

Reports, audit log and alerts


Webhooks


Marketplace


Organization, members, billing and branding

Two tools in this group (didit_org_top_up, didit_org_reveal_application_api_key) are defined in the server but hidden from the catalog of every OAuth-authenticated caller; they are only listed on a local stdio server.

File inputs

Tools that take a file (didit_verify_id, didit_verify_poa, didit_verify_passive_liveness, didit_verify_face_match, didit_verify_face_search, didit_verify_age, didit_lists_entry_upload_face, didit_branding_update) accept it in one of two forms:
  • *_base64: the file content inline, as raw base64 or a data: URL. Use this against the hosted endpoint.
  • *_path: an absolute path on the machine running the server. Only works for a local stdio server that shares a filesystem with you.
Both forms enforce a 15 MB cap and a magic-bytes allow-list (PNG, JPG, WebP, GIF, BMP, ICO, PDF). The hosted transport accepts JSON bodies up to 25 MB.

Examples

Conversations that use these tools end to end.

Advanced

Roles, cross-app behavior, branching workflows, webhooks, self-hosting.
Last modified on October 31, 2026