Skip to main content
Glama
noor202401938-netizen

cyber-chef-mcp

by noor202401938-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cyberchef_bake

Run multi-step data transformations to decode obfuscated payloads by chaining operations like Base64, Hex, URL decode, XOR, and hashing in a single pass. Solve layered encoding without multiple rounds.

Instructions

Executes a multi-stage sequential data transformation pipeline ('recipe') on the input string, chaining multiple operations such as Base64, Hex, URL decoding, XOR, ROT13, and hashing in a single turn. Use this tool when dealing with layered obfuscation or when an automated pipeline is needed to fully unwrap nested attack payloads without requiring multiple LLM conversational rounds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe raw, encoded, or obfuscated input string to process through the transformation pipeline. Can be plain text, hex-encoded bytes, Base64 strings, or URL-encoded parameters.
recipeYesOrdered array of recipe steps to execute in sequence. Example: [{'op': 'From Base64'}, {'op': 'URL Decode'}]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.2
    • changedInput schema / properties / input / description
      Previous value: -"The raw or encoded input string to transform"New value: +"The raw, encoded, or obfuscated input string to process through the transformation pipeline. Can be plain text, hex-encoded bytes, Base64 strings, or URL-encoded parameters."
    • changedInput schema / properties / recipe / description
      Previous value: -"Array of recipe steps to execute in sequence"New value: +"Ordered array of recipe steps to execute in sequence. Example: [{'op': 'From Base64'}, {'op': 'URL Decode'}]"
    • changedInput schema / properties / recipe / items / properties / args / description
      Previous value: -"Optional arguments for the operation"New value: +"Optional array of arguments required by the operation (e.g. ['secret'] for XOR key, or [13] for ROT13 offset). If omitted, operation defaults are used."
    • changedInput schema / properties / recipe / items / properties / op / description
      Previous value: -"Operation name, e.g., 'From Base64', 'URL Decode', 'From Hex'"New value: +"The canonical name of the CyberChef operation to apply. Supported operations include: 'From Base64', 'To Base64', 'From Hex', 'To Hex', 'URL Decode', 'URL Encode', 'XOR', 'ROT13', 'MD5', 'SHA256', 'Defang URL', 'Refang URL', 'Entropy', 'Extract URLs', 'Extract Emails'."
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully states that operations are sequential and happen in a single turn, but it does not describe output format, failure behavior, or whether the operation is side-effect-free. The transformation nature implies non-destructiveness, but this is not made explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the core action. There is minor redundancy between 'multi-stage sequential' and 'chaining multiple operations', and between 'single turn' and 'without requiring multiple LLM conversational rounds', but overall it is well-structured and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The parameter instructions and recipe examples are clear and complete. However, there is no output schema and the description does not describe what the tool returns or how errors are handled, which leaves a gap for a tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the schema already documents both parameters well. The description adds context and operation examples but no additional parameter syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('executes a multi-stage sequential data transformation pipeline') and a specific resource ('input string', 'recipe'). It emphasizes chaining multiple operations, which distinguishes it from the sibling single-operation tools like cyberchef_from_base64 or cyberchef_url_decode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool: for layered obfuscation or when an automated pipeline is needed without multiple conversational rounds. It does not explicitly say 'do not use for single operations', but the contrast with sibling tools is strongly implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools