Home / Companies / Didit / Blog / Post Details
Content Deep Dive

The identity verification MCP server for Claude

Blog post from Didit

Aggregate trend data notice

Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.

Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.

This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.

Post Details
Company
Date Published
Author
Didit
Word Count
1,756
Company Posts That Month
43
Language
English
Hacker News Points
-
Post removed?
No
Summary

Didit’s identity verification MCP server connects Claude to real, typed identity and fraud operations rather than allowing the model to invent verification outcomes, enabling tasks such as creating verification sessions, retrieving decisions, conducting AML and KYB checks, managing cases, configuring workflows, and screening transactions. Its hosted endpoint uses stateless Streamable HTTP and OAuth 2.1 with PKCE and Dynamic Client Registration, operates as the signed-in user under existing Didit organization roles, and does not support API-key authentication. The server provides 115 hosted tools across 19 domains, with role enforcement, input validation, annotations for read, write, and destructive actions, credential redaction, and sanitized error responses, although teams should implement their own human approval controls for consequential actions and note a schema gap affecting wildcard deletion confirmation. Image-based tools require files on the MCP server’s filesystem and therefore are generally unsuitable for images uploaded directly to hosted Claude; hosted applicant verification should instead use a created Didit session and its hosted capture link. The connector is intended for authorized users coordinating bounded work in an existing Didit workspace, while deterministic application integrations should use Didit’s REST APIs or SDKs; the MCP connection is free, with standard verification pricing including a $0.33 full KYC bundle and monthly free-use allowances.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
MCP 30 8,729 854 211 -20%
LLM 1 5,068 1,020 229 -34%
Secrets Management 1 2,244 480 132 -13%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.