Is the Apished Checksum Validator MCP server down?

mcp-registry/com.apished/checksum-validator · v1.0.0

As of 2026-10-27 04:28 UTC, the Apished Checksum Validator MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks.

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

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

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (90/100)

What to fix (1)

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.apished%2Fchecksum-validator/fixes

{
  "name": "ean_validate",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "value"
    ],
    "properties": {
      "value": {
        "type": "string",
        "description": "identifier or value to check"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "iban_validate",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "value"
    ],
    "properties": {
      "value": {
        "type": "string",
        "description": "identifier or value to check"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "isbn_validate",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "value"
    ],
    "properties": {
      "value": {
        "type": "string",
        "description": "identifier or value to check"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.apished/checksum-validator"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.apished/checksum-validator"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~682 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.48% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• vateu_validate ~130 tokens
• swiftbic_validate ~129 tokens
• ean_validate ~112 tokens
• iban_validate ~109 tokens
• isbn_validate ~109 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.apished%2Fchecksum-validator.svg)](https://glimind.com/server/mcp-registry%2Fcom.apished%2Fchecksum-validator?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.apished%2Fchecksum-validator?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.apished%2Fchecksum-validator.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.apished%2Fchecksum-validator.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.apished%2Fchecksum-validator?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3d5ddf4242b8edff…, first seen 2026-10-24, included at leaf 61679 of 77,349. Version history · verify what your client received.

Tools (6)

• ean_validate
• iban_validate
• isbn_validate
• luhn_validate
• swiftbic_validate
• vateu_validate

Compare: most reliable other servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Apished Checksum Validator MCP server down right now?

As of 2026-10-27 04:28 UTC, the Apished Checksum Validator MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks.

How many tools does Apished Checksum Validator MCP server provide?

Apished Checksum Validator MCP server advertises 6 tools, including ean_validate, iban_validate, isbn_validate, luhn_validate, swiftbic_validate.

How do I install Apished Checksum Validator MCP server?

Point your MCP client at this streamable-http endpoint: https://apished.com/mcp/v1/checksum

Is the Apished Checksum Validator MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Apished Checksum Validator MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.