io.github.cyanheads/pentest-mcp-server

Est-ce que io.github.cyanheads/pentest-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/pentest-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• pentest_analyze_response≈ 1657 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • context · string · optionnel
    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.
  • status_code · integer · optionnel
    HTTP status code (100–599). Helps classify the response type.
  • response_body · string · optionnel
    Raw HTML, JSON, XML, or error response body text. Maximum 10,000 characters.
  • response_headers · string · optionnel
    Raw HTTP response headers, optionally including the status line. Maximum 20,000 characters.

  Exemple d'appel

  {"name": "pentest_analyze_response", "arguments": {"context": "texte", "status_code": 1, "response_body": "texte", "response_headers": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "summary": "texte", "findings": [], "fingerprints": {}, "nextToolSuggestions": [], "authorized_use_reminder": "texte"}}

• pentest_encode_payload≈ 981 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • chain · array · requis
    Ordered 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.
  • explain · boolean · optionnel
    Whether to include the decode path and bypass rationale.
  • payload · string · requis
    Input payload string to encode. Max 10,000 characters.

  Exemple d'appel

  {"name": "pentest_encode_payload", "arguments": {"chain": [], "payload": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "encoded": "texte", "original": "texte", "decode_path": "texte", "detection_note": "texte", "bypass_rationale": "texte", "intermediate_steps": [], "authorized_use_reminder": "texte"}}

• pentest_generate_payloads≈ 1244 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • count · integer · optionnel
    Number of payload variants to return (1–20, default 5). More variants cover different bypass approaches for the same context.
  • category · string · requis · xss | sqli | ssrf | xxe | path_traversal | ssti | command_injection | open_redirect
    Vulnerability category for payload generation.
  • encoding · array · optionnel
    Optional encoding chain applied left to right to each returned template.
  • waf_profile · string · optionnel · cloudflare | aws_waf | modsecurity_crs | imperva | akamai | f5_bigip_asm | nginx_modsecurity | fortinet_fortiwaf
    WAF or filter in front of the authorized test target. When a specific WAF is named, bypass variants referencing known public research are included.
  • injection_context · string · requis · html_attribute | html_body | js_string | js_template | js_script_block | url_parameter | url_path | sql_where
    Precise injection context. Critical for XSS: an HTML attribute payload differs from a JS string payload. Provide the most specific context for the best results.

  Exemple d'appel

  {"name": "pentest_generate_payloads", "arguments": {"category": "xss", "injection_context": "html_attribute"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "category": "texte", "payloads": [], "injection_context": "texte", "authorized_use_reminder": "texte"}}

• pentest_get_guide≈ 1638 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • phase · string · optionnel · all | recon | enumeration | exploitation | post_exploitation
    Methodology phase selector. "all" returns the complete playbook; a named phase returns only that phase.
  • vector · string · requis · auth_bypass | idor | ssrf | xss | sqli | xxe | path_traversal | cors
    Attack vector to retrieve methodology for. Each vector has its own methodology branch covering recon through exploitation. Authorized testing only.
  • target_context · object · optionnel
    Optional target profile for authorized engagement. Providing this narrows the playbook to what is most relevant for the specific environment.

  Exemple d'appel

  {"name": "pentest_get_guide", "arguments": {"vector": "auth_bypass"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "phases": [], "vector": "texte", "owasp_references": [], "nextToolSuggestions": [], "attack_technique_ids": [], "authorized_use_reminder": "texte"}}

• pentest_lookup_group≈ 945 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    ATT&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 the best match.

  Exemple d'appel

  {"name": "pentest_lookup_group", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "name": "texte", "type": "group", "error": {}, "aliases": [], "description": "texte", "attack_version": "texte", "techniques_used": [], "authorized_use_reminder": "texte"}}

• pentest_lookup_technique≈ 1432 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    ATT&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 match plus related techniques.
  • include_subtechniques · boolean · optionnel
    Include sub-techniques in the result. Set to false when only the parent technique summary is needed.

  Exemple d'appel

  {"name": "pentest_lookup_technique", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "error": {}, "tactics": [], "detection": {}, "platforms": [], "description": "texte", "mitigations": [], "technique_id": "texte", "attack_version": "texte", "sub_techniques": [], "procedure_examples": [], "authorized_use_reminder": "texte"}}

• pentest_map_techniques≈ 1428 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • os · string · optionnel · linux | windows | macos | unknown
    Target operating system. Narrows to OS-specific techniques.
  • limit · integer · optionnel
    Maximum number of techniques to return (1–50, default 15). Higher values give broader coverage; lower values focus on highest-relevance items.
  • stack · array · optionnel
    Technology stack components (e.g., ["Node.js", "Express", "PostgreSQL", "Redis"]). Each element matched against technique platform and procedure examples.
  • services · array · optionnel
    Exposed services and interfaces (e.g., ["REST API", "GraphQL", "file upload", "admin panel"]). Narrows technique relevance.
  • auth_type · string · optionnel · jwt | session_cookie | api_key | oauth2 | basic_auth | ntlm | kerberos | none
    Authentication mechanism in use. Surfaces auth-specific attack techniques.

  Exemple d'appel

  {"name": "pentest_map_techniques", "arguments": {"os": "linux", "limit": 1, "stack": [], "services": [], "auth_type": "jwt"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "truncated": true, "attack_version": "texte", "profile_summary": "texte", "owasp_test_cases": [], "ranked_techniques": [], "authorized_use_reminder": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://pentest.caseyjhand.com/mcp