mcpbeat Sign in

Check Digits MCP Server

not responding

Check Digits is listed as active in the registry but did not answer our last check. 19 installs a week from npm. It exposes 3 tools. Last commit 17 Sep 2026.

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

The author archived this repository on GitHub, meaning it is no longer maintained.

Installs per day peak 7 · avg 2 · -10% w/w
a month agotoday
Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
3
Tools
read from the server
5 ms
Response time
average over 24h
19
Installs / week
npm and PyPI

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 August 2026. No other catalogue keeps this.

11 Aug a tool changed version2 times that day
and 1 more, back to 11 August 2026

Check Digits does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add check-digits --transport http https://check-digits.toolstop.dev
Settings → Connectors → Add custom connector, then paste this address
https://check-digits.toolstop.dev
~/.codex/config.toml
[mcp_servers.check-digits]
url = "https://check-digits.toolstop.dev"
.cursor/mcp.json
{
  "mcpServers": {
    "check-digits": {
      "url": "https://check-digits.toolstop.dev"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "check-digits": {
      "type": "http",
      "url": "https://check-digits.toolstop.dev"
    }
  }
}

Available tools 3

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

compute
compute_luhn_digit
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.
identify
identify_format
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.
validate
validate_identifier
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.

Endpoints

URLTransportStateLatencyChecked
https://check-digits.toolstop.dev streamable-http answering 5 ms 13 min ago

Alternatives to Check Digits

same job, measured the same way
Dora Register Lint
by jmshinhwa

24 checks on the register CSV before it reaches the supervisor — LEI check digits, ISO dates and cod

149 installs/wk local only
S
Solwyn
by solwyn

Check budgets before AI spend, record what your code spends and read Solwyn costs.

3 042 installs/wk local only
G
GLEIF Global LEI & Corporate Entity KYB Lookup
by ceadigital

Search Global Legal Entity Identifier (GLEIF LEI) records for corporate KYB and entity verification.

28 tools answering
Veritap
by veritap

Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.

59 installs/wk 6 tools answering
Vulnify
by vulnify

Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.

72 installs/wk answering
SkanQRCode
by skanqrcode

Check whether a URL or IP is safe before an AI agent fetches or opens it.

45 installs/wk local only
X402 Checks
by 89rat

Machine-payable deterministic identifier checks + signed XDR-1 receipts for agents.

57 tools answering
ripsem
by sadykhzadeh

Offline code search for agents: find code by identifier, error message or plain description

291 installs/wk local only

Check Digits — questions

Answers built from our own checks of this server.

What can Check Digits do?
It exposes 3 tools, read directly from the server on our last check. Among them: compute_luhn_digit, identify_format, validate_identifier. 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 Check Digits working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 5 ms. The bar chart above shows every period we have measured.
Is Check Digits still maintained?
The author archived this repository on GitHub, meaning it is no longer maintained. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Check Digits as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Check Digits?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Check Digits need an API key?
No. Check Digits completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How many people use Check Digits?
The npm package @toolstop/check-digits was installed 19 times in the last week. Week over week that is -10%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Check Digits open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at check-digits.toolstop.dev, which runs on its operator's own terms.