Skip to main content
Glama
titaniumtushar

burp-mcp-plus

by titaniumtushar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to burp-mcp-plus

No user-submitted related servers found.

    Related Servers

    • Burp Suite MCP Server

      jayluxferro
      F
      license
      A
      quality
      D
      maintenance
      Exposes Burp Suite's REST API to AI assistants, enabling users to trigger vulnerability scans, monitor progress, and manage security tasks through natural language. It also provides programmatic access to Burp's security knowledge base for querying vulnerability definitions and remediation advice.
      8
      1
      -

    • mcp-code-context

      achatainga
      A
      license
      B
      quality
      B
      maintenance
      Enables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.
      25
      19 npm
      3
      MIT

    • dsh-burpsuite-mcp

      6jeffr3y
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables DeepSeek Harness agents to natively use Burp Suite capabilities such as proxy, logger, history, repeater, rewrite, intercept, BCheck, and Bambda, with runtime configuration and controlled active operations.
      -

    • Burp Suite MCP Analyzer

      sklnhunt
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets AI assistants analyze Burp Suite XML exports offline, without running Burp. Provides 19 tools for mapping endpoints, finding secrets, detecting vulnerabilities, analyzing headers, exporting curl commands, and generating pentest reports.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct Burp feature or action: collaborator generation vs. polling, dedup management (load, list, get, search, send to repeater), JS file handling (load, list, get, search), history browsing (list, search, inspect), repeater/intruder creation from history or template, direct request sending, and sitemap building. Overlaps like multiple tools that send to repeater are differentiated by source (history entry vs. template vs. dedup entry).

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., collaborator_check, dedup_get, list_history, send_request) with occasional prepositions for specificity (e.g., dedup_to_repeater, repeater_from_history). The naming is predictable and readable across the entire set.

    Tool Count5/5

    With 20 tools, the server covers multiple distinct aspects of Burp interaction (history, repeater, intruder, collaborator, dedup, JS files) without being overbearing. Each tool serves a clear purpose, and the count is well-scoped for a comprehensive Burp automation interface.

    Completeness4/5

    The tool set provides a solid coverage of core Burp workflow needs: history inspection, mutation and forwarding to repeater/intruder, collaborator interaction, dedup management, and JS file analysis. Minor gaps exist—such as no direct way to manage scope or proxy settings—but the surface is sufficient for typical automated testing scenarios.

    Resources