Mmcp.market

Cyberchef MCP server

by doublegate·io.github.doublegate/cyberchef-mcp·v4.2.0
No reviews yet

CyberChef's 504 data-transformation operations as MCP tools: encryption, encoding, forensics.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

19 stars474 downloads/wk

Reviews

Write one

Nobody has reviewed Cyberchef yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cyberchef tools (13, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cyberchef_analysewrite action

    Run one of this server's analysis tools -- analyses a CyberChef operation

  • cyberchef_bakewrite action

    Execute a CyberChef recipe. Use this for complex chains of operations.

  • cyberchef_batchwrite action

    Execute multiple CyberChef operations in batch (parallel or sequential mode). Supports partial success.

  • cyberchef_cache_clear

    Clear the operation result cache.

  • cyberchef_cache_stats

    Get cache statistics including hits, misses, size, and items.

  • cyberchef_categories

    List CyberChef's operation categories with counts and examples.

  • cyberchef_describe_operation

    Full argument schema, defaults and types for one or more operations.

  • cyberchef_quota_info

    Get current resource quota information including concurrent operations and data sizes.

  • cyberchef_recipe_executewrite action

    Execute a saved recipe with input data.

  • cyberchef_recipe_export

    Export a recipe to various formats (json, yaml, url, cyberchef).

  • cyberchef_search

    Search for available CyberChef operations. Returns names and one-line summaries;

  • cyberchef_telemetry_export

    Export collected telemetry metrics. Returns anonymized usage statistics.

  • cyberchef_worker_stats

    Get worker thread pool statistics including thread count, utilization, and completed tasks. Only available when ENABLE_WORKERS=true.

Public scan report

scanner v0.1.8 · 2026-09-19 · same rubric, same numbers if you re-run it

2 medium
  • Code scan706 source files scanned15/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (2)

  • mediumnpm install lifecycle script presentinstall.script
  • mediumnpm install lifecycle script presentinstall.script
    package.json: … "lint:grammar": "cspell ./src", "postinstall": "node scripts/patch-dependencies.mjs", …
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Cyberchef repository's README, as published. We do not edit it. Read it on GitHub

CyberChef MCP Server

This project provides a Model Context Protocol (MCP) server interface for CyberChef, the "Cyber Swiss Army Knife" created by GCHQ.

By running this server, you enable AI assistants (like Claude, Cursor AI, and others) to natively utilize CyberChef's extensive library of 504 data manipulation operations—including encryption, encoding, compression, and forensic analysis—as executable tools.

Latest Release: v4.2.0 | Release Notes | Tutorial | Examples | Breaking Changes | Security Policy

Upstream base: GCHQ CyberChef v11.4.0 | Licence: GPL-3.0-or-later (from v2.0.0; v1.9.x and earlier remain Apache-2.0)

Project Context

CyberChef is a simple, intuitive web app for carrying out all manner of "cyber" operations within a web browser. It was originally conceived and built by GCHQ.

This fork wraps the core CyberChef Node.js API into an MCP server, bridging the gap between natural language AI intent and deterministic data processing.

Fork Relationship

This project maintains a selective sync relationship with the upstream GCHQ/CyberChef repository:

files in src/node/. Mirrored verbatim — never hand-edit them; fork changes live as re-applied patches.

  • Synced from upstream: src/core/** (minus three generated paths) and six upstream-owned

workflows)

  • Web UI Components: Removed (88 files, ~19,260 lines) — not needed for an MCP server
  • MCP-Specific Code: this fork's own (src/node/mcp-server.mjs, src/node/lib/**, tests/mcp/,

changes cannot be contributed back to an Apache-2.0 upstream.

  • Sync is one-way: pull only. As of v2.0.0 the combined work is GPL-3.0-or-later, so MCP-layer

Exact scope, the patch model, and what to do when a sync conflicts: Upstream Sync Guide.

See Upstream Sync Guide for details on the synchronization process.

Features

MCP Tools

The server exposes CyberChef operations as MCP tools:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-09-19restoreC → Bscore 77: npm install lifecycle script present; npm install lifecycle script present
  • 2026-09-19restoreF → Cscore 58: Base64 decoded then executed; npm install lifecycle script present; npm install lifecycle script present

Install directly

claude mcp add cyberchef-mcp -- docker run -i --rm ghcr.io/doublegate/cyberchef-mcp_v4:4.2.0
Add to Cursor

Cyberchef: common questions

Is Cyberchef MCP server safe?
Mostly: it is graded B (77/100). Read the Cyberchef safety report
How do I install Cyberchef?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Cyberchef need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cyberchef maintained?
The last commit was 7 days ago (2026-09-13). The latest release is v4.2.0.

More from doublegate →