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

    • redash-mcp

      oceandepthz
      F
      license
      B
      quality
      B
      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
      -

    • openobserve-community-mcp

      alilxxey
      A
      license
      B
      quality
      C
      maintenance
      A read-only MCP server for OpenObserve Community Edition that works over the REST API. Provides tools for searching logs, traces, stream schemas, and dashboards - no Enterprise license required.
      8
      17
      GPL 3.0

    • TrustLayer MCP Server

      liquid1982
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides read-only access to TrustLayer's public API, enabling users to query and retrieve data about parties, documents, projects, and other TrustLayer entities through MCP-compatible tools.
      MIT

    • Technitium DNS MCP

      X1pheR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT

    • lcm2m-caddis-mcp

      LCM2M
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to LCM2M Caddis VM2M API for equipment, runs, telemetry, alarms, etc., via MCP tools.
      31
      31 npm
      MIT
    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources