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

MCP server exposing cryptography library functionality

Available components

0 this week 94 Trust /100

Last scanned (17 hours ago)

Scores higher than 97% of PyPI servers

Category Security

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 build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency96
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to daedalus/mcp-cryptography). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 208 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 979 tokens (~44/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 25 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 23 Oct 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.

  • 22 Oct 26 −1
    • Stability: pass → 0.93 functional
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 4 Nov 2026 · Analysed pypi/mcp-cryptography@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo daedalus/mcp-cryptography
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/daedalus/mcp-cryptography/.github/workflows/pypi-publish.yml@refs/tags/v0.1.1
Rekor log index 1262898088
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:769cd8a77ca2ef71a35d71d4f8b43484578a4e8e59c06decbc357b34a3f9ace9

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 · ~979 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.
modestring–Encryption 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).
modestring–Encryption 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
lengthinteger–Number of bytes to generate (default 32).
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_random_bytes ~29

Generate random bytes.

NameTypeReqDescription
lengthinteger–Number of bytes to generate (default 32).
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_rsa_key ~41

Generate an RSA key pair.

NameTypeReqDescription
key_sizeinteger–Key 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_validinteger–Number of days the certificate is valid (default 365).
organization––Organization name (optional).

Structured output declared, but exposes no named fields.

No examples provided.

generate_symmetric_key ~17

Generate a Fernet symmetric key.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

generate_x25519_key ~22

Generate an X25519 key pair for key exchange.

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
algorithmstring–Hash algorithm - 'sha256' or 'sha512' (default sha256).
datastringyesString to sign.
keystringyesHex-encoded key.
NameTypeReqDescription
resultstringyes–

No examples provided.

hmac_verify ~68

Verify HMAC.

NameTypeReqDescription
algorithmstring–Hash 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
iterationsinteger–Number of iterations (default 480000, OWASP recommended).
passwordstringyesPassword to derive from.
salt––Hex-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.
salt––Hex-encoded salt (optional, will generate if not provided).

Structured output declared, but exposes no named fields.

No examples provided.

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
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 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 979 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 4 November 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.