Skip to main content
Glama
TraceOrb

traceorb-mcp

Official
by TraceOrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to traceorb-mcp

No user-submitted related servers found.

    Related Servers

    • Gear MCP Server

      CloudStudioIoT
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to read facilities, devices, live values, history, and alarms from a Cloud Studio Gear IoT account, filtered to the user's permissions and strictly read-only.
      MIT

    • unofficial-trackjs-mcp

      olaj
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and other MCP clients to query JavaScript error data through the TrackJS Data API, including top messages, errors by URL, daily/hourly error counts, page views, and usage. It is read-only and returns compact, dashboard-linked results.
      8
      11 npm
      MIT

    • tracearr-mcp-server

      Barrow1990
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients to Tracearr's read-only Public API v2, enabling queries for live streams, watch history, media stats, users, and library information without modifying anything.
      MIT

    • redash-mcp

      oceandepthz
      F
      license
      B
      quality
      D
      maintenance
      Read-only MCP server wrapping the Redash REST API, enabling query listing, execution, data source inspection, and dashboard retrieval with optional per-user API key support.
      7
      -
    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.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: metrics, daily metrics, requests (list/get/compare), facets, and alert rules/incidents/firing-count. Even with similar descriptions, the names and endpoints make boundaries unambiguous.

    Naming Consistency5/5

    All tool names use a consistent verb_noun snake_case pattern: query_*, list_*, get_*, search_*, get_* with clear objects. The verb choice varies slightly but is semantically coherent and predictable.

    Tool Count5/5

    10 tools is well-scoped for a telemetry/observability server. It covers the primary data surfaces—metrics, requests, facets, and alerts—without unnecessary duplication or bloat.

    Completeness4/5

    The surface provides comprehensive read-only coverage for the domain: metrics variants, request lookups and comparison, facet search, alert rule listing, incident retrieval and firing counts. The only minor gap is lack of a get_alert_rule endpoint, but the listing makes this workable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources