Skip to main content
Glama
Sign In
anthonylouschwank

noc-pcap-mcp-server

by anthonylouschwank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to noc-pcap-mcp-server

No user-submitted related servers found.

    Related Servers

    • pcaplens

      xuange-hu
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an LLM to triage packet captures with nine tools that return capped summaries of conversations, talkers, protocols, DNS, HTTP, and TLS, then drill into individual packets, with every finding citing the packet number that proves it. Reads classic pcap and pcapng files using only the Python standard library, so no tshark or other external binary is required.
      MIT

    • pcap-mcp

      jiadewoer
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to securely investigate packet captures through Wireshark's tshark engine, with bounded tools for protocol inventory, TCP failure diagnosis, latency measurement, and threat hunting.
      12
      MIT

    • Wireshark MCP

      andsopwn
      F
      license
      C
      quality
      F
      maintenance
      Enables LLMs to capture, analyze, and summarize network traffic using Wireshark CLI tools, supporting live capture, pcap analysis, and LLM-oriented summaries.
      76
      -

    • mcpacket

      mcpcap
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to analyze network packet captures (PCAP files) from local or remote sources through a modular architecture. Supports DNS traffic analysis with structured JSON responses for network security and troubleshooting tasks.
      9
      121 PyPI
      53
      MIT
    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.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct layer or task: overall summary, conversation enumeration, per-conversation transport analysis, security scanning, and JSON-RPC payload extraction. Though analyze_tcp_conversation and extract_json_rpc_exchange both work on a conversation, one is transport-focused and the other application-focused, so no reasonable misselection exists.

    Naming Consistency5/5

    All tool names follow a clear verb_noun snake_case pattern: get/list/analyze/detect/extract plus a specific object. The singular 'tcp_conversation' after 'analyze_' and the plural in 'list_tcp_conversations' is grammatically consistent, not a style break.

    Tool Count5/5

    Five tools is a well-scoped set for a PCAP analysis server; each tool provides a distinct capability without redundancy. This is within the ideal range and leaves room for focused use.

    Completeness4/5

    The surface covers the core NOC/PCAP workflow: summarize, enumerate conversations, drill into a conversation's health, detect anomalies, and extract application-layer exchanges. A minor gap is the lack of generic packet/filter drill-down or pcap file management, but agents can work around these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources