Didit
NPM · @PIPEWORX/MCP-DIDIT · 2 COMPONENTS
Didit MCP — wraps the Didit v3 identity / compliance API (didit.me)
Available components
Last scanned (8 hours ago)
Scores higher than 68% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-didit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 618 tokens (~309/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-didit@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-didit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-didit/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617513211 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e0c6cf3cc58b9bacb25c0964fe767edb07926d42ba51bc20bff57db7b1e75ff6e8bffbabb2ded1e6376bfa44095f09f1b1c62413c66e8e445737e62c6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
didit_aml ~299
Screen a person (or entity) against 1,300+ global sanctions, PEP, watchlist, and adverse-media lists using the Didit AML API. Returns an overall status + risk score plus each individual hit (sanctions/PEP/adverse-media matches). Example: didit_aml({ full_name: "Vladimir Putin", date_of_birth: "1952-10-07", nationality: "RU", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Didit API key. Get one at https://didit.me/pricing (docs: https://docs.didit.me/). |
| date_of_birth | string | – | Optional date of birth in YYYY-MM-DD format, e.g. "1972-02-29". Improves match precision. |
| document_number | string | – | Optional government ID / document number for higher-confidence matching. |
| entity_type | string | – | Optional: "person" (default) or "company". |
| full_name | string | yes | Full name of the person or entity to screen, e.g. "Antonio Ejemplo Modelo" |
| include_adverse_media | boolean | – | Include adverse-media screening. Adds ~10s to the request. Default false. |
| nationality | string | – | Optional ISO 3166-1 alpha-2 country/nationality code, e.g. "ES", "US". Also accepted as `country`. |
No output schema declared.
No examples provided.
didit_kyb ~266
Business (KYB) verification via the Didit company registry. Given a company name (+ country), returns the matched company profile (registration number, status, address, incorporation date) plus officers/directors and UBO/beneficial-owner ownership. Resolves the free registry search then pulls the full billable profile in one call. Example: didit_kyb({ name: "Stripe Inc", country: "US", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Didit API key. Get one at https://didit.me/pricing (docs: https://docs.didit.me/). |
| company_id | string | – | Optional: the candidate company_id to select when a kyb_response_id is provided. |
| country | string | – | ISO 3166-1 alpha-2 country code the company is registered in, e.g. "US", "GB", "ES". |
| kyb_response_id | string | – | Optional: a kyb_response_id from a prior search to skip re-searching. |
| name | string | – | Company name to look up, e.g. "Stripe Inc". Also accepted as `company_name`. |
| registration_number | string | – | Optional company registration number to disambiguate. |
No output schema declared.
No examples provided.
How do I install the Didit MCP server?
Didit runs locally as an npm package, launched with npx -y @pipeworx/mcp-didit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-didit
claude mcp add pipeworx-io-didit -- npx -y @pipeworx/mcp-didit
What is the Didit MCP server?
Didit is an MCP server listed in the public MCP registry as io.github.pipeworx-io/didit. Didit MCP, wraps the Didit v3 identity / compliance API (didit.me). This page covers its npm package (@pipeworx/mcp-didit).
Is the Didit MCP server safe to use?
Didit scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Didit MCP server expose?
Didit exposes 2 tools: didit_aml, didit_kyb. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Is the Didit MCP server still maintained?
Didit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Didit MCP server under?
Didit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.