Checksum Validator
REMOTE · APISHED.COM · SCANNED OCT 4
Validates Luhn, IBAN, ISBN, EAN/UPC, SWIFT/BIC, and EU VAT checksums and formats.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 436 tokens (~72/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Checksum Validator MCP server?
Checksum Validator is a hosted endpoint at https://apished.com/mcp/v1/checksum, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apished.com
claude mcp add --transport http com-apished-checksum-validator 'https://apished.com/mcp/v1/checksum'
{
"mcpServers": {
"com-apished-checksum-validator": {
"url": "https://apished.com/mcp/v1/checksum"
}
}
} {
"servers": {
"com-apished-checksum-validator": {
"type": "http",
"url": "https://apished.com/mcp/v1/checksum"
}
}
} [mcp_servers.com-apished-checksum-validator] url = "https://apished.com/mcp/v1/checksum"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-apished-checksum-validator": {
"type": "remote",
"url": "https://apished.com/mcp/v1/checksum",
"enabled": true
}
}
} openclaw mcp add com-apished-checksum-validator --url 'https://apished.com/mcp/v1/checksum' --transport streamable-http
mcp_servers:
com-apished-checksum-validator:
url: "https://apished.com/mcp/v1/checksum" {
"McpServers": {
"com-apished-checksum-validator": {
"Transport": "http",
"Url": "https://apished.com/mcp/v1/checksum"
}
}
} assistant mcp add com-apished-checksum-validator -t streamable-http -u 'https://apished.com/mcp/v1/checksum'
{
"mcpServers": {
"com-apished-checksum-validator": {
"type": "http",
"url": "https://apished.com/mcp/v1/checksum"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://apished.com/mcp/v1/checksum
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apished.com | CN=YR2,O=Let's Encrypt,C=US | 17 Aug 2026 | 15 Nov 2026 | RSA 4096 | SHA256-RSA | 5f4dfa5fcafb280b9204690908ddbca6b5c |
| SANs: apished.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of apished.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| apished.com. | present | 38629 | 8 | Verified |
| apished.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apished.com/mcp/v1/checksum | Verified | 200 | |
| http (plaintext) | http://apished.com/mcp/v1/checksum | HTTPS enforced | 301 | https://apished.com/mcp/v1/checksum |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ean_validate ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | identifier or value to check |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| valid | boolean | yes | – |
No examples provided.
iban_validate ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | identifier or value to check |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| valid | boolean | yes | – |
No examples provided.
isbn_validate ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | identifier or value to check |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| valid | boolean | yes | – |
No examples provided.
luhn_validate ~49
Validates a numeric string against the Luhn (mod-10) checksum — payment card numbers, IMEI numbers, and similar identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | identifier or value to check |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| valid | boolean | yes | – |
No examples provided.
swiftbic_validate ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | identifier or value to check |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| valid | boolean | yes | – |
No examples provided.
vateu_validate ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | identifier or value to check |
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| valid | boolean | yes | – |
No examples provided.
What is the Checksum Validator MCP server?
Checksum Validator is an MCP server listed in the public MCP registry as com.apished/checksum-validator. Validates Luhn, IBAN, ISBN, EAN/UPC, SWIFT/BIC, and EU VAT checksums and formats. This page covers its hosted endpoint (https://apished.com/mcp/v1/checksum).
Is the Checksum Validator MCP server safe to use?
Checksum Validator scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Checksum Validator MCP server expose?
Checksum Validator exposes 6 tools: ean_validate, iban_validate, isbn_validate, luhn_validate, swiftbic_validate, vateu_validate. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Does the Checksum Validator MCP server require authentication?
No. We connected to Checksum Validator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Checksum Validator MCP server still maintained?
Checksum Validator is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.