CyberChef MCP Server
Related Servers
Alternatives to CyberChef MCP Server
- AlicenseAqualityAmaintenanceModel Context Protocol server for Ghidra reverse engineering. 179 tools for decompilation, symbol management, cross-references, and binary analysis.83,761Apache 2.0
Related Servers
- AlicenseBqualityCmaintenanceEnables LLM clients to encode, decode, and transform data using CyberChef operations via an MCP server that interfaces with the CyberChef API.344MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to discover, execute, and validate CyberChef operations for data encoding, decoding, encryption, and transformation tasks. Provides structured access to CyberChef's extensive catalog of data manipulation tools through natural language interactions.-
- FlicenseNot gradedqualityCmaintenanceExposes hundreds of CyberChef data operations as tools for LLM agents to perform encoding, decoding, hashing, compression, encryption, and data format conversion.-
- FlicenseAqualityCmaintenanceEnables AI assistants to perform defensive security tasks such as vulnerability detection, CVE lookup, phishing/link safety checks, and security report generation via MCP tools.23-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to autonomously execute over 200 open-source penetration testing tools via MCP, including reconnaissance, web exploitation, and brute-forcing, through a unified server architecture with Docker sandboxing for safe execution.53MIT
- AlicenseAqualityBmaintenanceAn MCP server that bundles 53 online utility tools (164 capabilities) for AI assistants, covering JSON processing, encryption/decryption, code formatting, text conversion, unit conversion, network queries, QR/barcode generation, and reference lookups via natural language calls.53431MIT
TDQS
Scored across 23 tools
Most tools are distinct, but cyberchef_recipe_execute, cyberchef_bake, and cyberchef_batch overlap heavily in executing operations/recipes; the description clarifies that bake is for complex chains and batch for multiple operations, but the boundaries remain fuzzy for an agent.
All tools follow the consistent prefix_noun_verb pattern (cyberchef_recipe_delete, cyberchef_list_operations, etc.), making the set predictable and scannable.
23 tools is on the heavy side for a single domain; the 10 recipe lifecycle tools are justified, but cache, worker, quota, and telemetry stats tools add operational overhead that feels tangential to core CyberChef usage.
Recipe lifecycle is fully covered (create, get, list, update, delete, test, validate, import, export, execute), and operation discovery plus analysis tools are present; minor gaps include no direct recipe duplicate/copy or operation-level metadata export.