io.github.mdfifty50-boop/trace-forge
NPM · TRACE-FORGE-MCP
Structured execution trace and span logging for AI agents
Available components
Last scanned (22 hours ago)
Scores higher than 49% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 210 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability46
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 656 tokens (~65/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 19 Nov 26 −1
- Stability: pass → 0.97 functional
- 18 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 −2
- Stability: pass → 0.90 functional
- 4 Nov 26 +1
- Stability: 0.97 → pass security
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/trace-forge-mcp@0.1.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
get_trace ~37
Retrieve a complete trace tree with all spans, events, tool calls, and decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | Trace ID to retrieve |
No output schema declared.
No examples provided.
health_check ~20
Returns server health, uptime, version, and call stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_traces ~76
Find traces by agent ID and/or status. Returns matching traces sorted by recency with summary stats.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Filter by agent ID |
| limit | integer | – | Max results to return (default 20) |
| status | string | – | Filter by status (active, success, failure, partial, timeout) |
No output schema declared.
No examples provided.
trace_decision ~109
Log an agent decision point — what it considered, what it chose, and why. Critical for EU AI Act explainability.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives_considered | array | yes | Other options the agent evaluated |
| chosen_action | string | yes | What the agent decided to do |
| confidence | number | yes | Agent confidence in this decision (0.0 to 1.0) |
| reasoning | string | yes | Why the agent made this decision |
| trace_id | string | yes | Trace this decision belongs to |
No output schema declared.
No examples provided.
trace_end ~62
Complete a trace. Auto-calculates total duration, event counts, and span counts.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | Final outcome of the traced task |
| summary | string | – | Optional summary of what happened |
| trace_id | string | yes | Trace to complete |
No output schema declared.
No examples provided.
trace_span ~98
Create a span within a trace. Spans represent logical units of work and can be nested via parent_span_id.
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | object | – | Optional span metadata |
| parent_span_id | string | – | Parent span ID for nesting (creates a tree) |
| span_name | string | yes | Name of this span (e.g. "research", "code_generation", "validation") |
| trace_id | string | yes | Trace to attach this span to |
No output schema declared.
No examples provided.
trace_start ~82
Begin a new trace for an agent task. Returns a trace_id used to attach spans, tool calls, and decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Unique identifier for the agent starting the trace |
| metadata | object | – | Optional metadata (model, department, priority, etc.) |
| task_description | string | yes | Human-readable description of what the agent is doing |
No output schema declared.
No examples provided.
trace_tool_call ~160
Log a tool call within a trace. Records tool name, arguments, result, duration, and token usage. Auto-calculates cost estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | yes | Arguments passed to the tool |
| duration_ms | number | yes | How long the tool call took in milliseconds |
| result_preview | string | yes | Brief preview of the result (max 500 chars) |
| span_id | string | – | Span this tool call belongs to (optional) |
| status | string | yes | Outcome of the tool call |
| tokens_used | integer | – | Token count for this call (optional, enables cost estimation) |
| tool_name | string | yes | Name of the tool that was called |
| trace_id | string | yes | Trace this tool call belongs to |
No output schema declared.
No examples provided.
How do I install the io.github.mdfifty50-boop/trace-forge MCP server?
io.github.mdfifty50-boop/trace-forge runs locally as an npm package, launched with npx -y trace-forge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · trace-forge-mcp
claude mcp add mdfifty50-boop-trace-forge -- npx -y trace-forge-mcp
What is the io.github.mdfifty50-boop/trace-forge MCP server?
io.github.mdfifty50-boop/trace-forge is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/trace-forge. Structured execution trace and span logging for AI agents. This page covers its npm package (trace-forge-mcp).
Is the io.github.mdfifty50-boop/trace-forge MCP server safe to use?
io.github.mdfifty50-boop/trace-forge scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against 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.mdfifty50-boop/trace-forge MCP server expose?
io.github.mdfifty50-boop/trace-forge exposes 8 tools: health_check, trace_start, trace_span, trace_tool_call, trace_decision, and 3 more. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.
Is the io.github.mdfifty50-boop/trace-forge MCP server still maintained?
io.github.mdfifty50-boop/trace-forge 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.mdfifty50-boop/trace-forge MCP server under?
io.github.mdfifty50-boop/trace-forge 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.mdfifty50-boop/trace-forge MCP server?
VerifyMCP ran 16 checks on io.github.mdfifty50-boop/trace-forge, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.