Skip to main content
Glama
desvert
by desvert

Related Servers

Alternatives to otparse-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that enables LLMs to analyze pcap files by providing tools for packet dissection, stream following, and data extraction via tshark. It supports protocol hierarchy analysis, credential scanning, and threat intelligence checks on captured network traffic.
      52
      470 PyPI
      238
      MIT
    • 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
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI-assisted network packet analysis using Wireshark's TShark tool. It provides tools for pcap file overview, session extraction, protocol filtering, and statistical analysis through a standardized interface.
      1
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that provides LLMs with real-time network traffic analysis capabilities, enabling tasks like threat hunting, network diagnostics, and anomaly detection through Wireshark's tshark.
      7
      584
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      MCP server for network-troubleshooting PCAP analysis via tshark, enabling users to analyze PCAP files, detect anomalies, and troubleshoot network issues.
      22
      -

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one parses BACnet/IP traffic and the other parses Modbus/TCP traffic. The descriptions specify different protocols (BACnet vs. Modbus) and outputs (decoded packets vs. transactions), leaving no ambiguity for an agent to misselect between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern (parse_bacnet_pcap and parse_modbus_pcap), using the same verb 'parse' and similar noun structures. This predictable naming makes the tool set easy to understand and navigate.

    Tool Count3/5

    With only 2 tools, the server feels thin for its apparent domain of parsing industrial protocol traffic from PCAPs. While it covers two common protocols, the scope could reasonably include more protocols or related operations, making the count borderline for comprehensive coverage.

    Completeness2/5

    The tool set is significantly incomplete for the inferred domain of industrial protocol analysis. It lacks essential operations such as listing available protocols, validating PCAP files, filtering or searching parsed data, and handling other common protocols like DNP3 or OPC UA, which limits agent workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues