MCP.Market

Veridigit MCP server

by qinisolabs·io.github.qinisolabs/veridigit·v0.1.0

Verified IBAN, card, ISBN-13 & VIN validation for AI agents — checksums, not guesses.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars34 downloads/wk

Reviews

Write one

Nobody has reviewed Veridigit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Veridigit tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • validate_card

    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.

  • validate_iban

    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.

  • validate_isbn

    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.

  • validate_vin

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 103 days ago8/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Veridigit compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
34
more than 23% of 12,191 servers with a package

What its tools let an agent do: 4 read

Install Veridigit in Claude Code, Cursor or VS Code

Runs npx -y veridigit on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add veridigit -- npx -y veridigit
Add to Cursor

What the publisher says

From the Veridigit repository's README, as published. We do not edit it. Read it on GitHub

veridigit

Verified validation of structured identifiers for AI agents — checksums, not guesses.

LLMs cheerfully accept malformed IBANs, mistype card check digits, invent ISBN and VIN check digits, and guess a card's brand wrong. veridigit gives an agent a deterministic, authoritative answer instead: it runs the real checksum algorithms and returns structured results with the parsed parts and clear error reasons.

It ships as both an MCP server (for agents to call live) and a typed TypeScript library (for apps to import).

Supported in v1:

(Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay), and length rules.

  • IBAN — ISO 7064 mod-97 checksum + country-specific length, for 75+ countries.
  • Payment cards — Luhn (ISO/IEC 7812) checksum, brand detection from the BIN
  • ISBN-13 — 978/979 prefix and mod-10 weighted check digit.
  • VIN — ISO 3779 alphabet (no I/O/Q) and the position-9 transliteration check digit.

Why

On 32 randomly generated, non-memorised identifiers, a frontier model with no tool got the check digit wrong 91% of the time — IBAN 100%, VIN 100%, ISBN-13 88%, card/Luhn 75% — versus 0% for veridigit. The failure is invisible: the model returns a confident, well-formatted answer that happens to be wrong. veridigit replaces the guess with the algorithm.

Benchmark and reproducible harness: https://qinisolabs.github.io/veridigit

The 91% figure is one frontier model, tool-free, at temperature 0. Run it on any model

yourself with the harness in bench/.

Use as an MCP server

// in your MCP client config
{
  "mcpServers": {
    "veridigit": { "command": "npx", "args": ["-y", "veridigit"] }
  }
}

Tools exposed: validateiban, validatecard, validateisbn, validatevin.

Use as a library

npm install veridigit
import { validateIban, validateCard, validateIsbn13, validateVin } from "veridigit";

validateIban("GB82 WEST 1234 5698 7654 32");
// { valid: true, countryCode: "GB", country: "United Kingdom", checkDigits: "82", ... }

validateCard("4111 1111 1111 1111");
// { valid: true, luhnValid: true, brand: "Visa", lengthValid: true, ... }

validateIsbn13("978-0-306-40615-7"); // { valid: true, type: "ISBN-13", checkDigit: "7", ... }
validateVin("1HGCM82633A004352");    // { valid: true, checkDigit: "3", ... }

Helper exports are also available: ibanCheckDigits, luhnValid, luhnCheckDigit, detectBrand, isbn13CheckDigit, vinCheckDigit, supportedIbanCountries.

Scope

veridigit validates the structure of an identifier — its format and checksum. It does not confirm that a bank account, card, book or vehicle actually exists, is active, or belongs to anyone. It performs no network calls.

Development

npm install
npm run build   # tsc -> dist/
npm test        # parity/known-answer tests via tsx

The curated reference data (IBAN country specs, card BIN ranges) lives in data/.

License

Apache-2.0

Nothing above is checked by us. What we check is on the safety report.

Veridigit: common questions

Is Veridigit MCP server safe?
Mostly: it is graded B (80/100). Read the Veridigit safety report
How do I install Veridigit?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Veridigit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Veridigit maintained?
The last commit was 142 days ago (2026-06-15). The latest release is v0.1.0.
How does Veridigit compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from qinisolabs →