Skip to main content
Glama
Jamie643

mcp-local-telemetry

by Jamie643
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-local-telemetry

No user-submitted related servers found.

    Related Servers

    • open-monitor

      hasna
      A
      license
      Not graded
      quality
      F
      maintenance
      Multi-machine system monitor with a built-in MCP server that enables AI agents to query health metrics, manage processes, schedule cron jobs, and run diagnostics across local and remote machines.
      133 npm
      Apache 2.0

    • DivLens MCP

      Lohithry
      F
      license
      Not graded
      quality
      C
      maintenance
      A real-time system diagnostics MCP server that gives AI agents live access to CPU, RAM, disk, network, processes, and hardware health metrics, with zero cloud dependency.
      7
      -

    • mcp-tespit

      maniakh
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to monitor real-time CPU, RAM, and disk usage on the local machine.
      -

    • cpu-z

      ivanfernandez2646
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients to inspect the local machine's CPU, memory, and disk information through tools, a structured resource, and an upgrade-assessment prompt.
      -

    • MCP Server Health Monitor

      nikolapP1
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to monitor server health through natural language, including HTTP endpoint checks, disk/memory/CPU usage, port status, and process listings.
      -
    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.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    get_system_metrics returns aggregate machine-level stats while get_top_processes returns per-process ranking, so their purposes are clearly distinct. An agent can trivially choose between them with no overlap.

    Naming Consistency5/5

    Both tools follow a consistent get_<noun> snake_case verb_noun pattern. Naming is predictable and idiomatic throughout.

    Tool Count3/5

    Two tools is on the thin side for a telemetry server; while each earns its place, the surface feels minimal and could reasonably include a couple more monitoring dimensions without bloat.

    Completeness3/5

    Core CPU/RAM/Disk and top-CPU-process coverage exists, but network I/O, memory-heavy process ranking, disk I/O, and any historical/sampling data are missing. Agents can perform basic pre-flight checks but hit dead ends for richer diagnostics.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources