Didit Protocol MCP Server

@didit-protocol/mcp-server npm v4.0.0

Published by @didit-protocol — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Didit MCP Server - AI agent integration for identity verification APIs

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([didit_get_import_template]) co-exist with external-action tools ([didit_list_webhook_destinations, didit_create_webhook_destination, didit_get_webhook_destination, didit_update_webhook_destination, didit_delete_webhook_destination, didit_kyb_search, didit_phone_send]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [didit_get_import_template] → sinks [didit_list_webhook_destinations, didit_create_webhook_destination, didit_get_webhook_destination, didit_update_we

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow didit_get_import_template → didit_list_webhook_destinations

medium Unconstrained URL/host parameter "url" on "didit_create_webhook_destination"MTC-CAP-007

Tool "didit_create_webhook_destination" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool didit_create_webhook_destination · inputSchema.properties.url

medium Unconstrained URL/host parameter "url" on "didit_update_webhook_destination"MTC-CAP-007

Tool "didit_update_webhook_destination" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool didit_update_webhook_destination · inputSchema.properties.url

medium Unconstrained URL/host parameter "webhook_url" on "didit_kyb_search"MTC-CAP-007

Tool "didit_kyb_search" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool didit_kyb_search · inputSchema.properties.webhook_url

Tools 82

Each tool and what it can reach — statically extracted from the published source.

  • didit_create_webhook_destinationnetwork egress
  • didit_delete_webhook_destinationnetwork egress
  • didit_get_import_templateingests untrusted input
  • didit_get_webhook_destinationnetwork egress
  • didit_kyb_searchnetwork egress
  • didit_list_webhook_destinationsnetwork egress
  • didit_phone_sendnetwork egress
  • didit_update_webhook_destinationnetwork egress
  • didit_add_session_reviewno sensitive capability
  • didit_age_estimationno sensitive capability
Show 72 more tools ↓
  • didit_aml_screeningno sensitive capability
  • didit_batch_delete_sessionsno sensitive capability
  • didit_create_businessno sensitive capability
  • didit_create_importno sensitive capability
  • didit_create_listno sensitive capability
  • didit_create_list_entryno sensitive capability
  • didit_create_questionnaireno sensitive capability
  • didit_create_sessionno sensitive capability
  • didit_create_transactionno sensitive capability
  • didit_create_userno sensitive capability
  • didit_create_workflowno sensitive capability
  • didit_database_validationno sensitive capability
  • didit_delete_businessesno sensitive capability
  • didit_delete_listno sensitive capability
  • didit_delete_list_entryno sensitive capability
  • didit_delete_questionnaireno sensitive capability
  • didit_delete_sessionno sensitive capability
  • didit_delete_usersno sensitive capability
  • didit_delete_workflowno sensitive capability
  • didit_email_checkno sensitive capability
  • didit_email_sendno sensitive capability
  • didit_face_matchno sensitive capability
  • didit_face_searchno sensitive capability
  • didit_generate_session_pdfno sensitive capability
  • didit_get_applicationno sensitive capability
  • didit_get_balanceno sensitive capability
  • didit_get_businessno sensitive capability
  • didit_get_customizationno sensitive capability
  • didit_get_importno sensitive capability
  • didit_get_import_errorsno sensitive capability
  • didit_get_listno sensitive capability
  • didit_get_questionnaireno sensitive capability
  • didit_get_session_decisionno sensitive capability
  • didit_get_transactionno sensitive capability
  • didit_get_userno sensitive capability
  • didit_get_workflowno sensitive capability
  • didit_id_verificationno sensitive capability
  • didit_import_shared_sessionno sensitive capability
  • didit_kyb_selectno sensitive capability
  • didit_list_applicationsno sensitive capability
  • didit_list_businessesno sensitive capability
  • didit_list_entriesno sensitive capability
  • didit_list_listsno sensitive capability
  • didit_list_organizationsno sensitive capability
  • didit_list_questionnairesno sensitive capability
  • didit_list_session_reviewsno sensitive capability
  • didit_list_sessionsno sensitive capability
  • didit_list_transactionsno sensitive capability
  • didit_list_usersno sensitive capability
  • didit_list_workflowsno sensitive capability
  • didit_loginno sensitive capability
  • didit_passive_livenessno sensitive capability
  • didit_phone_checkno sensitive capability
  • didit_poa_verificationno sensitive capability
  • didit_registerno sensitive capability
  • didit_resend_otpno sensitive capability
  • didit_screen_walletno sensitive capability
  • didit_share_sessionno sensitive capability
  • didit_top_upno sensitive capability
  • didit_update_businessno sensitive capability
  • didit_update_business_statusno sensitive capability
  • didit_update_customizationno sensitive capability
  • didit_update_listno sensitive capability
  • didit_update_questionnaireno sensitive capability
  • didit_update_session_datano sensitive capability
  • didit_update_session_poa_datano sensitive capability
  • didit_update_session_statusno sensitive capability
  • didit_update_userno sensitive capability
  • didit_update_user_statusno sensitive capability
  • didit_update_workflowno sensitive capability
  • didit_upload_face_entryno sensitive capability
  • didit_verify_emailno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v4.0.0 latest A 95/100 4 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/didit-protocol-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/didit-protocol-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/didit-protocol-mcp-server"><img src="https://mcptrustchecker.com/registry/didit-protocol-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/didit-protocol-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @didit-protocol/mcp-server --online

Use the free API → How scoring works

More in Security & Testing