io.github.ryudi84/hash
hash-forge
Is the io.github.ryudi84/hash MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.
MCP server for cryptographic hashing — MD5, SHA-1, SHA-256, SHA-384, SHA-512
alive probed 2026-11-14 · unchanged since 2026-10-27
- Run it
- npx -y hash-forge-mcp@1.0.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- hash-forge 1.0.0
- Capabilities
- tools
- Instructions
- 91 characters
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 477 tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 498. The o200k_base estimate is 253. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/ryudi84/sovereign-mcp-servers
- Registry
- active, updated 2026-02-25 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.89×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| compute_hmac | 192 | 102 | 40 % |
| compare_hashes | 145 | 77 | 30 % |
| hash_text | 140 | 74 | 29 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- io.github.ryudi84/hash-forge-mcp npmjs.com
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.ryudi84/env-forge-mcp · alive
- io.github.ryudi84/github-stats · alive
- io.github.ryudi84/gradient · alive
- io.github.ryudi84/gradient-forge-mcp · alive
- io.github.ryudi84/hash-forge-mcp · alive
- io.github.ryudi84/ip-calc · alive
- io.github.ryudi84/ip-calc-mcp · alive
- io.github.ryudi84/json · alive
Servers that mention hash.
- DJZS Trust MCP ai.djzs/trust-mcp · alive
- ai.getvda/password-hashing-and-jwt-service · newer protocol
- TikTok Trends API ai.trendsapi/tiktok · alive
- TikTok Trends MCP ai.trendsmcp/tiktok · alive
- A.U.G.U.R Synapse · Utils art.maddegen.agent/synapse-util · alive
- AINumbers Fintech Intelligence Suite co.ainumbers/tools · alive
- APIShed com.apished/apished · not MCP
- Hash Digest Tool com.apished/hash-digest-tool · not MCP
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-27 06:57 | alive | 306 ms | 3 | 477 | 253 |
| 2026-10-20 06:46 | alive | 352 ms | 3 | 253 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.