Skip to content
Agentmart
Submit a tool

MCP Agent Trace Inspector

Step-by-step observability for MCP agent workflows

Connector by dbsectrainer · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/dbsectrainer-mcp-agent-trace-inspector

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Step-by-step observability for MCP agent workflows

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
7 read · 5 write · 1 delete
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 13

Read from the source code; the running server may list different tools.

Read 7 · Look things up without changing anything.

  • compare_traces
  • export_compliance_log
  • export_dashboard
  • export_otel
  • extract_reasoning_chain
  • get_trace_summary
  • list_traces

Write 5 · Create, change, send or run things.

  • configure_alerts
  • set_retention_policy
  • trace_end
  • trace_start
  • trace_step

Delete 1 · Delete, drop, revoke or wipe things.

  • apply_retention

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • YOUR_API_KEY

Tools (13)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • apply_retentioncan change or delete data

    Apply the current retention policy: archives traces older than retention_days and deletes archived traces past 2× threshold. Example: {}

  • compare_tracesread-only

    Compare two traces side by side: step counts, tokens, latency, and step-by-step differences. Example: { "trace_id_a": "abc-123", "trace_id_b": "def-456" }

  • configure_alerts

    Configure alert rules for latency, error rate, or cost thresholds. Example: { "rules": [{"type":"latency","threshold":1000}], "slack_webhook": "https://hooks.slack.com/..." }

  • export_compliance_logread-only

    Export the compliance audit log as JSON or CSV. Example: { "format": "json" } or { "format": "csv", "from_date": "2025-01-01", "to_date": "2025-12-31" }

  • export_dashboardread-only

    Generate a self-contained HTML dashboard for a trace with error highlighting and latency waterfall visualization. Returns the full HTML as a string. Example: { "trace_id": "abc-123" }

  • export_otelread-only

    Export trace(s) in OpenTelemetry OTLP JSON span format. Omit trace_id to export all traces. Example: { "format": "json" } or { "trace_id": "abc-123", "format": "json" }

  • extract_reasoning_chainread-only

    Extract only the reasoning/thinking steps from a trace. Returns steps whose tool_name matches reasoning patterns (reason, think, plan, reflect, analyz, consider) or whose input/output content includes the word "think". Example: { "trace_id": "abc-123" }

  • get_trace_summaryread-only

    Retrieve a summary of a trace including step count, total tokens, total latency, cost estimate, and reasoning chain detection. Example: { "trace_id": "abc-123", "model": "claude-sonnet-4-6" }

  • list_tracesread-only

    List all stored traces with their names, statuses, and timestamps. Example: { "limit": 10 } to get the 10 most recent traces.

  • set_retention_policy

    Set the trace retention policy (how many days to keep traces before archiving). Example: { "retention_days": 30 }

  • trace_end

    Mark a trace as completed. No further steps should be added after this call. Example: { "trace_id": "abc-123" }

  • trace_start

    Begin a new agent workflow trace. Returns a trace_id to use with subsequent calls. Example: { "name": "My Search Workflow" }. Pass "auto" or leave name blank for an auto-generated name.

  • trace_step

    Record a single step within a trace. Captures tool name, input, output, optional token count and latency. Example: { "trace_id": "abc-123", "tool_name": "web_search", "input": {"query": "hello"}, "output": {"results": ["a","b"]}, "token_count": 50, "latency_ms": 320 }

Signals

Stars
0
Forks
1
Open issues
0
Last commit
Sep 22, 2026 (1 month ago)
Last release
Mar 23, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.dbsectrainer/mcp-agent-trace-inspector
Version
1.0.0
Auth
API key
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 25, 2026

More from dbsectrainer

Cite this page

MCP Agent Trace Inspector. Agent Mart. https://agentmart.dev/connectors/dbsectrainer-mcp-agent-trace-inspector (last updated 2026-10-25)