Skip to content

pentest-mcp-server

io.github.cyanheads/pentest-mcp-servercyanheadsstreamable-httpv0.3.1Scanned

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

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change 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 pentest-mcp-server can do

The pentest-mcp-server is published by the GitHub account cyanheads. It has 7 tools. It can create or change data (3 tools: pentest_map_techniques, pentest_generate_payloads and pentest_encode_payload), but cannot delete data. 4 tools only read.

1 tool brings in text other people can write (pentest_analyze_response).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.3.1.

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.

7 tools

Changes things 3Claude Code: ask
  • pentest_encode_payloadTransform a payload string through an ordered encoding chain for authorized filter research.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Transform a payload string through an ordered encoding chain for authorized filter research. Results include the final value, intermediate values, optional decode path and rationale, and detection guidance. All transforms are local; no live probing occurs.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • pentest_generate_payloadsGenerate context-specific payload templates for authorized systems.1 finding

    Why it is in this group

    • The name "pentest_generate_payloads" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "pentest_generate_payloads" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "pentest_generate_payloads" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Generate context-specific payload templates for authorized systems. Each template includes its vulnerability category, context rationale, WAF/IDS detection signature, mitigation, optional WAF research note, and optional encoded variant.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • pentest_map_techniquesRank ATT&CK techniques and OWASP test cases against an authorized target profile of technology stack, exposed services, authentication type, and operating system.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Rank ATT&CK techniques and OWASP test cases against an authorized target profile of technology stack, exposed services, authentication type, and operating system. Results include profile-specific relevance, detection opportunities, mitigations, and associated methodology vectors.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
Only reads 4Show 4 read-only tools
  • pentest_analyze_responseAnalyze an HTTP response from authorized probing for information leakage, fingerprinting signals, and related exposure.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "analyze" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Analyze an HTTP response from authorized probing for information leakage, fingerprinting signals, and related exposure. Structured findings cover version disclosures, stack traces, debug headers, internal paths, authentication patterns, CORS configuration, detection signals, remediation, and associated methodology vectors.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • pentest_get_guideReturn an authorized-testing methodology for a selected vector and optional target context.No findings

    Why it is in this group

    • The name "pentest_get_guide" says "get": a word for reading.
    Description, as the server wrote it
    Return an authorized-testing methodology for a selected vector and optional target context. The playbook covers reconnaissance, enumeration, exploitation, and post-exploitation phases with objectives, techniques, detection signals, mitigations, common pitfalls, references, and context-derived tool suggestions across 15 vectors.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • pentest_lookup_groupLook up a MITRE ATT&CK threat group or software entry by ID, name, or keyword.No findings

    Why it is in this group

    • The name "pentest_lookup_group" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up a MITRE ATT&CK threat group or software entry by ID, name, or keyword. Results include ATT&CK identity, aliases, type, description, and associated techniques with procedure-level context from public ATT&CK reporting.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • pentest_lookup_techniqueLook up a MITRE ATT&CK technique by exact ID or keyword.No findings

    Why it is in this group

    • The name "pentest_lookup_technique" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up a MITRE ATT&CK technique by exact ID or keyword. Results include tactics, platforms, description, detection data, public procedure examples, mitigations, related sub-techniques, and dataset version.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true

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 private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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 20, 2026, 19:34 UTC, unchanged since Oct 22, 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
3
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
  • WarnThe whole server

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

    Matched text

    https://pentest.caseyjhand.com/mcp: tools/list returned 7 tools to an anonymous client, including pentest_map_techniques (write), pentest_generate_payloads (write), pentest_encode_payload (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "pentest_generate_payloads" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "pentest_generate_payloads" says "generate": a word for a change.

    What this check looks for

History

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

  1. Tools2 changed.~2 changedView diff

Install

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

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

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__pentest__pentest_get_guide",
      "mcp__pentest__pentest_analyze_response",
      "mcp__pentest__pentest_lookup_technique",
      "mcp__pentest__pentest_lookup_group"
    ],
    "ask": [
      "mcp__pentest__pentest_map_techniques",
      "mcp__pentest__pentest_generate_payloads",
      "mcp__pentest__pentest_encode_payload"
    ],
    "deny": []
  }
}

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 pentest. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pentest__pentest_analyze_response untrusted-input

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/io.github.cyanheads/pentest-mcp-server/verify?hash=9c374113c9381acd7fadbe3348dc48529850a5a32d6b140c80f20c23acb22466" | jq -e '.changed == false'

Pinned hash 9c374113c938, from Nov 21, 2026, 16:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.cyanheads/pentest-mcp-server/changes.xml

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

Badge

Anlyon Radar badge for io.github.cyanheads/pentest-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/pentest-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/pentest-mcp-server)

Source: MCP Registry · repository. Synced Nov 21, 2026, 16:17 UTC.

pentest-mcp-server: questions and answers

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

Is the pentest-mcp-server safe?

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

Can the pentest-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the pentest-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 pentest-mcp-server have?

7 tools: 3 write, 4 read. pentest_map_techniques, pentest_generate_payloads, pentest_encode_payload, pentest_get_guide, pentest_analyze_response, pentest_lookup_technique and pentest_lookup_group.

Does the pentest-mcp-server need sign-in or OAuth?

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

Does the pentest-mcp-server send data to outside services?

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

Has the pentest-mcp-server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.