CheckDigit MCP server
dev.workers.mike-tusa.checkdigit/checkdigitcheckdigit.mike-tusa.workers.devstreamable-httpv0.2.1Scanned
Offline check-digit validation for IBAN, BIC, EU VAT, GTIN/EAN/UPC and ISBN. Format check only.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CheckDigit MCP server can do
The CheckDigit MCP server is published by checkdigit.mike-tusa.workers.dev, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: validate_code), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 0.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
validate_codeCheck the format and check digits of one identifier: IBAN (ISO 13616, per-country length and layout), BIC/SWIFT (ISO 9362 format and country), EU VAT number (offline checksum, VIES…1 finding
Why it is in this group
- The name "validate_code" says "validate": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "validate_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "validate_code" says "validate": a word for reading.
Description, as the server wrote it Check the format and check digits of one identifier: IBAN (ISO 13616, per-country length and layout), BIC/SWIFT (ISO 9362 format and country), EU VAT number (offline checksum, VIES not queried), GTIN/EAN-8/UPC-A/EAN-13/GTIN-14 (GS1 mod 10) or ISBN-10/13. type "auto" (default) detects the type from the shape. Returns valid, a reason when invalid (e.g. the expected check digit), and normalized/formatted forms. Format check, not a compliance check: valid does not mean the account, registration or product exists. The code is sent in a POST body and not stored or logged. Read-only. Same engine, keys and limits as POST /v1/{type}.
Annotations the server declares
- title: Validate code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_metaReturn the service version and build, supported IBAN and VAT countries, GTIN formats, the disclaimer and the current limits.No findings
Why it is in this group
- The name "get_meta" says "get": a word for reading.
Description, as the server wrote it Return the service version and build, supported IBAN and VAT countries, GTIN formats, the disclaimer and the current limits. Does not count as a check. Read-only. Same data as GET /v1/meta.
Annotations the server declares
- title: Service info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://checkdigit.mike-tusa.workers.dev/mcp: tools/list returned 2 tools to an anonymous client, including validate_code (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnvalidate_code
The server marks "validate_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "validate_code" says "validate": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http checkdigit https://checkdigit.mike-tusa.workers.dev/mcpclaude mcp add --transport http checkdigit https://checkdigit.mike-tusa.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__checkdigit__get_meta"
],
"ask": [
"mcp__checkdigit__validate_code"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as checkdigit. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.mike-tusa.checkdigit/checkdigit/verify?hash=7b3192877f24074b6222845240839cfc88ec2700596f3ac882a3a0fa796264c2" | jq -e '.changed == false'Pinned hash 7b3192877f24, from Nov 17, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.mike-tusa.checkdigit/checkdigit/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.mike-tusa.checkdigit/checkdigit)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
CheckDigit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CheckDigit MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CheckDigit MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CheckDigit MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CheckDigit MCP server have?
- 2 tools: 1 write, 1 read. validate_code and get_meta.
Does the CheckDigit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CheckDigit MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CheckDigit MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.