io.github.dbsectrainer/mcp-agent-trace-inspector

MCPcommunity
v1.0.0io.github.dbsectrainerUnknownUpdated 6mo agonpmGitHub

Step-by-step observability for MCP agent workflows

Local-first, MCP-native observability for agent workflows. Every tool call, prompt transformation, latency, and token count is recorded in a local SQLite database — no cloud account, no API key, no traces leaving your machine. Built specifically for MCP rather than bolted onto a generic LLM proxy. Tool reference | Configuration | Contributing | Troubleshooting | Design principles Tool call…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1Forks
6mo agoLast update
Package
Authorio.github.dbsectrainer
LicenseUnknown
Version1.0.0
Sourcemcp-registry
npmmcp-agent-trace-inspector
GitHubdbsectrainer/mcp-agent-trace-inspector
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · none privileged
Security scan✓ Cleanv1.0.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · none privileged
Statically extracted from the published packagev1.0.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

analyze-traceNo description published

This tool published no description. Forge does not invent one.

trace_idNo description published

This tool published no description. Forge does not invent one.

trace_startNo description published

This tool published no description. Forge does not invent one.

trace_stepNo description published

This tool published no description. Forge does not invent one.

trace_endNo description published

This tool published no description. Forge does not invent one.

get_trace_summaryNo description published

This tool published no description. Forge does not invent one.

list_tracesNo description published

This tool published no description. Forge does not invent one.

export_dashboardNo description published

This tool published no description. Forge does not invent one.

compare_tracesNo description published

This tool published no description. Forge does not invent one.

extract_reasoning_chainNo description published

This tool published no description. Forge does not invent one.

export_otelNo description published

This tool published no description. Forge does not invent one.

configure_alertsNo description published

This tool published no description. Forge does not invent one.

set_retention_policyNo description published

This tool published no description. Forge does not invent one.

apply_retentionNo description published

This tool published no description. Forge does not invent one.

export_compliance_logNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Local-first, MCP-native observability for agent workflows. Every tool call, prompt transformation, latency, and token count is recorded in a local SQLite database — no cloud account, no API key, no traces leaving your machine. Built specifically for MCP rather than bolted onto a generic LLM proxy. Tool reference | Configuration | Contributing | Troubleshooting | Design principles Tool call tracing: Captures inputs, outputs, latency, and token usage for every step in a workflow. Persistent…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

15 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.