crypto-tools

Crypto Tools MCP Server exposes defense-grade cryptographic compliance and analysis utilities through a single MCP endpoint. It bundles compliance modules (FIPS 140-3 validation, CNSA 2.0 analysis, and PQC readiness) alongside a suite of classical cryptography tools (Caesar, Vigenere, XOR, ROT13, frequency analysis, and cipher detection) with easy-to-call tool interfaces. You can invoke individual tools or run integrated compliance checks via the MCP framework, enabling automated validation, reporting, and key lifecycle management within your trusted agent ecosystem. The server is designed for use within the Agentic System and can be extended with additional modules or custom analyses as part of a larger security tooling workflow.

To use the tools, connect to the MCP server and call the available tools by name, e.g. check_fips_compliance, analyze_cnsa_compliance, assess_pqc_readiness, or any of the classical tools like caesar_encrypt, vigenere_encrypt, or detect_cipher_type. Results are returned in structured formats suitable for integration into CI pipelines or security dashboards, with SARIF-compatible outputs where applicable.

Prerequisites:

• Python 3.10 or higher
• Access to install Python packages (pip)
• Git (optional, for cloning the repository)

Install steps:

1. Clone the repository (or download the release the MCP server is packaged in):

git clone https://github.com/marc-shade/crypto-tools-mcp.git
cd crypto-tools-mcp

2. Create and activate a virtual environment (recommended):

python -m venv venv
# On Windows
venv\Scripts\activate.bat
# On macOS/Linux
source venv/bin/activate

3. Install dependencies (if a requirements.txt is provided, otherwise install as needed):

pip install -r requirements.txt

4. Run the MCP server module (assuming the module is crypto_tools_mcp):

python -m crypto_tools_mcp

5. Confirm the server is reachable at the configured host/port (default 127.0.0.1:8000). Adjust environment variables as needed before starting (see mcp_config for env hints).

Notes and tips:

• Environment variables: LOG_LEVEL can be set to DEBUG/INFO/WARNING/ERROR for more verbose output. HOST and PORT can be overridden to bind the MCP server to a specific interface or port.
• If you modify the MCP configuration, ensure the server process is restarted to apply changes.
• Some environments may require additional system dependencies for cryptographic backends; consult the module's requirements and platform notes if you encounter cryptography-related errors.
• When integrating with automation pipelines, prefer using SARIF outputs from the Crypto Audit Engine for standardized security scanning results.
• If you plan to extend capabilities, you can add new tools under the existing module namespace and expose them through the MCP interface with consistent naming conventions.