Hashproof MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

const TELEGRAM_API_BASE = "https://api.telegram.org";

        "input": "0x608060405234801561001057600080fd5b50336000806101000a81548173ffffffffffffffffffffffffffffffffffffffff021916908373ffffffffffffffffffffffffffffffffffffffff1602179055506113b5806100606000396000f3fe608060405234801561001057600080fd5b506004361061009e5760003560e01c8063…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add hashproof -- npx -y hashproof-mcp

{
  "mcpServers": {
    "hashproof": {
      "command": "npx",
      "args": [
        "-y",
        "hashproof-mcp"
      ]
    }
  }
}

[mcp_servers.hashproof]
command = "npx"
args = ["-y", "hashproof-mcp"]

{
  "mcpServers": {
    "hashproof": {
      "command": "npx",
      "args": [
        "-y",
        "hashproof-mcp"
      ]
    }
  }
}

{
  "servers": {
    "hashproof": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "hashproof-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: HASHPROOF_API_KEY (Prepaid API key (alternative to wallet). One of the two payment methods is required only for issue_credential), HASHPROOF_WALLET_PRIVATE_KEY (EVM private key of a dedicated wallet holding USDC on Base or Celo — pays $0.10 per issuance via x402), HASHPROOF_X402_NETWORK (base (default) or celo).