io.github.qinisolabs/veridigit
NPM · VERIDIGIT · SCANNED SEP 20
Verified IBAN, card, ISBN-13 & VIN validation for AI agents — checksums, not guesses.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 96 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 359 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.qinisolabs/veridigit MCP server?
io.github.qinisolabs/veridigit runs locally as an npm package, launched with npx -y veridigit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · veridigit
claude mcp add qinisolabs-veridigit -- npx -y veridigit
{
"mcpServers": {
"qinisolabs-veridigit": {
"command": "npx",
"args": [
"-y",
"veridigit"
]
}
}
} {
"servers": {
"qinisolabs-veridigit": {
"command": "npx",
"args": [
"-y",
"veridigit"
]
}
}
} codex mcp add qinisolabs-veridigit -- npx -y veridigit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qinisolabs-veridigit": {
"type": "local",
"command": [
"npx",
"-y",
"veridigit"
],
"enabled": true
}
}
} openclaw mcp add qinisolabs-veridigit --command npx --arg -y --arg veridigit
mcp_servers:
qinisolabs-veridigit:
command: "npx"
args: ["-y", "veridigit"] {
"McpServers": {
"qinisolabs-veridigit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"veridigit"
]
}
}
} assistant mcp add qinisolabs-veridigit -t stdio -c npx -a -y veridigit
{
"mcpServers": {
"qinisolabs-veridigit": {
"command": "npx",
"args": [
"-y",
"veridigit"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/veridigit@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
validate_card ~103
USE THIS to check a payment card number's structure before using it — never assume a card number is valid or guess its brand. Verifies the Luhn checksum, detects the brand (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay) from its BIN, and checks the length. Does NOT check whether the card is real, active or has funds.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The card number; spaces and dashes are ignored. |
No output schema declared.
No examples provided.
validate_iban ~99
USE THIS to verify an IBAN (international bank account number) before relying on it — instead of guessing whether it looks right. Checks the country, the country-specific length, and the ISO 7064 mod-97 checksum, and returns the country, check digits and BBAN. Call this whenever a user supplies a bank account for a payment, payout or invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | The IBAN to validate; spaces are ignored. |
No output schema declared.
No examples provided.
validate_isbn ~74
USE THIS to verify an ISBN-13 book identifier instead of trusting that 13 digits are correct. Checks the 978/979 prefix and the mod-10 weighted check digit, and returns the expected check digit when it fails.
| Name | Type | Req | Description |
|---|---|---|---|
| isbn | string | yes | The ISBN-13; hyphens and spaces are ignored. |
No output schema declared.
No examples provided.
validate_vin ~83
USE THIS to verify a vehicle VIN before acting on it — do not assume a 17-character string is a valid VIN. Checks the allowed alphabet (no I/O/Q) and the ISO 3779 transliteration check digit in position 9, and returns the expected check digit when it fails.
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | The 17-character VIN to validate. |
No output schema declared.
No examples provided.
What is the io.github.qinisolabs/veridigit MCP server?
io.github.qinisolabs/veridigit is an MCP server listed in the public MCP registry as io.github.qinisolabs/veridigit. Verified IBAN, card, ISBN-13 & VIN validation for AI agents, checksums, not guesses. This page covers its npm package (veridigit).
Is the io.github.qinisolabs/veridigit MCP server safe to use?
io.github.qinisolabs/veridigit scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.qinisolabs/veridigit MCP server expose?
io.github.qinisolabs/veridigit exposes 4 tools: validate_iban, validate_card, validate_isbn, validate_vin. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.
Is the io.github.qinisolabs/veridigit MCP server still maintained?
io.github.qinisolabs/veridigit is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.qinisolabs/veridigit MCP server under?
io.github.qinisolabs/veridigit declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.