Skip to main content
Glama
AgentOps-AI

AgentOps MCP

Official
by AgentOps-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to AgentOps MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • Maple

      alnosarus
      F
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server providing observability, safety control, and behavior evolution for high-agency AI agents through tracing, replaying, and auditing. It features real-time firewall guardrails and ML-driven anomaly detection to monitor, block, or fork agent actions based on risk.
      2 npm
      -

    • Cortex OS

      qi-mouren
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI agents with persistent memory, cross-agent sharing, and context management, enabling them to remember conversations, track complex tasks, and evolve skills across tools.
      2
      MIT

    • AIS Revizor

      bswvladimir-beep
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.
      -
    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 4 tools

    Disambiguation3/5

    The tools have some overlap that could cause confusion, particularly between get_trace and get_complete_trace, which both retrieve trace data by trace_id, making their boundaries unclear. However, get_span is distinct in targeting span-level data, and auth is clearly separate for authentication purposes.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern (e.g., get_complete_trace, get_span, get_trace), but auth deviates as a standalone verb without a noun, which is a minor inconsistency. Overall, the naming is readable and follows a predictable style.

    Tool Count4/5

    With 4 tools, the count is slightly low but reasonable for a server focused on trace and span retrieval, as it covers core operations without being overly thin. It could benefit from additional tools like creating or updating traces to be more comprehensive, but it's not severely lacking.

    Completeness2/5

    The tool surface is significantly incomplete for an observability domain like AgentOps, as it only provides read operations (get) for traces and spans, with no create, update, delete, or search capabilities. This will likely cause agent failures when trying to perform full lifecycle management of monitoring data.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources