io.github.tracelane/tracelane-mcp
NPM · @TRACELANEDEV/MCP
Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts
Available components
Last scanned (18 hours ago)
Scores higher than 65% 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
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to tracelane/tracelane). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 712 tokens (~89/item across 8 items; 8 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_eval_result" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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.
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.
- 14 Oct 26 +31
- 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
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 11 Oct 26 49
First indexed and scored.
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 16 Oct 2026 · Analysed npm/@tracelanedev/mcp@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | tracelane/tracelane |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/tracelane/tracelane/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 3168295383 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0ac21743a45e716842fac4abdad28f20884387c4205f56e55f8bf6522016ec4e8f3e4769005d2e8852c98e7b4577b7cf99a11e96ba2ddb9d5df35a8ee |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
explain_guardrail_block ~168
Explain a Tracelane guardrail signal. Two independent id kinds, pick the one you have: `correlation_id` — the id in a guardrail 403 response body, for a request that was blocked pre-flight (there is no trace/span for it, since the request never dispatched); or `trace_id` + `span_id` together — to explain a detection-layer (AFT) flag recorded on a span that DID execute.
| Name | Type | Req | Description |
|---|---|---|---|
| correlation_id | string | – | The correlation id from a guardrail block's 403 response body. |
| span_id | string | – | The span ID carrying an AFT detection flag. Use with trace_id. |
| trace_id | string | – | The trace ID containing an AFT-flagged span. Use with span_id. |
No output schema declared.
No examples provided.
get_eval_result ~44
Get the latest result for a specific eval
| Name | Type | Req | Description |
|---|---|---|---|
| eval_id | string | yes | Eval ID, e.g. PP-G3, PP-PR1, FT-01 |
No output schema declared.
No examples provided.
get_span ~87
Get details for a specific span including all LLM attributes. trace_id is REQUIRED in Cloud (gateway) mode — there is no span-by-id gateway route, so the span is located via GET /v1/traces/{trace_id}/spans.
| Name | Type | Req | Description |
|---|---|---|---|
| span_id | string | yes | The span ID |
| trace_id | string | – | The trace ID (required — see tool description). |
No output schema declared.
No examples provided.
get_trace ~29
Get all spans for a specific trace
| Name | Type | Req | Description |
|---|---|---|---|
| trace_id | string | yes | The trace ID to fetch |
No output schema declared.
No examples provided.
list_evals ~24
List all pain-point and fault-tolerance evals and their current status
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_traces ~73
List recent traces for the authenticated tenant
| Name | Type | Req | Description |
|---|---|---|---|
| has_error | boolean | – | Filter to traces with at least one error span |
| limit | number | – | Maximum traces to return (1-100) |
| model_filter | string | – | Filter by model name, e.g. claude-sonnet-4-6 |
No output schema declared.
No examples provided.
replay_trace ~136
Fetch the full stored structure of a trace (ordered spans with their LLM/tool attributes) for offline inspection and step-through debugging. Read-only: this returns the recorded trace as-is and does NOT re-execute any model or tool — live shadow re-execution requires the gateway and is not part of the MCP server surface.
| Name | Type | Req | Description |
|---|---|---|---|
| include_tool_calls | boolean | – | Include non-LLM (tool / browser / MCP) spans in the result. When false, only LLM spans (those whose attributes carry a gen_ai/llm model) are returned. |
| trace_id | string | yes | The trace ID to fetch for inspection |
No output schema declared.
No examples provided.
search_traces ~151
Search traces by free-text substring across span names and the attributes JSON blob, optionally narrowed by model name or error status. Read-only; tenant-scoped. In gateway (Cloud) mode the gateway rejects a search term shorter than 4 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| has_error | boolean | – | Restrict to error spans (status_code = 2) when true |
| limit | number | – | Maximum distinct traces to return (1-50) |
| model_filter | string | – | Restrict to spans whose attributes mention this model |
| query | string | yes | Case-insensitive substring matched against span name and the attributes JSON (model names, prompts, tool names, etc.). Gateway mode requires at least 4 characters. |
No output schema declared.
No examples provided.
How do I install the io.github.tracelane/tracelane-mcp server?
io.github.tracelane/tracelane-mcp runs locally as an npm package, launched with npx -y @tracelanedev/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 · @tracelanedev/mcp
claude mcp add tracelane-tracelane-mcp -- npx -y @tracelanedev/mcp
What is the io.github.tracelane/tracelane-mcp server?
io.github.tracelane/tracelane-mcp is listed in the public MCP registry as io.github.tracelane/tracelane-mcp. Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts. This page covers its npm package (@tracelanedev/mcp).
Is the io.github.tracelane/tracelane-mcp server safe to use?
io.github.tracelane/tracelane-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.tracelane/tracelane-mcp server expose?
io.github.tracelane/tracelane-mcp exposes 8 tools: list_traces, get_trace, get_span, search_traces, replay_trace, and 3 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.
Is the io.github.tracelane/tracelane-mcp server still maintained?
io.github.tracelane/tracelane-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 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.tracelane/tracelane-mcp server under?
io.github.tracelane/tracelane-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.