bytepeel
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
bytepeel
Peel layers of encoding off binary data. Built so that AI coding agents can call it instead of writing throwaway decoding scripts.
$ printf 'ChRTR1ZzYkc4c0lIZHZjbXhrSVNFPRAq' | bytepeel --format tree
base64(std,padded) [0..32] conf=0.85 -> 24 bytes
protobuf [0..24] conf=0.90
#1 LEN [0..22] len=20: string 0.95 "SGVsbG8sIHdvcmxkISE=" | packed_varint 0.03 | bytes 0.02
base64(std,padded) [0..20] conf=0.95 -> 14 bytes
utf8 [0..14] conf=1.00 "Hello, world!!"
#2 VARINT [22..24] uint=42 int=42 sint=21Recursive: base64 → protobuf → a string field that is base64 again → text, in one call.
Honest about ambiguity: each protobuf LEN field lists ranked interpretations (
message,string,packed_varint,bytes), and each varint shows itsuint,intandsintviews.Agent-friendly: compact JSON by default, byte ranges on everything, 64-bit integers as strings (safe for jq and JavaScript), and errors as
{"error":{"code","message","offset"}}with stable codes.Zero-dependency core (
bytepeel-core; gzip/zstd are opt-in features) and a single static binary.
Install
npx bytepeel --help # the CLI and MCP server, no install needed
npm install -g bytepeel # or install it (Node 18+)
cargo install bytepeel # or build it (Rust 1.87+)The npm package runs the same native binary as the others. Prebuilt binaries for Linux (static), macOS and Windows are attached to each
GitHub release. For
JavaScript, use npm install bytepeel or deno add jsr:@pinta365/bytepeel
(see npm/README.md), and for Rust, the
bytepeel-core crate.
For Claude Code, the plugin adds a skill that makes Claude reach for bytepeel on its own, plus the MCP server.
Related MCP server: Delx Agent Utilities
Supported formats
Layer | Notes |
hex | whitespace, |
hex dumps |
|
base64 | standard and URL-safe alphabets, padded and unpadded, line-wrapped |
PEM | any label; RFC 1421 headers skipped; multiple blocks (chain, key + cert) become a |
JWT | JWS (3 parts) and JWE (5 parts); each part decoded, and |
protobuf | schemaless; groups, negative varints, fixed32/64 as int and float |
DER / ASN.1 | X.509, PKCS, CMS; ~175 named OIDs, ISO times, any-width integers, DER nested in BIT/OCTET STRINGs decoded in place |
CBOR | RFC 8949: maps, arrays, tags (epoch → ISO-8601, bignums, uuid), indefinite lengths, half/single/double floats; |
MessagePack | maps, arrays, str/bin, int64/uint64, float32/64, ext (timestamp type -1 → ISO-8601 with nanoseconds); |
utf8 / bytes | leaves |
gzip, zlib, zstd | checksum-verified, multi-member/frame, 64 MiB output cap (optional core features |
PNG, zip | recognized by magic bytes (not decoded) |
Usage
bytepeel [OPTIONS] [FILE] # stdin when FILE is omitted or '-'
--in <auto|hex|base64|raw> how to read the input (default: auto)
--as <protobuf|der|cbor|msgpack|text|bytes>
force interpretation of the decoded bytes
--depth <N> max nesting (default 16)
--alts <N> interpretations kept per LEN field (default 3)
--max-items <N> max fields/values/elements decoded in total (default 1000000)
--get <PATH> protobuf: field numbers, e.g. 1.3[2].4
DER: 0-based child indices, e.g. 0.0.6
PEM bundle: first index picks the block, e.g. 1.0.0.5
CBOR/MessagePack: map keys / array indices, e.g. users.0.name
JWT: part, then JSON keys, e.g. payload.sub, header.alg
JSON text (decoded, or in a string): keys, e.g. users.37.id
paths cross formats: 2.0.0.5 = a cert's subject in
protobuf field 2 (base64, PEM or raw DER)
--format <json|tree|raw> raw writes a --get selection's payload bytesEditing: bytepeel set
Change, add and remove protobuf fields, CBOR/MessagePack values and DER
elements, and get the data back in the same outer format, with every other
byte preserved. PATH=VALUE changes, PATH+=VALUE adds, --del PATH
removes:
$ echo '1a 03 08 96 01' | bytepeel set 3.1=300000
1a 04 08 e0 a7 12
$ base64 -w0 msg.pb.gz | bytepeel set 2='"new name"' 3=sint:-5 > edited.b64
$ bytepeel set users.0.active=false ttl=null 'tags.0+="new"' --del legacy record.cbor > edited.cbor
$ echo '08 96 01 12 03 66 6f 6f' | bytepeel set 3+=42 --del 2
08 96 01 18 2a
$ bytepeel set '0.0.5.2.0.1="Test Root"' '0.0.4.1="2045-06-07T08:09:10Z"' ca.pem > test-ca.pem
$ echo 'a1 61 70 43 08 96 01' | bytepeel set p.1=300 'p.2+="hi"' # protobuf in a CBOR byte string
a1 61 70 47 08 ac 02 12 02 68 69Paths cross formats as --get paths do: 2.0.0.5.2.0.1='"Test Root"'
changes the common name of a base64 certificate in protobuf string field 2,
and both the certificate's base64 and the protobuf around it are re-encoded.
Editing a certificate invalidates its signature; that's fine for test fixtures, and you re-sign it if it must verify.
Hex keeps its spacing and case, base64 its alphabet and line width, PEM its
label, gzip its header. Values: 42, sint:-2, 1.5, true, null,
"text", hex:0a0b, b64:CgM=. The output is decoded again and checked before it is
written (REENCODE_VERIFY_FAILED otherwise).
Exit codes: 0 success, 1 decode error, 2 usage or I/O error.
$ echo '10 fe ff ff ff ff ff ff ff ff 01' | bytepeel
{"codec":"hex",…,"child":{"codec":"protobuf",…,"fields":[{"field":2,"wire":"VARINT","range":[0,11],"uint":"18446744073709551614","int":"-2","sint":"9223372036854775807"}]}}
$ echo 1a03089601 | bytepeel --get 3.1 --format raw | xxd
00000000: 9601
$ bytepeel cert.pem --get 0.0.4 --format tree # X.509 validity
SEQUENCE [124..156]
UTCTime [126..141] 2020-09-04T00:00:00Z
UTCTime [141..156] 2040-09-17T16:00:00Z
$ bytepeel record.cbor --get tags.1 --format raw # a CBOR map value
b
$ echo "$TOKEN" | bytepeel --get payload.sub --format raw # a JWT claim
1234567890See docs/DESIGN.md for the full JSON schema, paths, heuristics and error codes.
MCP server
bytepeel mcp runs a Model Context Protocol
server on stdio, so an agent can call bytepeel as a tool. It's built into the
same binary. For example, in Claude Code:
claude mcp add bytepeel -- npx -y bytepeel mcp # or: -- bytepeel mcp, if installedOther clients take the same command in their JSON config:
{ "mcpServers": { "bytepeel": { "command": "npx", "args": ["-y", "bytepeel", "mcp"] } } }It's listed in the MCP Registry as
io.github.Pinta365/bytepeel.
It offers two tools:
peeldecodesinput(text) orfile(a path), with optionalget,format(json,tree, orraw, which returns the payload as hex) and the CLI's options (in,as,depth,alts,max_items).setappliesedits([{"op":"set","path":"3.1","value":"300"}];opcan also beaddordel) and returns the re-encoded data. Text comes back as text and binary data as hex. Passoutput_fileto write the result instead; an existing file is replaced only withoverwrite: true.
Errors come back as tool results with isError: true and the same
{"error":{...}} JSON the CLI prints.
Claude Code plugin and agent skill
The repo is also a Claude Code plugin marketplace. The bytepeel plugin
bundles a skill that tells Claude to use bytepeel (rather than decoding bytes
by eye or writing a script) whenever it meets hex, base64, PEM, JWTs or binary
data, together with the MCP server above (started with npx -y bytepeel mcp, so it needs Node.js 18+ and nothing else).
/plugin marketplace add Pinta365/bytepeel
/plugin install bytepeel@bytepeelThe skill is a plain SKILL.md
folder, so other agents that read Agent Skills can use it too: copy
plugins/bytepeel/skills/bytepeel/ into their skills directory.
JavaScript / WebAssembly
npm/ is a WebAssembly build with a small JS wrapper (Node, Deno, Bun,
browsers; no dependencies):
import { load } from "bytepeel";
const bp = await load();
bp.get(pem, "0.0.5.2.0.1").value; // "ISRG Root X2"
bp.edit(hex, [{ set: "3.1", value: 300000 }]);See npm/README.md.
Development
cargo test --workspace
cargo clippy --workspace --all-targets -- -D warnings
cargo build --release # target/release/bytepeel
cd npm && npm run build && npm test # WebAssembly build and JS testsLicense
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Exact hashing, base64/hex/URL encoding, JWT decoding and UUIDs for AI agents. No auth required.
500+ deterministic tools for AI agents: math, conversion, validation, hashing, encoding, date/time.
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
Dev utilities for agents: JSON/YAML/CSV, schema validation, encoding, text & time. Free, no key.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to safely decode and inspect JWT tokens and Base64 payloads in real-time.7 npm3-
- AlicenseCqualityBmaintenanceStateless URL, DNS, x402, JWT, encoding, and parsing tools for AI agents.4486 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceExposes hundreds of CyberChef data operations as tools for LLM agents to perform encoding, decoding, hashing, compression, encryption, and data format conversion.-
- AlicenseAqualityBmaintenanceEnables AI agents to run multi-stage CyberChef recipes, decode and encode data, deobfuscate payloads, calculate entropy, and decode JWTs through MCP tools.1876 npm3Apache 2.0