Skip to main content
Glama
alanzha2

observe-instrument-mcp

by alanzha2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to observe-instrument-mcp

No user-submitted related servers found.

    Related Servers

    • cursor-otel

      smith
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that instruments Cursor AI agent interactions with OpenTelemetry traces and logs to monitor agent turns and performance. It enables tracking of user queries, assistant responses, and tool usage through GenAI-compliant telemetry spans.
      MIT

    • 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
      16 npm
      2
      MIT

    • mcp-o11y

      argotdev
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that demonstrates comprehensive observability with Sentry, OpenTelemetry, and Braintrust, providing tools for file, data, and HTTP operations along with real-time status and configuration resources.
      -

    • mcp-audit

      nyx-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents observability over their own tool calls, enabling auditing, cost tracking, latency analysis, and alerting.
      MIT

    • Observability MCP Server

      sandraschi
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides comprehensive monitoring and observability for MCP server ecosystems with real-time health checks, performance metrics, distributed tracing, anomaly detection, and automated performance reports using OpenTelemetry and Prometheus.
      1
      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

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one audits for missing instrumentation (read-only), the other applies the instrumentation (modifies the file). There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun snake_case pattern: check_instrumentation and instrument_agent. The naming is clear and predictable.

    Tool Count4/5

    With only 2 tools, the server is minimal but appropriately scoped for its specific workflow of auditing and instrumenting Python AI agent files. It is slightly below the typical 3-15 range but still well-focused.

    Completeness5/5

    The tool set covers the full lifecycle for the stated purpose: check for missing instrumentation and apply it. There is no obvious gap—the backup creation in instrument_agent provides a safety net.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources