Skip to main content
Glama
0xKoda

WireMCP

by 0xKoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to WireMCP

No user-submitted related servers found.

    Related Servers

    • SharkMCP

      tuliperis
      A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol server that provides network packet capture and analysis capabilities through Wireshark/tshark integration, enabling AI assistants to perform network security analysis and troubleshooting.
      4
      35
      MIT

    • Wireshark MCP

      sarthaksiddha
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that integrates Wireshark's network analysis capabilities with AI systems like Claude, allowing direct analysis of network packet data without manual copying.
      31
      MIT

    • NetForensicMCP

      kylecui
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for offline network forensic analysis and threat intelligence, enabling LLMs to analyze PCAP files, extract streams, detect threats, and identify credentials using tshark.
      6
      MIT

    • mcpcap

      sentry-official
      A
      license
      A
      quality
      D
      maintenance
      A modular MCP server for analyzing PCAP files using protocol-specific analysis tools, enabling LLMs to read and analyze network packet captures from local paths or remote URLs.
      4
      MIT

    • Zeek-MCP

      Gabbo01
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that integrates Zeek network analysis capabilities with LLM chatbots, allowing them to analyze PCAP files and parse network logs through natural language interactions.
      7
      Apache 2.0
    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

    B3.3/5.0

    Scored across 7 tools

    Disambiguation3/5

    There is significant overlap between tools, particularly among those that capture live traffic (capture_packets, check_threats, get_conversations, get_summary_stats), which could cause confusion as they all involve live capture but serve slightly different analysis purposes. However, the descriptions help differentiate their specific outputs (e.g., raw packet data vs. threat checking vs. conversation statistics), preventing complete ambiguity.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., analyze_pcap, capture_packets, check_ip_threats), with all using snake_case and clear action-object phrasing. The only minor deviation is 'check_threats' lacking a specific object like 'ip' compared to 'check_ip_threats', but overall naming is predictable and readable.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a network analysis server, covering key areas like packet analysis, threat detection, and credential extraction. Each tool appears to serve a distinct function within the domain, avoiding bloat while providing comprehensive coverage for typical tasks.

    Completeness4/5

    The tool set covers core network analysis workflows, including packet capture, threat checking, credential extraction, and statistical analysis, with both live and file-based options. A minor gap is the lack of tools for modifying or filtering traffic, but agents can likely work around this for most analysis tasks, making the surface reasonably complete.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources