Remote MCP · Endpoint

Checksum Validator MCP server

No. Checksum Validator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://apished.com/mcp/v1/checksum

The last check completed an MCP handshake.

Registry name
com.apished/checksum-validator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
362 ms
Tools exposed
6 tools
Uptime, last 30 days
68.4% from 19 checks
Described by its publisher as
Validates Luhn, IBAN, ISBN, EAN/UPC, SWIFT/BIC, and EU VAT checksums and formats.
Website
https://apished.com/
Listing
From the official MCP registry (active).
Recent checks of Checksum Validator
CheckedResultHandshake
1 hour agoHandshake completed362 ms
18 hours agoHandshake completed364 ms
2 days agoHandshake completed368 ms
3 days agoHandshake completed362 ms
4 days agoHandshake completed371 ms
5 days agoHandshake completed722 ms
6 days agoHandshake completed380 ms
7 days agoHandshake completed374 ms
10 days agoHandshake completed375 ms
13 days agoHandshake completed413 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed366 ms
19 days agoHandshake completed417 ms
21 days agoHandshake completed365 ms
23 days agoFailed - the server returned an HTTP error—
25 days agoFailed - the server returned an HTTP error—
27 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—
29 days agoFailed - the server returned an HTTP error—

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Checksum Validator and makes no claim about it beyond what these checks measured.