Check Digit Validator

Validates IBAN/ISBN/EAN/Luhn checksums and finds the one wrong digit

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
100%
命名品質
100%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~649Token(工具定義)
~1.9 KB典型回應大小
中等的注意力影響(128k 上下文的 0.51%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "check-digit": {
      "url": "https://check-digit.gumballtools.com/api/mcp"
    }
  }
}

遠端端點

https://check-digit.gumballtools.com/api/mcpstreamable-http

它能做什麼

工具清單

工具(1)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢run(input, format)

Validate the check digit(s) on an IBAN, ISBN-10, ISBN-13, EAN-13, UPC-A, or Luhn-checked card number, and when it fails, try to say which digit is wrong. Use this instead of computing the checksum yourself. Mod-97 arithmetic on a rearranged 15-34 character IBAN, or a weighted sum mod 10/11 over 10-19 digits, is exactly the kind of long deterministic calculation language models get wrong silently and confidently — there is no way for a reader to tell a fabricated "valid" from a real one without redoing the math. This tool actually redoes the math, and when the checksum fails, searches for the single adjacent-digit swap or single-character substitution that would repair it, because a transposed pair is the most common real cause of a bounced payment or a mistyped barcode. IMPORTANT, and easy to get wrong: for ISBN-13/EAN-13/UPC-A and Luhn, the digit alphabet (0-9) almost exactly spans the checksum's modulus, so a failing check usually admits MANY equally valid single-digit substitutions — the math genuinely cannot narrow it to one digit unless the error was an adjacent transposition. When that happens, the response reports the full candidate list rather than picking one; treat that as the honest answer, not a failure to find it. IBAN (mod 97) is the exception and usually does localize to one digit. Inputs: `input` (the number; spaces and hyphens are stripped automatically) and `format`, one of iban | isbn10 | isbn13 | ean13 | upca | luhn — required, never auto-detected, because the same digit string can be validly checked under more than one format with different results. Refuses rather than guesses: an IBAN country code not in the ISO 13616 length registry, the wrong length for a declared format, or characters outside the format's alphabet (e.g. a letter in a card number). A passing checksum is a syntax check only — it does not confirm an IBAN names an open account, an ISBN is a real book, or a card is active or unstolen.

輸入結構描述

{
  "type": "object",
  "properties": {
    "input": {
      "type": "string",
      "description": "The number to check, e.g. \"DE89370400440532013000\". Spaces and hyphens are stripped automatically; anything else must match the declared format exactly."
    },
    "format": {
      "type": "string",
      "enum": [
        "iban",
        "isbn10",
        "isbn13",
        "ean13",
        "upca",
        "luhn"
      ],
      "description": "Which checksum to apply — one of: iban, isbn10, isbn13, ean13, upca, luhn. Required; a bare number is not auto-detected because the same digits can be validly checked under more than one format with different results."
    }
  },
  "required": [
    "input",
    "format"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本1 個工具
已驗證未記錄版本1 個工具