Skip to main content
Glama
doublegate

CyberChef MCP Server

by doublegate

cyberchef_crib_drag

Read-onlyIdempotent

Drag a guessed plaintext crib across XOR ciphertext to find matching offsets. Use two ciphertexts to reveal plaintext spans, or a known key length to recover key bytes.

Instructions

Drag a guessed plaintext fragment along a XOR ciphertext and report every offset where it fits, ranked. With TWO ciphertexts under one key their XOR cancels the key, so a crib guessed in one message yields the matching span of the OTHER. With ONE ciphertext and a known fragment it yields key bytes instead; supply key_length and periodicity becomes a far stronger filter than printability, recovering the whole key when the crib is at least as long as it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoHow many offsets to report, best first.
cribYesThe guessed plaintext fragment, e.g. " the ".
ciphertextYesThe ciphertext to drag along.
key_lengthNoSingle-ciphertext mode only: the repeating key's length, if known. Derived bytes must then agree mod this length, which rejects far more offsets than printability.
ciphertext_bNoA second ciphertext under the SAME key. Every hit is then a span of the other plaintext. Omit it to recover key bytes instead.
input_formatNoHow the ciphertexts are encoded. The crib is always literal text.Hex
printable_onlyNoReport only fully printable results. False when the plaintext is not text.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv3.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark the tool read-only and non-destructive; the description adds substantial behavioral detail beyond that: XOR cancels the key in two-ciphertext mode, periodicity modulo key_length is a stronger filter than printability, and full key recovery requires a crib at least as long as the key. No contradiction with 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 dense but efficient: three sentences front-load the core behavior, then explain the two modes and the key_length refinement. No filler or redundant restating of the tool name.

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?

The description covers the core algorithm, mode selection, key_length behavior, and key-recovery requirements. The only notable gap is the lack of an explicit output-shape description, such as how offsets and recovered key bytes are formatted, and no output schema exists to fill that gap.

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%, so the baseline is 3. The description adds meaning by explaining that ciphertext_b is only for the shared-key mode, key_length applies in single-ciphertext mode, and periodicity filtering is stronger than printable_only. This goes beyond the schema without repeating it.

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 names a specific technique and resource: dragging a guessed plaintext crib along XOR ciphertext and reporting ranked matching offsets. It also clearly distinguishes the two operating modes (two ciphertexts vs one), so an agent can tell it apart from generic CyberChef operations.

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 gives explicit mode-selection guidance: with two ciphertexts under the same key, use it to recover the other plaintext span; with one ciphertext, use it for key-byte recovery, and supply key_length to strengthen filtering. It does not explicitly name alternative sibling tools, but the specialized purpose and conditions are clear.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/doublegate/CyberChef-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server