Skip to main content
Glama
AgentIA1984-cmd

agent-observability-mcp

by AgentIA1984-cmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to agent-observability-mcp

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
      13 npm
      2
      MIT

    • iris-eval/mcp-server

      iris-eval
      A
      license
      A
      quality
      A
      maintenance
      MCP-native agent evaluation and observability server. Log traces, evaluate output quality with 12 built-in rules (PII detection, prompt injection, cost thresholds), and track agent costs. Real-time dashboard, OTel-compatible spans. Self-hosted, MIT licensed.
      9
      857 npm
      9
      MIT

    • runmeter

      Aptica-Solutions
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that provides cost and reliability observability for LLM and agent workflows. It records model calls and allows querying and aggregating telemetry data through MCP tools.
      6
      MIT

    • mcp-context-inspector

      sohaibsohail98
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.
      8
      3
      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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: retrieving traces, logging events, searching events, aggregating metrics, scanning anomalies, and listing projects. No overlap in functionality.

    Naming Consistency5/5

    All tools follow the pattern 'obs_<resource>_<action>' with consistent verb-noun structure (e.g., obs_trace_get, obs_event_log, obs_events_search). The prefix 'obs_' unifies the set.

    Tool Count5/5

    Six tools is well-scoped for an observability server. Each tool addresses a core need (logging, retrieval, search, metrics, anomalies, project overview) without excess or deficiency.

    Completeness5/5

    The set covers the full lifecycle of agent observability: event creation, trace retrieval, search, metric aggregation, anomaly detection, and project listing. Missing operations like deletion are non-essential for an append-only observability system.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources