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-cryptography

PYPI · MCP-CRYPTOGRAPHY · SCANNED SEP 20

MCP server exposing cryptography library functionality

Available components

0 this week 81 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
  • 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1070 tokens (~48/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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • 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
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

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

io.github.daedalus/mcp-cryptography runs locally as a PyPI package, launched with uvx mcp-cryptography. 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-cryptography

# add to Claude Code
claude mcp add daedalus-mcp-cryptography -- uvx mcp-cryptography
// .cursor/mcp.json
{
  "mcpServers": {
    "daedalus-mcp-cryptography": {
      "command": "uvx",
      "args": [
        "mcp-cryptography"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "daedalus-mcp-cryptography": {
      "command": "uvx",
      "args": [
        "mcp-cryptography"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add daedalus-mcp-cryptography -- uvx mcp-cryptography
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "daedalus-mcp-cryptography": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-cryptography"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add daedalus-mcp-cryptography --command uvx --arg mcp-cryptography
# ~/.hermes/config.yaml
mcp_servers:
  daedalus-mcp-cryptography:
    command: "uvx"
    args: ["mcp-cryptography"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "daedalus-mcp-cryptography": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-cryptography"
      ]
    }
  }
}
# add to Vellum
assistant mcp add daedalus-mcp-cryptography -t stdio -c uvx -a mcp-cryptography
// mcp.json
{
  "mcpServers": {
    "daedalus-mcp-cryptography": {
      "command": "uvx",
      "args": [
        "mcp-cryptography"
      ]
    }
  }
}
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 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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-cryptography@0.1.1

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 18 packages
Packages resolved 18
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~1,070 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
aes_decrypt ~70

Decrypt AES ciphertext.

NameTypeReqDescription
ciphertextstringyesHex-encoded ciphertext.
ivstringyesHex-encoded initialization vector.
keystringyesHex-encoded AES key.
modestringEncryption mode - 'CBC' or 'GCM' (default CBC).
NameTypeReqDescription
resultstringyes

No examples provided.

aes_encrypt ~66

Encrypt data using AES.

NameTypeReqDescription
datastringyesString to encrypt.
keystringyesHex-encoded AES key (16, 24, or 32 bytes).
modestringEncryption mode - 'CBC' or 'GCM' (default CBC).

Structured output declared, but exposes no named fields.

No examples provided.

fernet_decrypt ~42

Decrypt Fernet ciphertext.

NameTypeReqDescription
ciphertextstringyesBase64-encoded ciphertext.
keystringyesBase64-encoded Fernet key.
NameTypeReqDescription
resultstringyes

No examples provided.

fernet_encrypt ~43

Encrypt data using Fernet symmetric encryption.

NameTypeReqDescription
datastringyesPlain text string to encrypt.
keystringyesBase64-encoded Fernet key.
NameTypeReqDescription
resultstringyes

No examples provided.

generate_random_base64 ~34

Generate random bytes encoded as base64.

NameTypeReqDescription
lengthintegerNumber of bytes to generate (default 32).
NameTypeReqDescription
resultstringyes

No examples provided.

generate_random_bytes ~29

Generate random bytes.

NameTypeReqDescription
lengthintegerNumber of bytes to generate (default 32).
NameTypeReqDescription
resultstringyes

No examples provided.

generate_rsa_key ~41

Generate an RSA key pair.

NameTypeReqDescription
key_sizeintegerKey size in bits (default 2048). Must be at least 2048.

Structured output declared, but exposes no named fields.

No examples provided.

generate_self_signed_cert ~62

Generate a self-signed X.509 certificate.

NameTypeReqDescription
common_namestringyesCommon name for the certificate subject.
days_validintegerNumber of days the certificate is valid (default 365).
organizationOrganization name (optional).

Structured output declared, but exposes no named fields.

No examples provided.

generate_symmetric_key ~63

Generate a Fernet symmetric key. Returns: Base64-encoded 32-byte key suitable for Fernet encryption. Example: >>> key = generate_symmetric_key() >>> len(key) # 44 characters base64 encoded 44

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

generate_x25519_key ~67

Generate an X25519 key pair for key exchange. Returns: Dictionary with 'public_key' and 'private_key' in PEM format. Example: >>> keys = generate_x25519_key() >>> len(keys['public_key']) > 0 True

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

hash_sha1 ~42

Compute SHA-1 hash. Note: SHA-1 is considered cryptographically broken. Use only for legacy compatibility.

NameTypeReqDescription
datastringyesString to hash.
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha256 ~31

Compute SHA-256 hash.

NameTypeReqDescription
datastringyesString or base64-encoded bytes to hash.
NameTypeReqDescription
resultstringyes

No examples provided.

hash_sha512 ~25

Compute SHA-512 hash.

NameTypeReqDescription
datastringyesString to hash.
NameTypeReqDescription
resultstringyes

No examples provided.

hmac_sign ~57

Generate HMAC.

NameTypeReqDescription
algorithmstringHash algorithm - 'sha256' or 'sha512' (default sha256).
datastringyesString to sign.
keystringyesHex-encoded key.
NameTypeReqDescription
resultstringyes

No examples provided.

hmac_verify ~68

Verify HMAC.

NameTypeReqDescription
algorithmstringHash algorithm - 'sha256' or 'sha512'.
datastringyesString that was signed.
hmacstringyesHex-encoded HMAC to verify.
keystringyesHex-encoded key.
NameTypeReqDescription
resultbooleanyes

No examples provided.

parse_certificate ~27

Parse X.509 certificate.

NameTypeReqDescription
certificate_pemstringyesCertificate in PEM format.

Structured output declared, but exposes no named fields.

No examples provided.

pbkdf2_derive ~68

Derive key using PBKDF2.

NameTypeReqDescription
iterationsintegerNumber of iterations (default 480000, OWASP recommended).
passwordstringyesPassword to derive from.
saltHex-encoded salt (optional, will generate if not provided).

Structured output declared, but exposes no named fields.

No examples provided.

rsa_decrypt ~45

Decrypt RSA ciphertext using private key.

NameTypeReqDescription
ciphertextstringyesBase64-encoded ciphertext.
private_key_pemstringyesRSA private key in PEM format.
NameTypeReqDescription
resultstringyes

No examples provided.

rsa_encrypt ~55

Encrypt data using RSA with OAEP asymmetric_padding.

NameTypeReqDescription
datastringyesString to encrypt (max ~446 bytes for 4096-bit key).
public_key_pemstringyesRSA public key in PEM format.
NameTypeReqDescription
resultstringyes

No examples provided.

rsa_sign ~39

Create RSA digital signature.

NameTypeReqDescription
datastringyesString to sign.
private_key_pemstringyesRSA private key in PEM format.
NameTypeReqDescription
resultstringyes

No examples provided.

rsa_verify ~51

Verify RSA digital signature.

NameTypeReqDescription
datastringyesOriginal signed data.
public_key_pemstringyesRSA public key in PEM format.
signaturestringyesBase64-encoded signature.
NameTypeReqDescription
resultbooleanyes

No examples provided.

scrypt_derive ~45

Derive key using Scrypt.

NameTypeReqDescription
passwordstringyesPassword to derive from.
saltHex-encoded salt (optional, will generate if not provided).

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

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

io.github.daedalus/mcp-cryptography is listed in the public MCP registry as io.github.daedalus/mcp-cryptography. MCP server exposing cryptography library functionality. This page covers its PyPI package (mcp-cryptography).

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

io.github.daedalus/mcp-cryptography scores 81 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-cryptography server expose?

io.github.daedalus/mcp-cryptography exposes 22 tools: generate_symmetric_key, generate_rsa_key, generate_x25519_key, fernet_encrypt, fernet_decrypt, and 17 more. Their descriptions and schemas cost roughly 1,070 tokens of context every time the server is loaded.

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

io.github.daedalus/mcp-cryptography 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-cryptography server under?

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