Skip to main content
Glama
Sign In
MCP Trace Inspector

MCP Trace Inspector

by abhishekash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Trace Inspector

No user-submitted related servers found.

    Related Servers

    • otel-mcp

      moondef
      A
      license
      A
      quality
      D
      maintenance
      MCP server that gives AI agents access to your application's OpenTelemetry traces for querying, analysis, and debugging.
      5
      11 npm
      2
      MIT

    • hatchet-ops-mcp

      TavenYin
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that exposes Hatchet client / REST observability APIs to coding agents across multiple environments from one process.
      MIT

    • poly-observability-mcp

      hyperpolymath
      A
      license
      Not graded
      quality
      D
      maintenance
      Unified MCP server for observability and monitoring, providing tools to query metrics, logs, and traces through Prometheus, Grafana, Loki, and Jaeger.
      2
      Mozilla Public 2.0

    • fanout

      labstack
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted OpenTelemetry backend in one Go binary. Its MCP server exposes tools for service health, latency, topology, trace inspection, log search, read-only SQL over traces, logs and metrics, and dashboards.
      11
      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

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have distinct analytical purposes (failure_report, tool_stats, security_audit, span_tree, slowest_spans, etc.), but token_usage and compare_runs overlap in cost/token/latency aggregation, and recent_activity vs list_runs both surface recent runs/spans, which could cause occasional misselection.

    Naming Consistency5/5

    All 12 tools use a consistent snake_case noun_phrase or verb_noun pattern (failure_report, tool_stats, list_runs, run_summary, span_tree), making names predictable and readable.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each targets a specific diagnostic need (failures, stats, security, activity, comparison, runs, summary, tree, latency, approvals, tokens, search).

    Completeness4/5

    The surface covers run listing, summaries, span trees, failures, latency, tokens, security, approvals, search, and comparison—strong lifecycle coverage for trace inspection. Minor gaps like deleting/exporting traces or filtering by date/tool in list_runs are workaround-able but not critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources