Checksum Validator MCP Server

by apished Your server? Claim it

answering

Checksum Validator is answering right now. Last checked 15 min ago. It exposes 6 tools.

Validates Luhn, IBAN, ISBN, EAN/UPC, SWIFT/BIC, and EU VAT checksums and formats.

Uptime history 14 days of history

14 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

182 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Checksum Validator every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add checksum-validator --transport http https://apished.com/mcp/v1/checksum

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "checksum-validator": {
      "url": "https://apished.com/mcp/v1/checksum"
    }
  }
}

~/.codex/config.toml

[mcp_servers.checksum-validator]
url = "https://apished.com/mcp/v1/checksum"

.cursor/mcp.json

{
  "mcpServers": {
    "checksum-validator": {
      "url": "https://apished.com/mcp/v1/checksum"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "checksum-validator": {
      "url": "https://apished.com/mcp/v1/checksum"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ean

ean_validate

Validates an 8-digit (EAN-8), 12-digit (UPC-A), 13-digit (EAN-13), or 14-digit (GTIN-14) barcode checksum: alternating weights 1 3 applied right-to-left, check digit is (10 - sum mod 10) mod 10.

iban

iban_validate

Validates an IBAN's length for its issuing country (per the SWIFT IBAN registry) and its mod-97 checksum. Does not decompose the BBAN into a bank code/account number or resolve a BIC.

isbn

isbn_validate

Validates a 10- or 13-character ISBN. ISBN-10 uses weights 10..1 over 10 characters (last may be X, worth 10), sum mod 11 must be 0. ISBN-13 uses the same GTIN checksum as barcodes.

luhn

luhn_validate

Validates a numeric string against the Luhn (mod-10) checksum — payment card numbers, IMEI numbers, and similar identifiers.

swiftbic

swiftbic_validate

Structural format validation only for a SWIFT/BIC code: 8 or 11 characters (4 letters bank code + 2 letters country code + 2 alphanumeric location code + optional 3 alphanumeric branch code). The country code is not cross-checked against ISO 3166-1.

vateu

vateu_validate

Format validation only (no VIES lookup) for an EU VAT number: checks the 2-letter member-state prefix (EL for Greece, XI for Northern Ireland) against that country's digit/letter pattern. A format-valid result does not mean the number is actually registered.

Endpoints

URL	Transport	State	Latency	Checked
https://apished.com/mcp/v1/checksum	streamable-http	answering	201 ms	15 min ago

Alternatives to Checksum Validator

same job, measured the same way

APIShed

by apished

Validates PESEL/NIP/REGON/IBAN/Luhn/ISBN/EAN/SWIFT-BIC/VAT; RPN calc, date math, hashing, tokens

29 tools answering

Ibanchecker MCP

by koraykoylu

IBAN validation, extraction, format specs and BIC/SWIFT lookup tools for AI assistants.

79 installs/wk 5 tools answering

Veridigit

by qinisolabs

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

50 installs/wk local only

IBAN Validator

by peonixo147

Validate IBAN bank account numbers (format + mod-97 checksum). Returns whether the IBAN is valid.

1 tools answering

Vatnode MCP

by vatnode

Official MCP server: EU VAT validation via VIES, plus offline rates and format checks.

80 installs/wk local only

Openiban

by pipeworx-io

OpenIBAN MCP — validate an IBAN's checksum + bank code and resolve the

33 tools answering

IBAN Validation MCP

by iban-test-www

Validate IBANs in 111 countries; bank directory checks for DE, AT, BE, FR, LU, NL, PT and ES.

4 tools answering

PESEL/NIP/REGON Validator

by apished

Validates Polish PESEL, NIP, and REGON checksums; PESEL also decodes birth date and sex.

3 tools answering

Checksum Validator — questions

Answers built from our own checks of this server.

What can Checksum Validator do?

It exposes 6 tools, read directly from the server on our last check. Among them: ean_validate, iban_validate, isbn_validate, luhn_validate, swiftbic_validate, vateu_validate. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Checksum Validator working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 182 ms. The bar chart above shows every period we have measured.

How do I connect Checksum Validator?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Checksum Validator need an API key?

No. Checksum Validator completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Checksum Validator?

It answers our handshake in 182 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.