io.github.daedalus/mcp-pwntools

Official registry Other

MCP server exposing pwntools 4.15.0 functionality for binary exploitation

What can you do with io.github.daedalus/mcp-pwntools?

  • Packing/Unpacking: p8, p16, p32, p64, u8, u16, u32, u64, flat
  • Assembly/Disassembly: asm, disasm
  • Shellcode Generation: shellcraft, shellcraft_setreuid, shellcraft_dupsh
  • ELF Manipulation: elf_load, elf_asm, elf_read, elf_write
  • Process Interaction: process_create, remote_connect, listen
  • ROP: rop_load, rop_call
  • Exploitation: fmtstr_payload, fmtstr_split
  • Utilities: hexdump, cyclic, cyclic_find, fit, enhex, unhex, context_set, context_get

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package mcp-pwntools
Claude Code
claude mcp add mcp-pwntools -- uvx mcp-pwntools==0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mcp-pwntools": {
            "command": "uvx",
            "args": [
                "mcp-pwntools==0.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-pwntools
  2. Install
  3. MCP Server
  4. Development
  5. mcp-name

mcp-pwntools

MCP server exposing pwntools 4.15.0 functionality for binary exploitation tasks.

Install

pip install mcp-pwntools

MCP Server

This package exposes pwntools functionality via the MCP (Model Context Protocol).

Tools

The server provides the following tool categories:

  • Packing/Unpacking: p8, p16, p32, p64, u8, u16, u32, u64, flat
  • Assembly/Disassembly: asm, disasm
  • Shellcode Generation: shellcraft, shellcraft_setreuid, shellcraft_dupsh
  • ELF Manipulation: elf_load, elf_asm, elf_read, elf_write
  • Process Interaction: process_create, remote_connect, listen
  • ROP: rop_load, rop_call
  • Exploitation: fmtstr_payload, fmtstr_split
  • Utilities: hexdump, cyclic, cyclic_find, fit, enhex, unhex, context_set, context_get
  • Logging: log_debug, log_info, log_success, log_warn, log_error
Resources
  • elf://<path> - Load ELF file information
  • context://settings - Get current pwntools context
Usage

Run the MCP server:

mcp-pwntools
Configuration (mcp.json)
{
  "mcpServers": {
    "pwntools": {
      "command": "mcp-pwntools",
      "env": {}
    }
  }
}

Development

git clone https://github.com/daedalus/mcp-pwntools.git
cd mcp-pwntools
pip install -e ".[test]"

# run tests
pytest

# format
ruff format src/ tests/

# lint
ruff check src/ tests/

# type check
mypy src/

mcp-name

mcp-name: io.github.daedalus/mcp-pwntools

Frequently asked questions

What is io.github.daedalus/mcp-pwntools?

MCP server exposing pwntools 4.15.0 functionality for binary exploitation

How do I install io.github.daedalus/mcp-pwntools?

It runs on your machine. In Claude Code: claude mcp add mcp-pwntools -- uvx mcp-pwntools==0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.daedalus/mcp-pwntools need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.daedalus/mcp-pwntools open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.daedalus/mcp-pwntools?

It is published by daedalus. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.