@sebastienrousseau/crypto-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @sebastienrousseau/crypto-mcp@0.0.39
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
crypto_key_list | Returned a result under 0.1 s · 34 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
crypto_generate_key type, modulusLength, curve
Generate a key inside the server: a classical (RSA, ECC, Ed25519) or post-quantum (ML-KEM 512/768/1024 FIPS 203, ML-DSA 44/65/87 FIPS 204) keypair, a 256-bit symmetric key, or an HMAC-SHA256 key. Returns a keyHandle and, for keypairs, the public key. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_key_list
List the key handles this server holds, with each key's type and public metadata. At most 64 keys are held; beyond that the least recently used key is destroyed.
crypto_key_destroy keyHandle
Destroy a key: overwrite its secret bytes where the runtime allows and invalidate its handle.
crypto_key_import path, kind
Import an existing key from a file in the directory the server operator set in CRYPTO_MCP_KEY_DIR (disabled when it is unset). Reads an unencrypted PKCS#8 PEM private key (Ed25519, RSA 2048/3072/4096, ECDSA P-256/P-384/secp256k1; the type comes from the key) or a raw 32-byte key, as 32 binary bytes or 64 hex digits, imported as 'symmetric-256' (default) or 'hmac-sha256'. Files over 65536 bytes are refused. The key bytes never pass through the conversation. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_inspect_key keyData
Inspect and parse PEM certificate, public key, or OpenPGP armored block.
18 more tools
crypto_encrypt plaintext, algorithm, keyHandle
Encrypt plaintext with authenticated encryption (AES-256-GCM or ChaCha20-Poly1305) under a symmetric-256 key handle. Without keyHandle, a new key is generated and its handle returned. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_decrypt ciphertext, algorithm, keyHandle, iv, authTag
Decrypt and authenticate an AES-256-GCM or ChaCha20-Poly1305 ciphertext with a symmetric-256 key handle.
crypto_kem_encapsulate publicKey, level
Encapsulate a shared secret to an ML-KEM (FIPS 203) public key (512, 768, 1024). Returns the KEM ciphertext for the recipient and a symmetric-256 keyHandle for the shared secret, usable with crypto_encrypt. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_kem_decapsulate keyHandle, ciphertext, level
Recover an ML-KEM shared secret with an ml-kem key handle (512, 768, 1024). Returns a symmetric-256 keyHandle for the shared secret. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_hybrid_kem_encapsulate x25519PublicKey, mlKemPublicKey, level
Encapsulate a shared secret using Post-Quantum Hybrid KEM (X25519 + ML-KEM, RFC 9180/10024). Returns the classical ephemeral public key, ML-KEM ciphertext, and a symmetric-256 keyHandle for the combined shared secret. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_hybrid_kem_decapsulate x25519KeyHandle, mlKemKeyHandle, x25519EphemeralPublic, mlKemCiphertext, level
Recover a Post-Quantum Hybrid KEM shared secret (X25519 + ML-KEM) using server-held x25519 and ml-kem key handles. Returns a symmetric-256 keyHandle for the combined shared secret. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_stream_encrypt plaintext, x25519PublicKey, mlKemPublicKey, chunkSize
Encrypt plaintext using post-quantum hybrid STREAM AEAD (X25519 + ML-KEM-768 + XChaCha20-Poly1305) with anti-truncation protection. Returns base64 ciphertext.
crypto_stream_decrypt ciphertext, x25519KeyHandle, mlKemKeyHandle, chunkSize
Decrypt a post-quantum hybrid STREAM AEAD ciphertext using server-held x25519 and ml-kem-768 key handles. Plaintext memory is wiped after decoding.
crypto_stream_multi_encrypt plaintext, recipients, chunkSize
Encrypt plaintext for multiple recipients using post-quantum hybrid STREAM AEAD (X25519 + ML-KEM-768 + XChaCha20-Poly1305) with anti-truncation framing. Returns base64 ciphertext.
crypto_stream_multi_decrypt ciphertext, x25519KeyHandle, mlKemKeyHandle, recipientId, chunkSize
Decrypt a multi-recipient post-quantum hybrid STREAM AEAD ciphertext using server-held x25519 and ml-kem-768 key handles. Plaintext memory is wiped after decoding.
crypto_hybrid_kem_multi_encapsulate recipients, keyHandle
Encapsulate a symmetric key for multiple recipients using post-quantum hybrid KEM (X25519 + ML-KEM-768 + AES-256-GCM key wrapping). Returns recipient ciphertexts and a symmetric-256 keyHandle.
crypto_hybrid_kem_multi_decapsulate x25519KeyHandle, mlKemKeyHandle, ephemeralPublicKey, mlKemCiphertext, wrappedKey, encryptedKey, recipients, recipientId, recipientIndex
Decapsulate a multi-recipient post-quantum hybrid KEM key using server-held x25519 and ml-kem-768 key handles. Returns a symmetric-256 keyHandle for the recovered DEK.
crypto_sign data, keyHandle
Sign data with a key handle. The algorithm follows the key: Ed25519, RSASSA-PSS (SHA-256), ECDSA (SHA-256; SHA-384 on P-384), ML-DSA (44, 65, 87, FIPS 204), or HMAC-SHA256.
crypto_verify data, signature, publicKey, keyHandle
Verify a signature against a public key (SPKI PEM or ML-DSA hex) or a key handle (also HMAC-SHA256). Pass exactly one of publicKey or keyHandle.
crypto_hash data, algorithm
Compute cryptographic digest (SHA-256, SHA-384, SHA-512, SHA3-256, BLAKE2b512).
crypto_kms_wrap provider, keyId, keyHandle
Wrap the Data Encryption Key (DEK) a symmetric-256 key handle refers to under a Key Encryption Key held by a KMS provider. Only the 'local' provider is configured.
crypto_kms_unwrap provider, keyId, wrappedKey
Unwrap a DEK previously wrapped by crypto_kms_wrap in this server process into a symmetric-256 key handle. Only the 'local' provider is configured. Secret key material stays inside the server; only an opaque keyHandle is returned.
crypto_audit_cbom algorithms
Generate a Cryptographic Bill of Materials (CBOM) inventory from cryptographic identifiers.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT OR Apache-2.0 |
|---|---|
| Needs | node >=22.0.0 |
| Source | github.com/sebastienrousseau/crypto-service |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-kKzoD83OOODsm5nEQ60rAn/Gal9V0njl4r5+1W0moy6osFwXJP9WuEKXQqDbtFBh0aJpj7Bhw4xesjNzpdeTzA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40sebastienrousseau/crypto-mcp)
New version out? Ask for a fresh report.