CyberChef MCP Server

cyberchef_recipe_get

Read-onlyIdempotent

Retrieve a specific CyberChef recipe by its UUID to reuse or inspect the exact operations defined for data manipulation tasks.

Instructions

Get a recipe by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "cyberchef_recipe_get"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Recipe UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0Sep 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds no further behavioral details such as not-found behavior, response shape, or permission requirements, but it does not contradict the annotations.

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

Conciseness5/5

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

The description is a single clear sentence with no filler or redundant wording. Every word contributes to the basic purpose of the tool.

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

Completeness4/5

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

This is a simple one-parameter read-only getter, and the schema plus annotations cover most invocation needs. The absence of an output schema and any mention of what fields the returned recipe contains is a minor gap, but not enough to make the description inadequate.

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?

Schema description coverage is 100% and the single parameter 'id' is already described as 'Recipe UUID' with a UUID format and pattern. The description does not add meaningful parameter information beyond what the schema already provides.

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

Purpose4/5

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

The description clearly states the action ('Get'), the resource ('a recipe'), and the identifying mechanism ('by ID'). It is distinguishable from recipe_list and recipe_create, but it does not explicitly differentiate itself from recipe_export or recipe_execute.

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

Usage Guidelines3/5

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

The phrase 'by ID' implies this tool should be used when the agent already has a recipe UUID and wants the stored recipe. However, no alternative tools are mentioned and no explicit when-to-use or when-not-to-use guidance is given.

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