Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.daedalus/mcp-hashlib

PYPI · MCP-HASHLIB · SCANNED SEP 20

An MCP server that exposes hashlib functionality

Available components

0 this week 74 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 729 tokens (~33/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • Manipulation not yet verified: only 14 of 22 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.daedalus/mcp-hashlib server?

io.github.daedalus/mcp-hashlib runs locally as a PyPI package, launched with uvx mcp-hashlib. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-hashlib

# add to Claude Code
claude mcp add daedalus-mcp-hashlib -- uvx mcp-hashlib
// .cursor/mcp.json
{
  "mcpServers": {
    "daedalus-mcp-hashlib": {
      "command": "uvx",
      "args": [
        "mcp-hashlib"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "daedalus-mcp-hashlib": {
      "command": "uvx",
      "args": [
        "mcp-hashlib"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add daedalus-mcp-hashlib -- uvx mcp-hashlib
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "daedalus-mcp-hashlib": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-hashlib"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add daedalus-mcp-hashlib --command uvx --arg mcp-hashlib
# ~/.hermes/config.yaml
mcp_servers:
  daedalus-mcp-hashlib:
    command: "uvx"
    args: ["mcp-hashlib"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "daedalus-mcp-hashlib": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-hashlib"
      ]
    }
  }
}
# add to Vellum
assistant mcp add daedalus-mcp-hashlib -t stdio -c uvx -a mcp-hashlib
// mcp.json
{
  "mcpServers": {
    "daedalus-mcp-hashlib": {
      "command": "uvx",
      "args": [
        "mcp-hashlib"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +13
    • Malware scan: unverified → pass security
    • Stability: pass → 0.80 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 −14
    • Malware scan: pass → unverified security
  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +13
    • Malware scan: unverified → pass security
    • Stability: pass → 0.80 functional
  • 11 Sept 26 −15
    • Malware scan: pass → unverified security
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/mcp-hashlib@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 38 packages
Packages resolved 38
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~729 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
hash_blake2b ~37

Compute BLAKE2b hash (512-bit)

NameTypeReqDescription
datastringyes
digest_sizeinteger
NameTypeReqDescription
resultstringyes

No examples provided.

hash_blake2s ~37

Compute BLAKE2s hash (256-bit)

NameTypeReqDescription
datastringyes
digest_sizeinteger
NameTypeReqDescription
resultstringyes

No examples provided.

hash_copy ~30

Create a copy of a hash object

NameTypeReqDescription
algorithmstringyes
datastringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_file_digest ~31

Compute hash of a file-like object

NameTypeReqDescription
algorithmstring
datastringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_info ~23

Get information about available hash algorithms

NameTypeReqDescription
info_typestring
NameTypeReqDescription
resultstringyes

No examples provided.

hash_md5 ~30

Compute MD5 hash

NameTypeReqDescription
datastringyes
usedforsecurityboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_new ~37

Create hash object using any available algorithm

NameTypeReqDescription
algorithmstringyes
datastringyes
hexboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_pbkdf2_hmac ~60

PBKDF2-HMAC key derivation

NameTypeReqDescription
dkleninteger
hash_namestring
iterationsinteger
passwordstringyes
saltstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_properties ~22

Get properties of a hash algorithm

NameTypeReqDescription
algorithmstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_scrypt ~58

Scrypt key derivation

NameTypeReqDescription
dkleninteger
ninteger
pinteger
passwordstringyes
rinteger
saltstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha1 ~30

Compute SHA1 hash

NameTypeReqDescription
datastringyes
usedforsecurityboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha224 ~30

Compute SHA224 hash

NameTypeReqDescription
datastringyes
usedforsecurityboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha256 ~30

Compute SHA256 hash

NameTypeReqDescription
datastringyes
usedforsecurityboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha3_224 ~25

Compute SHA3-224 hash

NameTypeReqDescription
datastringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha3_256 ~25

Compute SHA3-256 hash

NameTypeReqDescription
datastringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha3_384 ~25

Compute SHA3-384 hash

NameTypeReqDescription
datastringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha3_512 ~25

Compute SHA3-512 hash

NameTypeReqDescription
datastringyes
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha384 ~30

Compute SHA384 hash

NameTypeReqDescription
datastringyes
usedforsecurityboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha512 ~30

Compute SHA512 hash

NameTypeReqDescription
datastringyes
usedforsecurityboolean
NameTypeReqDescription
resultstringyes

No examples provided.

hash_shake_128 ~38

Compute SHAKE-128 XOF hash (variable length)

NameTypeReqDescription
datastringyes
output_lengthinteger
NameTypeReqDescription
resultstringyes

No examples provided.

hash_shake_256 ~38

Compute SHAKE-256 XOF hash (variable length)

NameTypeReqDescription
datastringyes
output_lengthinteger
NameTypeReqDescription
resultstringyes

No examples provided.

hash_update ~38

Compute hash incrementally with multiple updates

NameTypeReqDescription
algorithmstringyes
data_partsarrayyes
hexboolean
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.daedalus/mcp-hashlib server?

io.github.daedalus/mcp-hashlib is listed in the public MCP registry as io.github.daedalus/mcp-hashlib. An MCP server that exposes hashlib functionality. This page covers its PyPI package (mcp-hashlib).

Is the io.github.daedalus/mcp-hashlib server safe to use?

io.github.daedalus/mcp-hashlib scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.daedalus/mcp-hashlib server expose?

io.github.daedalus/mcp-hashlib exposes 22 tools: hash_md5, hash_sha1, hash_sha256, hash_sha512, hash_sha224, and 17 more. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.

Is the io.github.daedalus/mcp-hashlib server still maintained?

io.github.daedalus/mcp-hashlib is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.daedalus/mcp-hashlib server under?

io.github.daedalus/mcp-hashlib declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.