Skip to main content
Glama
Pawangunjkar

agent-trace-mcp

by Pawangunjkar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-trace-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-agent-trace-inspector

      dbsectrainer
      A
      license
      A
      quality
      B
      maintenance
      Enables local-first observability for MCP agent workflows by recording tool calls, prompts, latency, and token usage in a local SQLite database, and provides tools for inspecting, comparing, exporting, and generating dashboards from traces.
      13
      20 npm
      MIT

    • mcp-tool-observability

      Uscout07
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables live tracing and observability of MCP tool calls, persisting execution traces to MongoDB and streaming them in real time to a dashboard.
      -

    • agent-obs

      KryptosAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to self-report every tool call, token usage, decision, and session grade into a local SQLite store, so users can trace execution, audit reasoning, and see per-session costs in a local dashboard. Also supports proxy mode to intercept and trace MCP tool invocations for agents that cannot self-report.
      35 npm
      2
      MIT

    • MCP Execution Ledger

      Saimadhav27
      F
      license
      Not graded
      quality
      D
      maintenance
      Records all MCP tool interactions in a centralized ledger, enabling developers to trace, replay, inspect, and audit AI agent workflows.
      -

    • MCP Agent Trace

      AMEOBIUS-space
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables recording and analyzing AI agent execution traces, including event logging, metric computation, loop detection, and JSON export for debugging agent behavior.
      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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct purpose: recording, listing runs, retrieving a run, filtering failures, computing token costs, finding slowest tools, and checking status. No overlaps or ambiguity.

    Naming Consistency5/5

    All tools follow the consistent pattern of 'trace_' prefix plus a descriptive verb or noun phrase, using snake_case throughout. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With 7 tools, the server is well-scoped for tracing functionality—covering recording, querying, and analysis without excess or deficiency.

    Completeness4/5

    The surface covers core tracing needs: record, list, get, filter failures, cost, performance, and status. Minor gaps like clearing or deleting runs exist but are not critical for typical usage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources