Remote MCP · Endpoint
Hash Digest Tool MCP server
No. Hash Digest Tool answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://apished.com/mcp/v1/hash
The last check completed an MCP handshake.
- Registry name
- com.apished/hash-digest-tool
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 369 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 66.7% from 18 checks
- Described by its publisher as
- Computes MD5, SHA1, SHA256, SHA512, and CRC32 digests from text, base64, or hex input.
- Website
- https://apished.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 369 ms |
| 1 day ago | Handshake completed | 358 ms |
| 2 days ago | Handshake completed | 388 ms |
| 3 days ago | Handshake completed | 358 ms |
| 4 days ago | Handshake completed | 371 ms |
| 5 days ago | Handshake completed | 360 ms |
| 7 days ago | Handshake completed | 362 ms |
| 9 days ago | Handshake completed | 358 ms |
| 12 days ago | Handshake completed | 358 ms |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Handshake completed | 360 ms |
| 18 days ago | Handshake completed | 380 ms |
| 20 days ago | Handshake completed | 378 ms |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 28 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 29.
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.
Listing data comes from the official MCP registry. Glide is not affiliated with Hash Digest Tool and makes no claim about it beyond what these checks measured.