Mcp Cryptography

io.github.daedalusPublished by GitHub account daedalusv0.1.1Updated Oct 24, 2026

MCP server exposing cryptography library functionality

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that exposes Python cryptography library operations — key generation, encryption, signing, hashing, key derivation and X.509 certificates —…

What you can do
  • Generate symmetric (Fernet), RSA and X25519 keys
  • Encrypt and decrypt with Fernet, AES (CBC/GCM) and RSA-OAEP
  • Sign and verify with RSA and HMAC
  • Hash data with SHA-256, SHA-512 and SHA-1
  • Derive keys with PBKDF2 and Scrypt
  • Create self-signed X.509 certificates and parse certificates; generate random bytes and base64
When to use it
Useful when you want an assistant to perform ad-hoc cryptographic operations locally — producing test keys, encrypting or decrypting sample payloads, computing hashes and HMACs, or generating self-signed certificates — without writing scripts yourself.
Requirements
Runs as a local stdio process installed from the PyPI package mcp-cryptography (pip install). No accounts, API keys, environment variables or headers are declared. Desktop-only; not available as a web executable.
Before you install
Keys, plaintext and derived secrets pass through the assistant conversation and may be logged or retained by the model provider. Generated keys and certificates are returned to the model, so treat them as exposed and do not use them for production secrets. Encryption and signing tools act on whatever data is supplied; verify results before relying on them.

Installation

In SourceWeft

  1. Open Mcp Cryptography in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-cryptography

MCP server exposing cryptography library functionality.

[PyPI] [Python] [Ruff]

mcp-name: io.github.daedalus/mcp-cryptography

Install

bash
pip install mcp-cryptography

Usage

python
from mcp_cryptography import mcp
# Run the MCP serverif __name__ == "__main__":    mcp.run()

Available Tools

The server provides the following cryptographic tools:

Key Generation

  • generate_symmetric_key - Generate a Fernet symmetric key
  • generate_rsa_key - Generate an RSA key pair
  • generate_x25519_key - Generate an X25519 key pair

Symmetric Encryption

  • fernet_encrypt / fernet_decrypt - Fernet encryption
  • aes_encrypt / aes_decrypt - AES encryption (CBC/GCM modes)

Asymmetric Encryption

  • rsa_encrypt / rsa_decrypt - RSA OAEP encryption
  • rsa_sign / rsa_verify - RSA digital signatures

Hashing

  • hash_sha256 - SHA-256 hash
  • hash_sha512 - SHA-512 hash
  • hash_sha1 - SHA-1 hash

HMAC

  • hmac_sign - Generate HMAC
  • hmac_verify - Verify HMAC

Key Derivation

  • pbkdf2_derive - PBKDF2 key derivation
  • scrypt_derive - Scrypt key derivation

X.509 Certificates

  • generate_self_signed_cert - Generate self-signed certificate
  • parse_certificate - Parse X.509 certificate

Utilities

  • generate_random_bytes - Generate random bytes
  • generate_random_base64 - Generate random base64 bytes

Development

bash
git clone https://github.com/daedalus/mcp-cryptography.gitcd mcp-cryptographypip install -e ".[test]"
# run testspytest
# formatruff format src/ tests/
# lintruff check src/ tests/
# type checkmcp_cryptography src/

Source: README.md at commit 64b7ae8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts