Skip to main content
Glama
originchain-ai

@originchain/telemetry-mcp

Official
by originchain-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @originchain/telemetry-mcp

No user-submitted related servers found.

    Related Servers

    • DevContext

      sid-stack001
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to access live runtime observability data such as logs, deploys, and health metrics for evidence-based incident triage.
      1
      MIT
    • Spyglass AI MCP Server by Spyglass-AI

      Spyglass AI MCP Serverofficial

      Spyglass-AI
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to query telemetry data via the Spyglass AI agent, providing intelligent insights about application performance, errors, and bottlenecks.
      1
      MIT
    • Mirador MCP by mirastacklabs-ai

      Mirador MCPofficial

      mirastacklabs-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform observability analysis across Prometheus-compatible metrics and logs without prior vendor knowledge, including signal discovery, entity topology resolution, root-cause analysis, correlation, and capacity forecasting through natural-language anchors.
      Apache 2.0

    • otel-mcp-server

      shiftyp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying and analysis of OpenTelemetry traces, metrics, and logs stored in Elasticsearch/OpenSearch, allowing AI assistants to investigate performance issues, find root causes, and explore system behavior.
      21 npm
      14
      MIT

    • OpenTelemetry MCP Server

      agarwalvivek29
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to query Prometheus metrics and Loki logs for intelligent alert investigation and troubleshooting. Provides service discovery, metric querying, log searching, and correlation tools to help identify root causes of issues.
      9
      -
    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.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct concerns: aggregates, pattern search, raw lines, errors, traces, and dependency graphs. Some overlap exists between fts_search and similar_patterns, and between recent_events and recent_errors, but descriptions are explicit enough that an agent can disambiguate.

    Naming Consistency4/5

    All names use lowercase snake_case and are mostly noun-phrase query names like log_volume, top_patterns, and service_graph. A few names like trace_lookup and sql_query hint at actions, so the pattern is not perfectly uniform, but it is readable and predictable.

    Tool Count5/5

    Ten tools is well-scoped for a telemetry server. Each tool covers a distinct analytical need—aggregation, pattern search, raw log access, error analysis, incident synthesis, dependencies, traces, and SQL—without feeling bloated or redundant.

    Completeness5/5

    The surface covers the core telemetry workflow comprehensively: finding patterns, searching semantically and by keyword, inspecting actual log lines, analyzing errors, investigating entire incidents, tracing requests, and exploring service dependencies. The read-only SQL escape hatch also covers edge cases, so there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources