The Didit MCP Tool Reference: 130+ Identity and Fraud Tools

Didit's MCP (Model Context Protocol) server exposes 130+ tools across 11 categories, which is a lot to hold in your head. This is the map. Below, each category gets a short description, the representative tools you will actually reach for, and one natural-language prompt so you can see how an AI agent invokes them. Treat it as a reference you skim before wiring up a workflow — not a spec (the canonical, always-current tool list lives in the docs and the repo).

Key takeaways

• The server is hosted at https://mcp.didit.me/mcp (Streamable HTTP), authenticated with OAuth 2.1 + PKCE — no API key.
• Tools are grouped into 11 categories spanning the full identity and fraud lifecycle: discovery, sessions, workflows, standalone APIs, transaction monitoring, users/businesses, lists, cases, reports, webhooks, and workspace.
• Every tool respects your console role, so a Reader-scoped agent reads while an Admin-scoped agent can mutate.
• Each category below includes representative tools and a copy-ready example prompt.
• Pricing is unchanged: KYC core flow $0.33, wallet screening $0.15/check, 500 free verifications/month. The MCP layer is free.

Before you start: connect the server

For Claude Code:

claude mcp add --transport http didit https://mcp.didit.me/mcp

Then run /mcp and complete the "Log in with Didit" flow through business.didit.me. Claude Desktop uses Settings → Connectors → Add custom connector; Cursor, VS Code, Windsurf, and Zed take the same URL in JSON config; ChatGPT adds it as a connector by URL in OpenAI Developer Mode (an OpenAI beta). Full details at didit.me/developers/mcp.

1. Discovery / Cross-App

Orientation tools. Before an agent does anything, it can ask what exists in your workspace — which workflows are configured, which modules are enabled, what resources it can reach. This is what lets an agent act without you pre-listing every ID.

"What verification workflows and modules do we have configured in this workspace?"

2. Sessions (KYC / KYB)

The core of ID Verification and business verification. Tools here create a verification session against a workflow, fetch its status and decision, and pull the underlying documents, liveness, and face-match results. This is the most common entry point for onboarding flows.

"Create a KYC session for our standard onboarding workflow and give me the link to send to the applicant."

3. Workflows & Questionnaires

Drive the no-code Workflow Orchestrator. These tools list and read the workflows that define which modules run in what order, plus the custom questionnaires you attach to a flow to collect structured answers alongside the identity checks.

"List our workflows and show me which modules the 'High-Risk Onboarding' workflow runs."

4. Standalone Verification APIs

Sometimes you want a single module, not a whole session. Standalone tools call individual checks directly — face match, document OCR, AML Screening, proof of address — for cases where you already have the data and just need one verdict.

"Run an AML screening on Jane Doe, date of birth 1988-04-12, nationality Spanish, and summarize any sanctions or PEP hits."

5. Transaction Monitoring (AML)

Post-onboarding fraud coverage. These tools reach into transaction monitoring: the real-time rule engine, the seeded rule bundles, the alerts a rule raises, and the workflow around a flagged transaction. Fiat and crypto both flow through the same engine.

"Show me the open transaction-monitoring alerts from the last 24 hours and group them by rule."

6. Vendor Users & Businesses

Manage the verified people and companies already in your account. Tools here list, read, and update the user and business records — useful when an agent needs to reconcile a new session against an existing customer, or pull a UBO (Ultimate Beneficial Owner) tree for a company you have already verified.

"Find the business record for 'Acme Payments Ltd' and list its beneficial owners with their verification status."

7. Lists / Blocklist / Allowlist

The gates that sit in front of onboarding. These tools read and maintain your blocklist (deny) and allowlist (permit) entries, so an agent can check whether an identifier is already blocked or add one after a decision — always subject to your role's write permissions.

"Add this document number to our blocklist with a note that it was flagged for a forged ID."

8. Cases

Compliance case management. When a check needs human review, it becomes a case. These tools open, read, comment on, and resolve cases, letting an agent triage the queue and surface the ones that need a person.

"List unresolved cases assigned to the compliance team and summarize the reason each was opened."

9. Reports / Audit / Alerts

Oversight and evidence. These tools pull reports, read the audit trail of who did what, and fetch alerts across the account. This is how an agent produces the paper trail a regulator or an internal reviewer will ask for.

"Pull the audit log for all list changes made this week and tell me who made each change."

10. Webhooks

Wiring for downstream events. These tools register, list, and inspect webhook destinations so that when a session completes or an alert fires, your systems get notified. An agent can verify a webhook is configured before it relies on the event.

"List our webhook destinations and confirm one is subscribed to session-completion events."

11. Workspace / Billing

Account context. These tools read workspace configuration and usage — how many verifications you have run this month, what is enabled, where you stand against the free tier. Useful for an agent that needs to reason about cost or capacity before kicking off a batch.

"How many verifications have we used this month, and how many of our 500 free ones are left?"

How the categories fit together

The power is in composition. A single agent request can cross categories: discover the right workflow (1), create a KYB session (2), pull the resulting UBO records (6), run AML screening on each owner (4), add a flagged owner to the blocklist (7), open a case for review (8), and confirm a webhook will notify your team (10). Because every call runs under one OAuth session scoped to your console role, the whole chain stays inside the permissions you already granted — and secrets are redacted from what the model ever sees.

Reference, not a cage

This map covers the shape of all 130+ tools, but the authoritative, versioned list lives in the docs and the open-source (MIT) repository. Pricing stays exactly as it is across the platform — KYC core flow $0.33, wallet screening $0.15/check, AML Screening $0.20, transaction monitoring $0.02/transaction, and 500 free verifications per month with sub-2-second inference. The MCP layer that makes it all callable is free.

Read the overview at didit.me/developers/mcp, then Start free at business.didit.me — 500 free verifications every month, and connecting the MCP server costs nothing. Point your AI client at https://mcp.didit.me/mcp and start composing.