Skip to content

binary-forensics MCP server

com.quickcoderhub/binary-forensicsquickcoderhub.comstreamable-httpv1.0.0Scanned

12 Binary/Forensics MCP tools: entropy triage, ELF/PE/WASM disasm, PCAP, EXIF, SQLite, ZIP.

12 tools: 2 can delete or cancel things, 2 change things and 8 only read.

Tools: 2 delete, 0 irreversible, 2 write, 8 read.
  • Reads private data · 9
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the binary-forensics MCP server can do

The binary-forensics MCP server is published by quickcoderhub.com, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (2 tools: archive_join_and_verify and archive_peek_central_dir) and create or change data (2 tools: disassemble_wasm_or_hex and hexdump_inspect). 8 tools only read.

9 tools read private data (binary_triage, executable_inspect, wasm_inspect and 6 more); 2 tools bring in text other people can write (wasm_inspect and pcap_inspect).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 2Claude Code: deny
  • archive_join_and_verifyStitch split multi-part archive chunks, detect magic file header, compute & verify SHA-256 checksum, and peek ZIP Central Directory entries.No findings

    Why it is in this group

    • The name "archive_join_and_verify" says "archive": a word for removing or ending something.
    Description, as the server wrote it
    Stitch split multi-part archive chunks, detect magic file header, compute & verify SHA-256 checksum, and peek ZIP Central Directory entries.
  • archive_peek_central_dirInspect ZIP Central Directory headers (filenames, compression method, CRC-32, sizes) or POSIX USTAR TAR entry headers without full extraction.No findings

    Why it is in this group

    • The name "archive_peek_central_dir" says "archive": a word for removing or ending something.
    Description, as the server wrote it
    Inspect ZIP Central Directory headers (filenames, compression method, CRC-32, sizes) or POSIX USTAR TAR entry headers without full extraction.
Changes things 2Claude Code: ask
  • disassemble_wasm_or_hexDisassemble WebAssembly (.wasm) bytecode into .wat text or decode x86-64, AArch64, and RISC-V machine code hex bytes.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Disassemble WebAssembly (.wasm) bytecode into .wat text or decode x86-64, AArch64, and RISC-V machine code hex bytes.
  • hexdump_inspectGenerate an annotated hex + ASCII dump of a binary range with Shannon entropy classification and multi-endian int/float data inspection at offset.Reads private dataNo findings

    Why it is in this group

    • The name "hexdump_inspect" says "inspect": a word for reading.
    • The description's first verb is "generate": a word for a change.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Generate an annotated hex + ASCII dump of a binary range with Shannon entropy classification and multi-endian int/float data inspection at offset.
Only reads 8Show 8 read-only tools
  • binary_triageInspect a binary for magic header signature, Shannon entropy (packing/encryption detection), UPX markers, and ASCII/UTF-16LE strings.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Inspect a binary for magic header signature, Shannon entropy (packing/encryption detection), UPX markers, and ASCII/UTF-16LE strings.
  • executable_inspectParse Linux ELF32/64, Windows PE32/PE32+, and macOS Mach-O / Universal binary headers, sections, entry points, and exploit mitigations (PIE, ASLR, NX, RELRO, CFG).Reads private dataNo findings

    Why it is in this group

    • The name "executable_inspect" says "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Parse Linux ELF32/64, Windows PE32/PE32+, and macOS Mach-O / Universal binary headers, sections, entry points, and exploit mitigations (PIE, ASLR, NX, RELRO, CFG).
  • exif_inspect_and_stripInspect JPEG APP1 EXIF/XMP/ICC segments for GPS coordinates, camera Make/Model, and timestamps, and optionally strip metadata cleanly.Reads private dataNo findings

    Why it is in this group

    • The name "exif_inspect_and_strip" says "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Inspect JPEG APP1 EXIF/XMP/ICC segments for GPS coordinates, camera Make/Model, and timestamps, and optionally strip metadata cleanly.
  • pcap_inspectParse libpcap (.pcap) packet capture headers and decode Ethernet, IPv4, TCP, UDP, and DNS/HTTP packet summaries.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "pcap_inspect" says "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Parse libpcap (.pcap) packet capture headers and decode Ethernet, IPv4, TCP, UDP, and DNS/HTTP packet summaries.
  • sourcemap_analyzeAudit a JavaScript SourceMap (.js.map) v3 JSON file to break down bundled byte attribution per source module and spot bloated dependencies.Reads private dataNo findings

    Why it is in this group

    • The name "sourcemap_analyze" says "analyze": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Audit a JavaScript SourceMap (.js.map) v3 JSON file to break down bundled byte attribution per source module and spot bloated dependencies.
  • sqlite_header_inspectInspect a SQLite3 database binary header (page size, schema cookie, encoding, WAL/journal version) and scan root B-tree SQL CREATE statements.Reads private dataNo findings

    Why it is in this group

    • The name "sqlite_header_inspect" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "inspect" and "database": it reads databases.
    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Inspect a SQLite3 database binary header (page size, schema cookie, encoding, WAL/journal version) and scan root B-tree SQL CREATE statements.
  • unicode_inspectInspect every Unicode code point in text for zero-width joiners, bidirectional Trojan Source overrides, homoglyph spoofing, and UTF-8/UTF-16 byte encodings.Reads private dataNo findings

    Why it is in this group

    • The name "unicode_inspect" says "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    Description, as the server wrote it
    Inspect every Unicode code point in text for zero-width joiners, bidirectional Trojan Source overrides, homoglyph spoofing, and UTF-8/UTF-16 byte encodings.
  • wasm_inspectInspect a WebAssembly (.wasm) binary module for sections, function signatures, imports, exports, and linear memory page allocations.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "wasm_inspect" says "inspect": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.filePath), and the tool reads: it reads files.
    • untrusted-inputThe description's first sentence says "inspect" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Inspect a WebAssembly (.wasm) binary module for sections, function signatures, imports, exports, and linear memory page allocations.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.quickcoderhub.com/mcp/binary-forensics: tools/list returned 12 tools to an anonymous client, including archive_join_and_verify (destructive), archive_peek_central_dir (destructive), disassemble_wasm_or_hex (write), hexdump_inspect (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http binary-forensics https://api.quickcoderhub.com/mcp/binary-forensics
claude mcp add --transport http binary-forensics https://api.quickcoderhub.com/mcp/binary-forensics

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__binary-forensics__binary_triage",
      "mcp__binary-forensics__executable_inspect",
      "mcp__binary-forensics__wasm_inspect",
      "mcp__binary-forensics__pcap_inspect",
      "mcp__binary-forensics__exif_inspect_and_strip",
      "mcp__binary-forensics__sqlite_header_inspect",
      "mcp__binary-forensics__sourcemap_analyze",
      "mcp__binary-forensics__unicode_inspect"
    ],
    "ask": [
      "mcp__binary-forensics__disassemble_wasm_or_hex",
      "mcp__binary-forensics__hexdump_inspect"
    ],
    "deny": [
      "mcp__binary-forensics__archive_join_and_verify",
      "mcp__binary-forensics__archive_peek_central_dir"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as binary-forensics. Review it before you use it.

Capability tags behind 9 rules
  • mcp__binary-forensics__binary_triage private-data
  • mcp__binary-forensics__executable_inspect private-data
  • mcp__binary-forensics__wasm_inspect private-data, untrusted-input
  • mcp__binary-forensics__hexdump_inspect private-data
  • mcp__binary-forensics__pcap_inspect private-data, untrusted-input
  • mcp__binary-forensics__exif_inspect_and_strip private-data
  • mcp__binary-forensics__sqlite_header_inspect private-data
  • mcp__binary-forensics__sourcemap_analyze private-data
  • mcp__binary-forensics__unicode_inspect private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.quickcoderhub/binary-forensics/verify?hash=501b988ac125565b5b9d555ff265f3e7314db193e747d7be2e356197bf680f66" | jq -e '.changed == false'

Pinned hash 501b988ac125, from Nov 19, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.quickcoderhub/binary-forensics/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.quickcoderhub/binary-forensics
[![Anlyon Radar](https://radar.anlyon.com/badge/com.quickcoderhub/binary-forensics.svg)](https://radar.anlyon.com/servers/com.quickcoderhub/binary-forensics)

Source: MCP Registry · repository. Synced Nov 19, 2026, 13:17 UTC.

binary-forensics MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the binary-forensics MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the binary-forensics MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: archive_join_and_verify and archive_peek_central_dir.

Can the binary-forensics MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the binary-forensics MCP server have?

12 tools: 2 destructive, 2 write, 8 read. archive_join_and_verify, archive_peek_central_dir, disassemble_wasm_or_hex, hexdump_inspect, binary_triage, executable_inspect, wasm_inspect, pcap_inspect and 4 more.

Does the binary-forensics MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the binary-forensics MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the binary-forensics MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.