CyberChef API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CYBERCHEF_API_URL | Yes | The URL of the CyberChef API server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bake_recipeC | |
| batch_bake_recipeC | |
| perform_magic_operationB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| data://cyberchef-operations-categories |
TDQS
Scored across 3 tools
bake_recipe and batch_bake_recipe are clearly distinct (single vs batch input), but their similarity could cause confusion. perform_magic_operation is distinct.
All tools use snake_case and verb_noun pattern (bake_recipe, batch_bake_recipe, perform_magic_operation), though 'perform' is less typical than 'bake'.
3 tools is slightly low but appropriate for a focused CyberChef wrapper; covers baking and magic detection without being overly minimal.
Covers core recipe execution and auto-detection, but missing tools for exploring available operations or constructing recipes, which are typical needs.