npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

pentester4codex

v0.2.4

Published

Expose PentestAgent tools over MCP stdio for Codex (requires GH05TCREW/pentestagent installed).

Readme

pentester4codex

MCP stdio server wrapper for PentestAgent tools. Props to GH05TCREW (MIT) for PentestAgent.

Original project:

https://github.com/GH05TCREW/pentestagent

What You Get

This package exposes PentestAgent tools over MCP stdio so any MCP client (like Codex) can call them. It does not install PentestAgent for you.

Prerequisites (Required)

  1. Python 3.10+
  2. PentestAgent installed (from GH05TCREW/pentestagent)

Install PentestAgent from source:

git clone https://github.com/GH05TCREW/pentestagent
cd pentestagent
python3 -m venv .venv
. .venv/bin/activate
python3 -m pip install -e ".[all]"

Verify:

. .venv/bin/activate
pentestagent --help

Install (This Package)

npm i -g pentester4codex

Verify:

pentester4codex --help

Start The MCP Server

pentester4codex --timeout 300

Optional:

  • --docker runs tools inside Docker (requires Docker).

Codex Setup (Plug‑In)

Recommended (Codex CLI):

codex mcp add pentester4codex /path/to/pentestagent/.venv/bin/python -m pentestagent.mcp.tools_server --timeout 300

Replace /path/to/pentestagent with your local clone. Example:

codex mcp add pentester4codex /Users/native/Desktop/coding/pentestagent-main/.venv/bin/python -m pentestagent.mcp.tools_server --timeout 300

Then restart Codex.

Alternate (Config File): create or update ~/.codex/mcp_servers.json:

{
  "mcpServers": {
    "pentester4codex": {
      "command": "/path/to/pentestagent/.venv/bin/python",
      "args": ["-m", "pentestagent.mcp.tools_server", "--timeout", "300"]
    }
  }
}

Restart Codex. You should now see tools from pentester4codex.

Troubleshooting

  • If Codex can’t find the server, confirm pentester4codex is on PATH:

    which pentester4codex
  • If tools fail, ensure pentestagent is installed:

    which pentestagent
  • If Codex reports an MCP handshake error, make sure you are not using --include-mcp when the server is listed inside the same MCP config. It can recurse and break startup. Use the exact CLI/config commands above.

Environment

  • PENTESTAGENT_MCP_EXCLUDE_TOOLS: comma-separated tool names to hide
  • PENTESTAGENT_WEBSEARCH_MCP_SERVER: forward web_search to an MCP server
  • PENTESTAGENT_WEBSEARCH_MCP_TOOL: tool name on that server (default: web_search)