Skip to content
BEAD

Luhn Check (Credit Card Validator)

Validate any number with the Luhn algorithm and detect common card brands by IIN range.

DeveloperMath

🔒 Numbers are checked locally. We don't store, log, or transmit them.

</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/luhn-validator/run \
  -H "Content-Type: application/json" \
  -d '{
  "input": "your input here"
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/luhn-validator/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "input": "your input here"
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_luhn_validator

Full reference: developer docs · OpenAPI spec

The Luhn algorithm

Patented in 1960 by IBM's Hans Peter Luhn, the Luhn algorithm (a.k.a. modulo 10 check) is the simple checksum baked into credit cards, IMEI numbers, US national-provider IDs, Canadian SINs, and a long list of other identifiers.

It only catches single-digit typos and most transpositions. It's a not-a-typocheck, not a fraud check — don't treat a valid Luhn as proof the number belongs to anyone.

Privacy:this tool runs locally. Numbers you type never leave the browser. Still, don't paste real card numbers into random web tools as a habit.

You might also like