io.github.dbsectrainer/mcp-agent-trace-inspector
NPM · MCP-AGENT-TRACE-INSPECTOR
Step-by-step observability for MCP agent workflows
Available components
Last scanned (23 hours ago)
Scores higher than 44% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1320 tokens (~101/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 +18
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 1.0.0 → 1.0.1 functional
- 3 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 2 Nov 26 −1
- Security disclosure: pass → unverified ▼ functional
- 31 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 12 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/mcp-agent-trace-inspector@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_retention ~43
Apply the current in-process retention policy: archives traces older than retention_days and deletes archived traces past 2× threshold. Call set_retention_policy first. Example: {}
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_traces ~101
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" }
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id_a | string | yes | ID of the first trace (baseline). Example: "abc-123" |
| trace_id_b | string | yes | ID of the second trace (to compare against). Example: "def-456" |
No output schema declared.
No examples provided.
configure_alerts ~118
Persist alert rules for latency, error rate, or cost thresholds. Rules are evaluated on trace_end; optional Slack or generic webhooks deliver fired alerts. Example: { "rules": [{"type":"latency","threshold":1000}], "slack_webhook": "https://hooks.slack.com/..." }
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | yes | Array of alert rules to configure. |
| slack_webhook | string | – | Optional Slack webhook URL for Slack block notifications. |
| webhook_url | string | – | Optional generic webhook URL for JSON POST notifications. |
No output schema declared.
No examples provided.
export_compliance_log ~115
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" }
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Output format: "json" or "csv". |
| from_date | string | – | Optional ISO date string to filter entries from (inclusive). |
| to_date | string | – | Optional ISO date string to filter entries to (inclusive). |
No output schema declared.
No examples provided.
export_dashboard ~70
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" }
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | ID of the trace to export. Example: "abc-123-def-456" |
No output schema declared.
No examples provided.
export_otel ~114
Export trace(s) as an OTLP/JSON document (resourceSpans → scopeSpans → spans) suitable for an OTLP collector or backend. Omit trace_id to export all traces. Example: { "format": "json" } or { "trace_id": "abc-123", "format": "json" }
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Export format. Currently only "json" is supported. |
| trace_id | string | – | Optional trace ID to export. Omit to export all traces. |
No output schema declared.
No examples provided.
extract_reasoning_chain ~93
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" }
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | ID of the trace to extract reasoning from. Example: "abc-123-def-456" |
No output schema declared.
No examples provided.
get_trace_summary ~119
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" }
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Model name for cost estimation. Example: "claude-sonnet-4-6". Defaults to "claude-sonnet-4-6". |
| trace_id | string | yes | ID of the trace to summarize. Example: "abc-123-def-456" |
No output schema declared.
No examples provided.
list_traces ~67
List all stored traces with their names, statuses, and timestamps. Example: { "limit": 10 } to get the 10 most recent traces.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of traces to return (most recent first). Example: 20. Omit for all. |
No output schema declared.
No examples provided.
set_retention_policy ~60
Set the trace retention policy (how many days to keep traces before archiving). Example: { "retention_days": 30 }
| Name | Type | Req | Description |
|---|---|---|---|
| retention_days | number | yes | Number of days to retain traces before archiving. Must be > 0. |
No output schema declared.
No examples provided.
trace_end ~68
Mark a trace as completed and evaluate the currently configured alert rules. Further trace_step calls for this trace are rejected. Example: { "trace_id": "abc-123" }
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | ID of the trace to complete. Example: "abc-123-def-456" |
No output schema declared.
No examples provided.
trace_start ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Human-readable name for this trace/workflow run. Example: "Product Search Workflow 2024-01-15". Pass "auto" to auto-generate. |
No output schema declared.
No examples provided.
trace_step ~262
Record a single step within a running trace. Captures tool name, input, output, optional token count and latency. Steps cannot be added after trace_end. Example: { "trace_id": "abc-123", "tool_name": "web_search", "input": {"query": "hello"}, "output": {"results": ["a","b"]}, "token_count": 50, "latency_ms": 320 }
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Input payload passed to the tool. Example: { "query": "weather in Paris" } |
| latency_ms | number | – | Optional wall-clock latency of this step in milliseconds. Example: 450 |
| output | object | yes | Output/result returned by the tool. Example: { "result": "Sunny, 22°C" }. Add "error" field or "isError": true to flag errors. |
| token_count | number | – | Optional number of tokens consumed in this step. Example: 150 |
| tool_name | string | yes | Name of the tool or action that was executed. Example: "web_search" or "llm_call" |
| trace_id | string | yes | ID of the trace to record this step under. Example: "abc-123-def-456" |
No output schema declared.
No examples provided.
How do I install the io.github.dbsectrainer/mcp-agent-trace-inspector server?
io.github.dbsectrainer/mcp-agent-trace-inspector runs locally as an npm package, launched with npx -y mcp-agent-trace-inspector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-agent-trace-inspector
claude mcp add dbsectrainer-mcp-agent-trace-inspector -- npx -y mcp-agent-trace-inspector
What is the io.github.dbsectrainer/mcp-agent-trace-inspector server?
io.github.dbsectrainer/mcp-agent-trace-inspector is listed in the public MCP registry as io.github.dbsectrainer/mcp-agent-trace-inspector. Step-by-step observability for MCP agent workflows. This page covers its npm package (mcp-agent-trace-inspector).
Is the io.github.dbsectrainer/mcp-agent-trace-inspector server safe to use?
io.github.dbsectrainer/mcp-agent-trace-inspector scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.dbsectrainer/mcp-agent-trace-inspector server expose?
io.github.dbsectrainer/mcp-agent-trace-inspector exposes 13 tools: trace_start, trace_step, trace_end, get_trace_summary, list_traces, and 8 more. Their descriptions and schemas cost roughly 1,320 tokens of context every time the server is loaded.
Is the io.github.dbsectrainer/mcp-agent-trace-inspector server still maintained?
io.github.dbsectrainer/mcp-agent-trace-inspector is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.dbsectrainer/mcp-agent-trace-inspector server under?
io.github.dbsectrainer/mcp-agent-trace-inspector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.dbsectrainer/mcp-agent-trace-inspector server?
VerifyMCP ran 15 checks on io.github.dbsectrainer/mcp-agent-trace-inspector, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.dbsectrainer/mcp-agent-trace-inspector: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.