Log inSubmit server
Hash logo

Hash

Cryptographic hash & HMAC MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Hash

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "hash": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hash"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Tools2

What Hash lets your agent do. Expand a tool for its parameters.

Self-reported~87 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 33d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-hash (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads225Package downloads in the last 30 days.
Last commit28d agoMost recent push to the default branch.
Tools exposed2Callable tools this server registers over MCP.

From the project README

mcp-hash

Cryptographic hash & HMAC MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

ToolDescription
hashCompute a cryptographic hash (hex digest) of text: algorithm = md5, sha1, sha256 (default), sha384, or sha512. Keyless/offline; the input is not stored or transmitted. MD5/SHA-1 are legacy (checksums only, not security).
hmacCompute an HMAC (hex) of text with a secret key. algorithm = sha1, sha256 (default), sha384, or sha512. Keyless/offline.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

config.json
{
  "mcpServers": {
    "hash": {
      "url": "https://gateway.pipeworx.io/hash/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/hash/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

config.json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

Terminal
curl -X POST https://gateway.pipeworx.io/v1/tools/hash \
  -H 'Content-Type: application/json' \
  -d '{"text":"hello world"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/hash. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

config.json
{
  "mcpServers": {
    "hash": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-hash"]
    }
  }
}

Or run it directly to confirm it starts:

Terminal
npx -y @pipeworx/mcp-hash

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

Code
ask_pipeworx({ question: "your question about Hash data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Hash

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "hash": { "command": "npx", "args": ["-y","@pipeworx/mcp-hash"] } }

Cryptographic hash & HMAC MCP.

We don't have confirmed pricing for Hash. Listing it on AllMCPs is free, but that says nothing about what the server itself costs — check the project's own site for current pricing.

Related MCP servers

All in Cryptography All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHash AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/hash?style=directory)](https://allmcps.com/mcp/hash)
HTML Embed
<a href="https://allmcps.com/mcp/hash"><img src="https://allmcps.com/api/badge/hash?style=directory" alt="Hash on AllMCPs" /></a>