Chepy MCP Service (CyberChef like Python library)

Created By
nebucaza year ago
This project exposes the powerful Chepy data transformation library as an MCP server. It allows you to access Chepy's tools (like encoding, decoding, and data manipulation) via a single flexible API: the bake pipeline tool, inspired by CyberChef.
Overview

What is Chepy MCP Service (CyberChef-like Python library)

This MCP Servic exposes the powerful Chepy data transformation library as an MCP server. It allows you to access Chepy's tools (like encoding, decoding, and data manipulation) via a single flexible API: the bake pipeline tool, inspired by CyberChef.

How to use Chepy MCP Service (Python chepy)?

Clone the repository, install the dependencies, and start the server/integrate with your favourite LLM.

Key features of MCP OpenMemory Server?

  • Single bake() function allows to chain multiple operations
  • Discovery of available operations and parameters

Use cases of MCP OpenMemory Server?

  • Encode/decode Binary Strings (e.g. base64, base58, base45)
  • Encryption/decryption (e.g. ROT13, AES)
  • Chain multiple operations (bake a recipe)

FAQ

What operations are supported within the bake() function?

Get the list of supported functions by interrogating the get_chepy_operations() endpoint.

Server Config

{
  "mcpServers": {
    "chepy-mcp": {
      "command": "/Users/username/.local/bin/uv",
      "args": [
        "--directory",
        "/Users/username/chepy-mcp",
        "run",
        "src/server.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nebucaz
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago