Skip to main content
Glama
mithung-vunet

@mithung/vunet-mcp-server

Related Servers

Alternatives to @mithung/vunet-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to query and explore your OpenObserve observability data. Provides read-only access to logs, metrics, and traces for analysis and troubleshooting.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server that lets an AI assistant read and operate the Lumics network monitoring platform via its REST API.
      2
      6 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.
      6
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      This project provides a Model Context Protocol (MCP) server that allows language models and other MCP clients to interact with a SuzieQ network observability instance via its REST API.
      2
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying observability data from Elasticsearch, SkyWalking, and Prometheus/VictoriaMetrics, enabling AI models to search logs, traces, and metrics across environments.
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      he Maximo MCP Server bridges AI agents (Claude, Cursor, Antigravity) with your IBM Maximo environment. It empowers your AI to autonomously discover Object Structures (APIs), inspect schemas, and query live data via OSLC. Instead of hallucinating field names, the AI validates queries instantly and ca
      29 npm
      9
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation3/5

    Both vunet_fetch_datamodels and vunet_list_data_models are about listing data models, with the former fetching live signals from the API and the latter listing common models by category. This overlap could lead to agent confusion despite the distinct descriptions.

    Naming Consistency5/5

    All tools follow a consistent vunet_verb_noun pattern (e.g., vunet_fetch_datamodels, vunet_get_status), making the naming predictable and clear.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of data discovery and querying, covering essential operations without being too heavy or too thin.

    Completeness4/5

    The tools cover basic discovery and querying needs for VuNet data models, but minor gaps exist, such as a dedicated tool for drilling into specific metric details or handling pagination.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues