Local Model Context Protocol (MCP) Server

Why MCP for Binary Data?

Large Language Models cannot reliably parse raw binary buffers injected directly into prompt context windows. Binary data consumes excessive tokens, triggers hallucinations, and risks encoding errors.

The Bitpeek Model Context Protocol (MCP) server solves this by exposing 12 structured inspection and transformation tools over local stdio transport.

The 12 Official Bitpeek MCP Tools

• bitpeek_capabilities: Returns supported schemas, limits, and format versions.
• bitpeek_open: Registers a local file within allowed roots and returns an opaque session handle.
• bitpeek_read: Reads bounded byte slices (default 4 KiB, max 64 KiB) as hex and ASCII.
• bitpeek_inspect: Decodes scalars, checksums, and hashes across a specific byte range.
• bitpeek_find: Searches for hex or text patterns with pagination cursors.
• bitpeek_strings: Extracts printable ASCII and UTF-16 text runs.
• bitpeek_structure: Returns parsed ELF, PNG, or schema trees with field coordinates.
• bitpeek_diff: Computes differences between two registered file sessions.
• bitpeek_verify_patch: Validates patch preconditions and cryptographic SHA-256 hashes.
• bitpeek_run_recipe: Executes multi-step declarative recipes with dry-run support.
• bitpeek_export: Writes modified binaries safely to allowed output directories.
• bitpeek_close: Closes session handles and frees system resources.

Security Sandbox & Containment

To protect the host system, McpSecurityManager enforces strict containment:

• Path Canonicalization: Resolves realpaths to block directory traversal and symlink escapes.
• Allowed Roots: Restricts file access strictly to operator-configured directory paths.
• Opaque Handles: Agents cannot inject raw filesystem paths into read/inspect tools; all access uses opaque handles (sess_<id>).
• Output Isolation: Exports cannot overwrite source files and are restricted to designated output directories.

Local processing and privacy

The MCP server workflow opens the same Bitpeek browser workspace. Selected file bytes, file names, pasted input, searches, edits, hashes, and comparison data are processed in local browser memory and are not sent to a Bitpeek server.

The static guide itself can be read without opening a file or creating an account.

Frequently asked questions