io.github.daedalus/mcp-reverse-engineering
PYPI · MCP-REVERSE-ENGINEERING
A sandboxed MCP tool for reverse engineering with multiple tool integrations
Available components
Last scanned (15 hours ago)
Scores higher than 80% of PyPI servers
Category Security
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency96
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to daedalus/mcp_reverse_engineering). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 208 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 940 tokens (~117/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed pypi/mcp-reverse-engineering@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | daedalus/mcp_reverse_engineering |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/daedalus/mcp_reverse_engineering/.github/workflows/pypi-publish.yml@refs/tags/v0.1.4 |
| Rekor log index | 1263854957 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:7344d8fa76422437819caf91f896257c0656cda76309b4414be511bd31b933fb |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
binwalk Binwalk ~139
Run binwalk to find embedded files and code in a binary. Binwalk is a tool for analyzing binary files to find embedded files and executable code. It uses entropy analysis and signature matching to identify compressed data, file systems, archives, and other embedded content.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to binwalk. Common options include: - -e: Extract found files automatically - -M: Enable signature matching - -B: Scan for common file signatures - -Y: Entropy analysis m… |
| file | – | – | Optional path to the file to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
file_cmd File Cmd ~122
Run the file command to determine file type. The file command performs a series of tests to identify the type of a file. It can detect file formats like ELF, PE, archives, images, and many others based on magic bytes and file structure.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to file command. Common options include: - -b: Brief output (don't show filename) - -z: Try to detect compressed files - -i: Output MIME type instead of human-readable |
| file | – | – | Optional path to the file to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
hexdump Hexdump ~121
Run hexdump on a file to display its contents in hexadecimal format. The hexdump utility displays the contents of a file in hex and ASCII, useful for analyzing binary file formats, identifying file headers, and inspecting raw file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to hexdump. Common options include: - -C: Canonical hex+ASCII output - -s OFFSET: Skip offset bytes from start - -n LENGTH: Only dump length bytes |
| file | – | – | Optional path to the file to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_tools List Tools ~41
List all available reverse engineering tools. This function returns a list of all tools that are currently enabled in the configuration and available for use through the MCP server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
objdump Objdump ~130
Run objdump to disassemble and analyze binary files. The objdump utility displays information about object files, including disassembly, symbol tables, section headers, and relocation information. Essential for reverse engineering and analyzing compiled binaries.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to objdump. Common options include: - -d: Disassemble executable sections - -t: Display symbol table - -h: Display section headers - -x: Display all available headers - -… |
| file | – | – | Optional path to the binary file to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
readelf Readelf ~139
Run readelf to display ELF binary information. The readelf utility displays information about ELF (Executable and Linkable Format) files, including headers, sections, symbols, dynamic linking information, and more. Specific to Linux/Unix ELF binaries.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to readelf. Common options include: - -h: Display ELF file header - -S: Display section headers - -s: Display symbol table - -d: Display dynamic section - -l: Display pro… |
| file | – | – | Optional path to the ELF file to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
strings Strings ~128
Run the strings command on a binary file to extract printable strings. The strings utility searches for printable strings in a binary file and outputs them. This is useful for extracting embedded strings, URLs, function names, and other text from compiled binaries.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to the strings command. Common options include: - -n MIN: Only print strings of length MIN or greater - -t FORMAT: Select output format (d, o, x) |
| file | – | – | Optional path to the file to analyze. If not provided, the file must be specified in args. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
xxd Xxd ~120
Run xxd on a file to create a hex dump. The xxd utility creates a hexadecimal representation of a file, similar to hexdump but with additional features like reverse conversion (hex to binary).
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Additional arguments to pass to xxd. Common options include: - -r: Reverse operation (hex to binary) - -p: Plain hex dump format - -s OFFSET: Skip offset bytes - -l LENGTH: Limit output to length byt… |
| file | – | – | Optional path to the file to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.daedalus/mcp-reverse-engineering server?
io.github.daedalus/mcp-reverse-engineering runs locally as a PyPI package, launched with uvx mcp-reverse-engineering. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-reverse-engineering
claude mcp add daedalus-mcp-reverse-engineering -- uvx mcp-reverse-engineering
What is the io.github.daedalus/mcp-reverse-engineering server?
io.github.daedalus/mcp-reverse-engineering is listed in the public MCP registry as io.github.daedalus/mcp-reverse-engineering. A sandboxed MCP tool for reverse engineering with multiple tool integrations. This page covers its PyPI package (mcp-reverse-engineering).
Is the io.github.daedalus/mcp-reverse-engineering server safe to use?
io.github.daedalus/mcp-reverse-engineering scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.daedalus/mcp-reverse-engineering server expose?
io.github.daedalus/mcp-reverse-engineering exposes 8 tools: strings, hexdump, xxd, file_cmd, objdump, and 3 more. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.
Is the io.github.daedalus/mcp-reverse-engineering server still maintained?
io.github.daedalus/mcp-reverse-engineering is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.daedalus/mcp-reverse-engineering server under?
io.github.daedalus/mcp-reverse-engineering declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.