Ext Ops Panel
Open dashboard
Comparison

io.github.cyanheads/pentest-mcp-server vs io.github.mrfentmen/pawn-mcp

io.github.cyanheads/pentest-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.mrfentmen/pawn-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.cyanheads/pentest-mcp-serverio.github.mrfentmen/pawn-mcp
Official MCP Registry Listed
Version: 0.3.0
Downloads/month (npm): 1 297
Downloads/week (npm): 228
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.3.0
Downloads/month (npm): 1 297
Downloads/week (npm): 228
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.cyanheads/pentest-mcp-server vs io.github.mrfentmen/pawn-mcp
Factio.github.cyanheads/pentest-mcp-serverio.github.mrfentmen/pawn-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-30Not published
Where it runs (differs)Remote server or your machineOn your machine (@mrfentmen/pawn-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)7, secrets among them: 0Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/cyanheads/pentest-mcp-servergithub.com/mrfentmen/awesome-servers
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-08
Endpoint at the last check (differs)Status out of date: last check 35 h ago returned HTTP 200no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.cyanheads/pentest-mcp-server

In its own words, on Official MCP Registry:

Offline methodology engine for authorized penetration testing, CTF, and security research.

io.github.mrfentmen/pawn-mcp

In its own words, on Official MCP Registry:

Pawn MCP: 20 real tools to read, check, lint, scaffold, build and run Pawn code.

How to run each

io.github.cyanheads/pentest-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http pentest-mcp-server https://pentest.caseyjhand.com/mcp

io.github.mrfentmen/pawn-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pawn-mcp -- npx -y @mrfentmen/pawn-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.cyanheads/pentest-mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.mrfentmen/pawn-mcp nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.mrfentmen/pawn-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.cyanheads/pentest-mcp-server · What it can do: io.github.mrfentmen/pawn-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built