# bytepeel (npm · bytepeel)

Decode and edit hex, base64, PEM, JWT, gzip, DER, CBOR, MessagePack and protobuf data byte-exactly.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `bytepeel`: 67/100 (this document), [markdown](https://verifymcp.io/servers/pinta365-bytepeel/bytepeel.md), [page](https://verifymcp.io/servers/pinta365-bytepeel/bytepeel)

## Channel facts

- Registry: `npm`
- Package: `bytepeel`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 93/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 4 of 5 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 4 of 5 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 53/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1048 tokens (~524/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the bytepeel MCP server?

bytepeel runs locally as an npm package, launched with npx -y bytepeel mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pinta365-bytepeel -- npx -y bytepeel mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pinta365-bytepeel": {
      "command": "npx",
      "args": [
        "-y",
        "bytepeel",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pinta365-bytepeel": {
      "command": "npx",
      "args": [
        "-y",
        "bytepeel",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pinta365-bytepeel -- npx -y bytepeel mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pinta365-bytepeel": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "bytepeel",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pinta365-bytepeel --command npx --arg -y --arg bytepeel --arg mcp
```

### Hermes

```yaml
mcp_servers:
  pinta365-bytepeel:
    command: "npx"
    args: ["-y", "bytepeel", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pinta365-bytepeel": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "bytepeel",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pinta365-bytepeel -t stdio -c npx -a -y bytepeel mcp
```

### Other

```json
{
  "mcpServers": {
    "pinta365-bytepeel": {
      "command": "npx",
      "args": [
        "-y",
        "bytepeel",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 65, 0)

- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-11-16 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 50)

First indexed and scored.

## MCP tools (2)

### `peel` (~496 tokens)

Decode data

Decode data byte-exactly through every layer (hex, base64, PEM, JWT, dumps, gzip/zlib/zstd, DER/ASN.1, CBOR, MessagePack, schemaless protobuf) and return a JSON tree with byte ranges. Ambiguous protobuf LEN fields list ranked alternatives (message, string, bytes, packed); 64-bit integers are JSON strings. Long text and bytes are previewed ("truncated":true); use get with format raw for a full payload. Paths: protobuf field numbers (1.3[2].4: the third field 3 of message 1), DER child indices (0.0.5), a PEM bundle's block index first, CBOR/MessagePack map keys and array indices (users.0.name), a JWT part then JSON keys (payload.sub), JSON keys and indices inside decoded JSON text (users.37.id). Paths cross formats: 2.0.0.5 is the subject of a certificate (base64, PEM or raw DER) held in protobuf field 2.

Input parameters:

- `alts` (integer): Max interpretations kept per protobuf LEN field (default 3).
- `as` (string): Force how the innermost decoded bytes are interpreted, when auto-detection picks wrongly.
- `depth` (integer): Max nesting of layers and messages (default 16).
- `file` (string): Path of a local file to read instead of input (binary files are fine).
- `format` (string): json (default); tree: a compact indented outline; raw: the selected item's payload bytes as lowercase hex (needs get).
- `get` (string): Select one item by path and return only it.
- `in` (string): How to read the input (default auto). raw = the bytes as they are.
- `input` (string): The data as text: hex, base64, PEM, a JWT, an xxd or hexdump -C dump, or any nesting of these. Give either input or file.
- `max_items` (integer): Max protobuf fields, CBOR/MessagePack values and DER elements decoded in total (default 1000000).
- `output_file` (string): Write the result to this file instead of returning it. Fails if the file exists, unless overwrite is true.
- `overwrite` (boolean): Allow output_file to replace an existing file.

### `set` (~436 tokens)

Edit and re-encode data

Change, add or remove values and get the data back in its original encoding (hex spacing, base64 alphabet and wrapping, PEM label, gzip header), with every other byte preserved. Edits apply in order; the result is decoded again and checked (REENCODE_VERIFY_FAILED otherwise). Editing signed data (a certificate) invalidates its signature; JWTs are not editable. Paths: protobuf field numbers (1.3[2].4: the third field 3 of message 1), DER child indices (0.0.5), a PEM bundle's block index first, CBOR/MessagePack map keys and array indices (users.0.name), a JWT part then JSON keys (payload.sub), JSON keys and indices inside decoded JSON text (users.37.id). Paths cross formats: 2.0.0.5 is the subject of a certificate (base64, PEM or raw DER) held in protobuf field 2.

Input parameters:

- `alts` (integer): Max interpretations kept per protobuf LEN field (default 3).
- `as` (string): Force how the innermost decoded bytes are interpreted, when auto-detection picks wrongly.
- `depth` (integer): Max nesting of layers and messages (default 16).
- `edits` (array, required): Edits, applied in order.
- `file` (string): Path of a local file to read instead of input (binary files are fine).
- `in` (string): How to read the input (default auto). raw = the bytes as they are.
- `input` (string): The data as text: hex, base64, PEM, a JWT, an xxd or hexdump -C dump, or any nesting of these. Give either input or file.
- `max_items` (integer): Max protobuf fields, CBOR/MessagePack values and DER elements decoded in total (default 1000000).
- `output_file` (string): Write the result to this file instead of returning it. Fails if the file exists, unless overwrite is true.
- `overwrite` (boolean): Allow output_file to replace an existing file.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pinta365-bytepeel/bytepeel#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 66
- 2026-11-18: 66
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 50

## Common questions

### What is the bytepeel MCP server?

bytepeel is an MCP server listed in the public MCP registry as io.github.Pinta365/bytepeel. Decode and edit hex, base64, PEM, JWT, gzip, DER, CBOR, MessagePack and protobuf data byte-exactly. This page covers its npm package (bytepeel).

### Is the bytepeel MCP server safe to use?

bytepeel scores 67 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the bytepeel MCP server expose?

bytepeel exposes 2 tools: peel, set. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.

### Is the bytepeel MCP server still maintained?

bytepeel is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the bytepeel MCP server under?

bytepeel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the bytepeel MCP server?

VerifyMCP ran 16 checks on bytepeel, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/bytepeel
- Socket report: https://socket.dev/npm/package/bytepeel
- Repository: https://github.com/Pinta365/bytepeel
- Changelog RSS feed: https://verifymcp.io/servers/pinta365-bytepeel/bytepeel.xml
- Changelog JSON feed: https://verifymcp.io/servers/pinta365-bytepeel/bytepeel/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pinta365-bytepeel/bytepeel.json
- HTML version of this page: https://verifymcp.io/servers/pinta365-bytepeel/bytepeel
