Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/pentest-mcp-server

REMOTE · PENTEST.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 20

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

Available components

remote · pentest.caseyjhand.com 81 npm · @cyanheads/pentest-mcp-server 43
0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1210 tokens (~172/item across 7 items; 7 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 7 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
Install

How do I install the io.github.cyanheads/pentest-mcp-server server?

io.github.cyanheads/pentest-mcp-server is a hosted endpoint at https://pentest.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pentest.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-pentest-mcp-server 'https://pentest.caseyjhand.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cyanheads-pentest-mcp-server": {
      "url": "https://pentest.caseyjhand.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyanheads-pentest-mcp-server": {
      "type": "http",
      "url": "https://pentest.caseyjhand.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cyanheads-pentest-mcp-server]
url = "https://pentest.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-pentest-mcp-server": {
      "type": "remote",
      "url": "https://pentest.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-pentest-mcp-server --url 'https://pentest.caseyjhand.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-pentest-mcp-server:
    url: "https://pentest.caseyjhand.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyanheads-pentest-mcp-server": {
      "Transport": "http",
      "Url": "https://pentest.caseyjhand.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cyanheads-pentest-mcp-server -t streamable-http -u 'https://pentest.caseyjhand.com/mcp'
// mcp.json
{
  "mcpServers": {
    "cyanheads-pentest-mcp-server": {
      "type": "http",
      "url": "https://pentest.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 0
    • Server version: 0.1.8 → 0.1.9 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Aug 26 79
    • Tool “pentest_map_techniques” rewrote its description, which is the text the model reads security
    • Tool “pentest_lookup_technique” rewrote its description, which is the text the model reads security
    • Tool “pentest_lookup_group” rewrote its description, which is the text the model reads security
    • Tool “pentest_guide” rewrote its description, which is the text the model reads security
    • Tool “pentest_generate_payloads” rewrote its description, which is the text the model reads security
    • Tool “pentest_encode” rewrote its description, which is the text the model reads security
    • Tool “pentest_analyze_response” rewrote its description, which is the text the model reads security
    • Schema quality: 256 → 172 ▲ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.1.6 → 0.1.8 functional
    • “pentest_analyze_response” reworded the description of “response_headers” cosmetic
    • “pentest_guide” reworded the description of “phase” cosmetic
    • “pentest_generate_payloads” reworded the description of “encoding” cosmetic
    • “pentest_encode” reworded the description of “explain” cosmetic
    • “pentest_analyze_response” reworded the description of “response_body” cosmetic
Diagnostics

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 20 Sept 2026 · Probed https://pentest.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 a6985204ed51ae050e7738aa6be668e9
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of pentest.caseyjhand.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
pentest.caseyjhand.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pentest.caseyjhand.com/mcp Verified 200
http (plaintext) http://pentest.caseyjhand.com/mcp HTTPS enforced 301 https://pentest.caseyjhand.com/mcp
MCP tools · 7 exposed · ~1,139 tokens

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 →

Tool Tokens
pentest_analyze_response ~183

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.

NameTypeReqDescription
contextstring–Freeform context about the authorized test target — e.g., "login endpoint", "GraphQL API", "file upload handler". Narrows the pattern matching to relevant categories. Max 2,000 characters.
response_bodystring–Raw HTML, JSON, XML, or error response body text. Maximum 10,000 characters.
response_headersstring–Raw HTTP response headers, optionally including the status line. Maximum 20,000 characters.
status_codeinteger–HTTP status code (100–599). Helps classify the response type.
NameTypeReqDescription
authorized_use_reminderstring–Reminder that response analysis is for authorized testing only. Rendered first.
errorobject–Present when the call failed. Absent on success.
findingsarray–Structured findings ordered by severity descending (high first).
fingerprintsobject–Detected server, framework, language, database, cloud, and other technology signals.
nextToolSuggestionsarray–Suggested tools derived from detected fingerprints and findings.
summarystring–One-paragraph summary of findings and associated follow-up actions.

No examples provided.

pentest_encode ~133

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.

NameTypeReqDescription
chainarrayyesOrdered list of encodings to apply (1–6 steps). Applied left to right. E.g., ["unicode", "url"] applies Unicode escape first, then URL-encodes the result.
explainboolean–Whether to include the decode path and bypass rationale.
payloadstringyesInput payload string to encode. Max 10,000 characters.
NameTypeReqDescription
authorized_use_reminderstring–Reminder that encoding transforms are for authorized bypass research only.
bypass_rationalestring–Why this encoding combination might bypass common filter patterns. Included when explain is true.
decode_pathstring–Step-by-step explanation of how a decoder (WAF, server, browser) would reverse the encoding chain. Included when explain is true.
detection_notestring–Detection methods for encoded variants, including normalization and behavior signals.
encodedstring–Final encoded payload after all chain steps applied.
errorobject–Present when the call failed. Absent on success.
intermediate_stepsarray–Intermediate values at each encoding step, for tracing the chain.
originalstring–The input payload.

No examples provided.

pentest_generate_payloads ~187

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.

NameTypeReqDescription
categorystringyesVulnerability category for payload generation.
countinteger–Number of payload variants to return (1–20, default 5). More variants cover different bypass approaches for the same context.
encodingarray–Optional encoding chain applied left to right to each returned template.
injection_contextstringyesPrecise injection context. Critical for XSS: an HTML attribute payload differs from a JS string payload. Provide the most specific context for the best results.
waf_profilestring–WAF or filter in front of the authorized test target. When a specific WAF is named, bypass variants referencing known public research are included.
NameTypeReqDescription
authorized_use_reminderstring–Reminder that these templates are for authorized testing only.
categorystring–Requested payload category.
errorobject–Present when the call failed. Absent on success.
injection_contextstring–Requested injection context.
payloadsarray–Payload templates ordered by coverage breadth, each annotated with offense and defense context.

No examples provided.

pentest_guide ~153

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.

NameTypeReqDescription
phasestring–Methodology phase selector. "all" returns the complete playbook; a named phase returns only that phase.
target_contextobject–Optional target profile for authorized engagement. Providing this narrows the playbook to what is most relevant for the specific environment.
vectorstringyesAttack vector to retrieve methodology for. Each vector has its own methodology branch covering recon through exploitation. Authorized testing only.
NameTypeReqDescription
attack_technique_idsarray–Relevant ATT&CK technique IDs for cross-referencing with pentest_lookup_technique.
authorized_use_reminderstring–Reminder that this methodology applies to authorized testing only. Included in every response.
errorobject–Present when the call failed. Absent on success.
nextToolSuggestionsarray–Suggested tools and arguments derived from the playbook.
owasp_referencesarray–Relevant OWASP Testing Guide test case IDs (e.g., "WSTG-INPV-01").
phasesarray–Ordered methodology phases. Contains only the requested phase when phase input is not "all".
vectorstring–The requested attack vector.

No examples provided.

pentest_lookup_group ~131

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.

NameTypeReqDescription
querystringyesATT&CK threat group ID (e.g., "G0007"), software ID (e.g., "S0002"), or name/keyword (e.g., "APT28", "Mimikatz", "Lazarus Group"). ID lookup is exact and case-insensitive; name/keyword search returns…
NameTypeReqDescription
aliasesarray–Known alternate names from ATT&CK.
attack_versionstring–ATT&CK dataset version used (e.g., "Enterprise v19.1").
authorized_use_reminderstring–Reminder that threat group data is for authorized testing and research only. Rendered first.
descriptionstring–ATT&CK description (truncated to 800 characters).
errorobject–Present when the call failed. Absent on success.
idstring–ATT&CK ID (e.g., "G0007" for a group, "S0002" for software).
namestring–Primary display name (e.g., "APT28", "Mimikatz").
techniques_usedarray–Up to 20 techniques associated with the group or software, including procedure-level context and technique IDs.
typestring–"group" for intrusion sets (threat actors), "software" for malware and tools.

No examples provided.

pentest_lookup_technique ~148

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.

NameTypeReqDescription
include_subtechniquesboolean–Include sub-techniques in the result. Set to false when only the parent technique summary is needed.
querystringyesATT&CK technique ID (e.g., "T1190", "T1059.001") or keyword describing the technique (e.g., "sql injection", "pass the hash", "web shell upload"). ID lookup is exact; keyword lookup returns the best…
NameTypeReqDescription
attack_versionstring–ATT&CK dataset version used (e.g., "Enterprise v19.1").
authorized_use_reminderstring–Reminder that technique data is for authorized testing and research only. Rendered first.
descriptionstring–ATT&CK description of the technique.
detectionobject–ATT&CK detection context for the technique.
errorobject–Present when the call failed. Absent on success.
mitigationsarray–Recommended mitigations from ATT&CK.
namestring–Technique name.
platformsarray–Target platforms (e.g., "Windows", "Linux", "Web Application").
procedure_examplesarray–Real-world usage examples from ATT&CK public reporting.
sub_techniquesarray–Sub-techniques of this parent technique. Empty when querying a sub-technique itself, or when include_subtechniques is false.
tacticsarray–ATT&CK tactics this technique belongs to (e.g., "Initial Access", "Execution").
technique_idstring–ATT&CK technique ID (e.g., "T1190").

No examples provided.

pentest_map_techniques ~204

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.

NameTypeReqDescription
auth_typestring–Authentication mechanism in use. Surfaces auth-specific attack techniques.
limitinteger–Maximum number of techniques to return (1–50, default 15). Higher values give broader coverage; lower values focus on highest-relevance items.
osstring–Target operating system. Narrows to OS-specific techniques.
servicesarray–Exposed services and interfaces (e.g., ["REST API", "GraphQL", "file upload", "admin panel"]). Narrows technique relevance.
stackarray–Technology stack components (e.g., ["Node.js", "Express", "PostgreSQL", "Redis"]). Each element matched against technique platform and procedure examples.
NameTypeReqDescription
attack_versionstring–ATT&CK dataset version used for technique data.
authorized_use_reminderstring–Reminder that technique mapping is for authorized testing engagements only. Rendered first.
capnumber–The limit applied to ranked_techniques.
errorobject–Present when the call failed. Absent on success.
owasp_test_casesarray–Relevant OWASP Testing Guide test cases for the profile (up to 10).
profile_summarystring–One-sentence normalized summary of the supplied target profile.
ranked_techniquesarray–Techniques ordered by relevance_score descending.
shownnumber–Number of ranked techniques returned.
truncatedboolean–True when ranked_techniques was capped by limit.

No examples provided.

Common questions

What is the io.github.cyanheads/pentest-mcp-server server?

io.github.cyanheads/pentest-mcp-server is listed in the public MCP registry as io.github.cyanheads/pentest-mcp-server. Offline methodology engine for authorized penetration testing, CTF, and security research. This page covers its hosted endpoint (https://pentest.caseyjhand.com/mcp).

Is the io.github.cyanheads/pentest-mcp-server server safe to use?

io.github.cyanheads/pentest-mcp-server scores 81 out of 100 on VerifyMCP. 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.cyanheads/pentest-mcp-server server expose?

io.github.cyanheads/pentest-mcp-server exposes 7 tools: pentest_guide, pentest_analyze_response, pentest_lookup_technique, pentest_lookup_group, pentest_map_techniques, and 2 more. Their descriptions and schemas cost roughly 1,139 tokens of context every time the server is loaded.

Does the io.github.cyanheads/pentest-mcp-server server require authentication?

No. We connected to io.github.cyanheads/pentest-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/pentest-mcp-server server still maintained?

io.github.cyanheads/pentest-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.