# Didit MCP Server: 186 Identity Verification Tools By Leah Goldberg · 2026-11-12 · Source: https://www.activepieces.com/blog/didit-mcp-server-186-identity-verification-tools --- [Didit](https://didit.me) MCP is a Model Context Protocol server from Didit, and Didit's own changelog **places its release in June 2026**. **We didn't build it or test it**, and, much as we would with any [Activepieces](https://www.activepieces.com) write-up of a third-party tool, we are only reporting what the vendor says. Everything below comes from Didit's published pages. ![Person listening to a sealed box beside a stack of pages](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/9be3a91d-84d9-4a1b-b3b9-19883b7b3312/didit-mcp-server-186-identity-verification-tools-b51887c9.webp) ## Reviewing Didit MCP's release date ### What Didit released and when Start with the source: the maker is Didit, at [didit.me](https://didit.me). The release date comes from the company's changelog, not from a press write-up or a third-party review. That matters because a product this new has no track record outside the vendor's own account. If you're deciding whether it belongs in a workflow, the changelog tells you it exists and roughly when it arrived. It doesn't tell you how it behaves under load or what breaks. If your automation platform has no native Didit support, as with an open source platform whose 747 integrations, counted from its monorepo, include no Didit one, you wire it in from general building blocks. The canvas below shows what such a flow looks like: - a weekly schedule trigger - a Firecrawl scrape (a web-scraping service) - an AI page audit - a Google [Docs](https://docs.didit.me/getting-started/introduction) write-up, with unpublished changes pending ![A four-step workflow automation flow for SEO analysis scheduled to run every Monday at 9 am, with steps to scrape a…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/357b3c1f-fb15-485a-8f48-28babe1a6f93/no-code-web-builder-best-options-in-2026-screens-869c3989.webp) It's an unrelated SEO flow, so take the shape from it, not any claim about Didit. I read Didit's own pages on 2026-11-12. Anything stated here about what Didit MCP is, who released it, and when traces back to those pages. If Didit has changed them since, trust the pages over this article. ## Why Didit MCP matters to automation ### What the Didit MCP server does Give an AI agent a vendor MCP server and it can act inside Didit directly, so the tool list works as a permissions list. Didit's [June 2026 changelog](https://docs.didit.me/changelog/june-2026) calls this the server's biggest release yet, and its [introduction page](https://docs.didit.me/getting-started/introduction) **counts 186 tools**. The changelog names four things agents can do: - Run verifications, per the June 2026 changelog. - Screen wallets, per the same changelog. - Manage workflows, per the same changelog. - Monitor transactions, per [Didit's homepage](https://didit.me). Which group a tool sits in decides how much access you hand over. Didit's [tools page](https://docs.didit.me/integration/mcp/tools) lists 87 read tools, so a read-only grant leaves out 99 of the 186. ![A tool list sorted into three trays: a large tray of read tools, a medium tray of write tools, and a small tray of…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/1c7f7bf8-2936-4af6-800c-903f45e87bf9/didit-mcp-server-186-identity-verification-tools-d2141cfd.webp) ### Sources for Didit MCP capabilities and figures We've tested none of it. Every capability above comes from Didit's own pages. The one outside figure is the [LendingIQ](https://lendingiq.ai) onboarding funnel. **Three in four are gone before login**, so an agent that touches onboarding touches the stage where most applicants are already lost. A mis-scoped write or destructive tool costs more there than almost anywhere else. ## What is measurably new in Didit MCP Since everything measurable here comes from Didit's own pages, it matters that those pages don't fully agree: one gives an exact tool count, another says only "over" a round number. - tool count - tool split - server URL - version - free credit - KYC price - speed claim Where two pages disagree, treat the looser wording as the safer one to plan around. Where a row has no stated figure, Didit hasn't given one. This is Didit's own server, not a community wrapper: a vendor-run interface to its identity verification platform. Its tool list mixes read operations with the destructive ones you're withholding, so the split matters before any agent gets credentials. Look at the hosted server address first. Didit's pages point to it, and the table lists it with its source. Read the version row before you build on it: a young server can change tool names between releases, and a workflow that calls a renamed tool fails silently until someone checks the run log. When the free credit runs out mid-run, neither page says what happens, so cap your agent's spend before the first live test. Didit's pages state the credit and a per-check KYC price, both in the table. Its speed claim is Didit's own, untested by us. ## Connecting Didit MCP in an Activepieces workflow today To reach Didit from Activepieces you go through its general building blocks, simplest first, because there is no Didit-specific integration as of 2026-11-12. We haven't run any of them against Didit MCP. Whatever you do connect there is an agent tool the moment it exists: the integration action that runs as a flow step is the one the per-project MCP server hands to Claude, ChatGPT, Cursor or an agent you built, and the MCP Server documentation and the open source `packages/pieces` directory both bear that out. Nothing gets published or exported a second time for the agent. ### Option 1: an HTTP request step Start here. Activepieces can send an HTTP request from any flow, so you can call Didit's regular API directly, with your Didit key in the request headers. Flows are unlimited on every Activepieces plan, the free one included, and a run costs 1 credit however many steps it has, so the free plan's 1,000 credits a month cover 1,000 test runs without an upgrade. This skips MCP entirely: you handle the endpoints and payloads yourself, from Didit's API documentation. You get verification results into your flow with the least moving parts, but none of the agent-style tool access that MCP is meant to offer. ### Option 2: an AI step with a custom provider If you want a model to decide when to call Didit, an AI step can point at a custom, OpenAI-compatible provider. Be clear about what this buys you. It gives the model a place to run, not a connection to Didit's tools. Unless you add the Didit calls yourself, the model has nothing to call, so treat this as a stepping stone rather than a finished route. ### Option 3: an MCP server If you want what Didit describes, point an MCP client at `https://mcp.didit.me/mcp`. For Activepieces with MCP support, this is the only option here that reaches Didit's 186 tools through Didit's MCP endpoint itself. ![An MCP client machine connected by a single cable to a server box labelled by a URL plate, the server holding a long rack…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/62dac805-53af-4ace-83a2-28932bd1a157/didit-mcp-server-186-identity-verification-tools-40a045ff.webp) Check first that your Activepieces version lets a flow or agent connect to an MCP server, and how it passes credentials. If it doesn't, fall back to Option 1. ## Comparing Didit MCP's cost and speed Didit's speed figures are its own claims and we haven't benchmarked them; the published prices cover only cost per check. On [Didit's introduction page](https://docs.didit.me/getting-started/introduction), device and IP checks cost $0.03 each, so a high-volume signup flow can screen every attempt without the check becoming the budget line. ![Where Didit's product lines sit on price](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/352c8b6e-cbeb-437b-9918-18eb8a6b5267/didit-mcp-server-186-identity-verification-tools-e01c7f3b.svg "Source: Didit") Five times that, wallet screening is $0.15 per check, so run it only where a crypto address is actually in play. **The full KYC bundle is $0.33 per check**, which is the figure to multiply by your monthly verifications before anything else. KYB starts at $2 per check, and "from" means your business-verification volume needs a quote-level conversation, not a back-of-envelope sum. Those prices belong to Didit, not to the route you use to call it. Whether an HTTP step, an AI step or an MCP server adds run time or extra task usage on your platform is the part nobody's published. | Route | Setup effort | What Didit documents | Unverified (speed and cost in a run) | |---|---|---|---| | HTTP step | Lowest: one request per check | Per-check prices above | Latency per call; task usage per run | | AI step | Moderate: prompt plus credentials | Per-check prices above | Model fees on top; extra latency | | MCP server | Highest: server connection and tool setup | Didit's MCP is new; the pages state its capabilities | Latency, overhead per tool call, total cost | _Prices and plan limits checked against [didit.me](https://didit.me) and [docs.didit.me](https://docs.didit.me/getting-started/introduction) and [docs.didit.me](https://docs.didit.me/changelog/june-2026) and [docs.didit.me](https://docs.didit.me/academy/platform-tour) on November 12, 2026._ Only the per-check price is firm. Before committing, time ten sandbox runs through each route and compare them against your own volume, so you catch any deviation that signals a problem before it ships. ## What to watch next as Didit MCP matures Once your sandbox timings are in, recheck five public sources before you commit, because Didit MCP's new and any of them can change what you should build. Nothing here's a forecast; each is something you can open and read today. Rerun the list below on a schedule, since it shows where each claim can be confirmed or dropped: - Didit's changelog, for entries after v5.0.0 - Didit's docs, for the current tool count - didit.me/pricing, for the published figures - Your platform's public repository, for a didit integration - Your platform's integration catalog, for a Didit listing Log each check as a yes or no with a date, so a change shows up as a difference from your last note rather than a hunch. Anything dated after v5.0.0 in the changelog is where MCP changes would appear, since it is the record of release history. If the tool count in the docs moves, the actions your workflow assumes may no longer match what exists, so re-read the list before you trust a step you built earlier. A pricing change matters the same way: it can alter what a high-volume trigger costs you. Every item above sits on Didit's own pages or in public listings, and none of it comes from our testing. If a page disagrees with this article, trust the page and rerun your sandbox timings. ## Frequently asked questions If a page disagrees with any answer below, the page wins, so treat these as pointers back to Didit's own wording. ### Cost and platform support Is Didit MCP free to use? Partly. Didit's pricing page describes a monthly free credit, and usage beyond it's billed per verification. Read the current terms there before you build a workflow around the free allowance. We haven't run a bill through it, so we can't say how far the credit stretches for your volumes. Does Activepieces support Didit MCP natively? Didit's pages don't claim one. If there's no native integration, the general building blocks, such as an HTTP request step, are the honest route to try. We haven't tested that route. ### Agents and documentation Can I use Didit MCP from an AI agent today? Didit publishes an MCP server URL and sorts its tools into read, write and destructive groups. That makes it usable in principle from any agent client that speaks MCP. We haven't connected an agent ourselves, so run it first with read-only tools. Keep the destructive group switched off until you've watched what the agent actually calls. Where is the official Didit MCP documentation? On Didit's own site, in its developer documentation, with the MCP server URL and tool groups listed there. Start from Didit's site rather than a third-party summary, this article included. The feature's new, and the pages are the source that gets updated first. ## Related reading - [Gemini Agent: What Google Launched, Pricing and Limits](https://www.activepieces.com/blog/gemini-agent-what-google-launched-pricing-and-limits) - [Best Data Automation Tools of 2026 for Analytics Teams](https://www.activepieces.com/blog/best-data-automation-tools-of-2026-for-analytics-teams) - [Reverse Logistics Automation Tools for Operations Teams](https://www.activepieces.com/blog/reverse-logistics-automation-tools-for-operations-teams) ## References - [Didit docs](https://docs.didit.me/integration/mcp/tools) - [Didit](https://docs.didit.me/getting-started/introduction) - [LendingIQ](https://lendingiq.ai)