Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Check Digits

NPM · @TOOLSTOP/CHECK-DIGITS · 2 COMPONENTS · SCANNED AUG 13

Catch a mistyped barcode, ISBN, VIN, NPI or LEI before a bad identifier corrupts a record.

78 Trust /100
Trust breakdown (6 categories)

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 →

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 toolstop/toolstop). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 920 tokens (~306/item across 3 items; 3 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 Management17
  • Stability observed for 5 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @toolstop/check-digits

# add to Claude Code
claude mcp add dev-toolstop-check-digits -- npx -y @toolstop/check-digits
# add to Codex CLI
codex mcp add dev-toolstop-check-digits -- npx -y @toolstop/check-digits
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-toolstop-check-digits": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@toolstop/check-digits"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-toolstop-check-digits --command npx --arg -y --arg @toolstop/check-digits
# ~/.hermes/config.yaml
mcp_servers:
  dev-toolstop-check-digits:
    command: "npx"
    args: ["-y", "@toolstop/check-digits"]
// mcp.json
{
  "mcpServers": {
    "dev-toolstop-check-digits": {
      "command": "npx",
      "args": [
        "-y",
        "@toolstop/check-digits"
      ]
    }
  }
}
Changelog

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.

  • 12 Aug 26 +15
    • Malware scan: unverified → pass security
  • 11 Aug 26 −12
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 75

    First indexed and scored.

Diagnostics

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 12 Aug 2026 · Analysed npm/@toolstop/check-digits@0.2.2

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 toolstop/toolstop
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/toolstop/toolstop/.github/workflows/deploy.yml@refs/heads/main
Rekor log index 2416142845
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:47d4c4f985161bedc19aed51eb622d4c0de2db1789581a801ee6a39a69ae2cc605c903d7b83cd8d36d5cedca17a4774a8b68557e04c0504e491e7701a
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools · 3 exposed · ~584 tokens

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.

Tool Tokens
compute_luhn_digit ~169

Given digits with the final check digit omitted, return the one that completes them. US healthcare NPIs and securities ISINs use the Luhn formula. Use it to build valid test fixtures, to recover a last digit that was lost or illegible, or to check an implementation against a reference. To test a number you already have in full, use validate_identifier instead. Input must reduce to digits only once spaces and dashes are stripped; anything else is an error. Payment cards also use Luhn, and are deliberately out of scope here: do not pass card digits, partial or complete. This constructs a well-formed number and nothing more: it does not create, reserve or verify a real provider or security.

NameTypeReqDescription
partialstringyesDigits excluding the final check digit.
NameTypeReqDescription
checkDigitstringyesThe single digit that completes a Luhn-valid string.
partialstringyesThe input digits, echoed back.

No examples provided.

identify_format ~169

Identify a bare number whose type was never recorded. Tests it against every supported format and reports which ones its check digit satisfies. Use it for an unlabeled spreadsheet column, a value pulled out of a log line or a scanned document, or any number handed over without being named. Reports every format that matches rather than choosing between them. Several matches is normal and does not mean the answer is unclear: some formats are subsets of others, so every ISBN-13 is also a valid EAN-13, and a short value can satisfy two unrelated formats by chance. Read one match as strong evidence and several as a set to narrow from context. As with validation, a match means the arithmetic is consistent, not that the identifier is registered or real.

NameTypeReqDescription
valuestringyesThe identifier to classify.
NameTypeReqDescription
inputstringyesThe normalized input that was tested.
matchedbooleanyesWhether any supported format matched.
matchesarrayyesEvery format whose check digit the input satisfies, in registry order. Each entry carries `kind` plus the same format-specific fields validate_identifier returns for that format, such as `country` fo…

No examples provided.

validate_identifier ~246

Verify a number when you already know what it is supposed to be. Use this whenever someone gives you a product barcode (GTIN, UPC or EAN), a book number (ISBN-10 or ISBN-13), a vehicle VIN, a US healthcare provider NPI, a security ISIN, or a legal entity LEI, and acting on a wrong one would cost something: a bounced claim, a rejected listing, a record that quietly corrupts a dataset. Every supported format is a public identifier. Bank accounts, IBANs, routing numbers and payment cards are not supported and must not be sent. Returns whether the checksum passes and, when it fails, the specific reason. If you do not already know the format, call identify_format first rather than guessing a `kind`, since a valid identifier checked against the wrong format comes back invalid. A passing checksum proves only that the digits are internally consistent: it does not mean the book, product, vehicle or provider exists, is active, or belongs to any particular person.

NameTypeReqDescription
kindstringyesWhich identifier format to validate against.
valuestringyesThe identifier to check. Spaces and dashes are ignored.
NameTypeReqDescription
actualCheckDigitstringThe digit the VIN actually carries at position 9. VIN only.
codestringBounded reason the check failed. Absent when valid.
countrystringISO country code parsed from the identifier. ISIN only.
expectedCheckDigitstringThe digit a VIN should carry at position 9. VIN only.
normalizedstringThe input with spaces and dashes removed, upper-cased.
reasonstringHuman-readable detail on the failure. Absent when valid.
validbooleanyesWhether the check digit is arithmetically consistent.
widthstringThe resolved width of a GTIN. GTIN input only.

No examples provided.