Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

bytepeel

NPM · BYTEPEEL

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

Available components

67 Trust /100

Last scanned (18 hours ago)

Scores higher than 38% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security93
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 4 of 5 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 4 of 5 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability53
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.1.1 → 0.1.2 functional
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 50

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/bytepeel@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~932 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
peel ~496

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.

NameTypeReqDescription
altsinteger–Max interpretations kept per protobuf LEN field (default 3).
asstring–Force how the innermost decoded bytes are interpreted, when auto-detection picks wrongly.
depthinteger–Max nesting of layers and messages (default 16).
filestring–Path of a local file to read instead of input (binary files are fine).
formatstring–json (default); tree: a compact indented outline; raw: the selected item's payload bytes as lowercase hex (needs get).
getstring–Select one item by path and return only it.
instring–How to read the input (default auto). raw = the bytes as they are.
inputstring–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_itemsinteger–Max protobuf fields, CBOR/MessagePack values and DER elements decoded in total (default 1000000).
output_filestring–Write the result to this file instead of returning it. Fails if the file exists, unless overwrite is true.
overwriteboolean–Allow output_file to replace an existing file.

No output schema declared.

No examples provided.

set ~436

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.

NameTypeReqDescription
altsinteger–Max interpretations kept per protobuf LEN field (default 3).
asstring–Force how the innermost decoded bytes are interpreted, when auto-detection picks wrongly.
depthinteger–Max nesting of layers and messages (default 16).
editsarrayyesEdits, applied in order.
filestring–Path of a local file to read instead of input (binary files are fine).
instring–How to read the input (default auto). raw = the bytes as they are.
inputstring–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_itemsinteger–Max protobuf fields, CBOR/MessagePack values and DER elements decoded in total (default 1000000).
output_filestring–Write the result to this file instead of returning it. Fails if the file exists, unless overwrite is true.
overwriteboolean–Allow output_file to replace an existing file.

No output schema declared.

No examples provided.

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.

npm · bytepeel

# add to Claude Code
claude mcp add pinta365-bytepeel -- npx -y bytepeel mcp
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.