Skip to main content
Glama
noor202401938-netizen

cyber-chef-mcp

by noor202401938-netizen
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Local

cyberchef_help

Search the built-in catalog of 28 core CyberChef operations by keyword or category to discover supported recipe names, tools, and parameters for data encoding, decoding, and analysis.

Instructions

Searches the built-in catalog of 28 core CyberChef operations to find available tools, supported recipe names, and operation parameters by keyword or category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional search term to filter operations (e.g., 'base64', 'hex', 'hash', 'aes', 'xor', 'jwt', 'forensics').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.4
    • changedInput schema / properties / query / description
      Previous value: -"Optional search term to filter operations (e.g., 'base64', 'hex', 'hash', 'xor', 'jwt', 'forensics'). If omitted or empty, returns the full catalog."New value: +"Optional search term to filter operations (e.g., 'base64', 'hex', 'hash', 'aes', 'xor', 'jwt', 'forensics')."
  2. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / query / description
      Previous value: -"Search term like 'hash', 'base64', 'aes', 'forensics', or leave empty for full catalog"New value: +"Optional search term to filter operations (e.g., 'base64', 'hex', 'hash', 'xor', 'jwt', 'forensics'). If omitted or empty, returns the full catalog."
  3. First observedv1.0.1

TDQS

A4/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 full behavioral burden. 'Searches' implies a read-only lookup with no side effects, and the description says what kind of information is returned, but it does not explicitly confirm that it performs no mutation or describe any auth, rate-limit, or failure behavior.

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 well-formed sentence that front-loads the action and resource, then states the intended outcome. Every clause earns its place with no redundancy.

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?

For a simple read-only discovery tool with one optional parameter and no output schema, the description adequately covers its purpose and the kind of results it returns. It could be slightly more complete by clarifying whether an empty query returns the full catalog or by naming the sibling tools it complements.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents the optional query parameter with examples. The description adds that the query can be a keyword or a category, which is a small but useful semantic extension beyond the schema's example list.

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 states a specific verb (Searches), a specific resource (the built-in catalog of 28 core CyberChef operations), and the intended outcome (find available tools, supported recipe names, and operation parameters). It clearly distinguishes this discovery/help tool from the sibling execution tools such as cyberchef_bake or cyberchef_sha256.

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 description implies the tool is for looking up operations by keyword or category, but it does not explicitly state when to use it versus the sibling execution tools, nor does it state when not to use it. An agent can infer its role, but the routing guidance is only 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