io.github.MasonChow/source-map-parser-mcp
NPM · SOURCE-MAP-PARSER-MCP · SCANNED AUG 3
Parse JavaScript error stack traces back to original source code using source maps
Available components
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 →
Supply Chain Security97
- 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
- 1 of 1 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- 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 (ISC).Pass
- Actively maintained (last published 308 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 304 tokens (~152/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · source-map-parser-mcp
claude mcp add masonchow-source-map-parser-mcp -- npx -y source-map-parser-mcp
codex mcp add masonchow-source-map-parser-mcp -- npx -y source-map-parser-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"masonchow-source-map-parser-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"source-map-parser-mcp"
],
"enabled": true
}
}
} openclaw mcp add masonchow-source-map-parser-mcp --command npx --arg -y --arg source-map-parser-mcp
mcp_servers:
masonchow-source-map-parser-mcp:
command: "npx"
args: ["-y", "source-map-parser-mcp"] {
"mcpServers": {
"masonchow-source-map-parser-mcp": {
"command": "npx",
"args": [
"-y",
"source-map-parser-mcp"
]
}
}
} 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.
- 31 Jul 26 −11
- Malware scan: pass → unverified ▼ security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +25
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Tool coverage: 0 functional
- 26 Jul 26 45
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 1 package
1 package in the resolved dependency tree · 1 without a linked repository.
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.
operating_guide ~62
# Parse Error Stack Trace This tool allows you to parse error stack traces by mapping them to the corresponding source code locations using source maps. It is particularly useful for debugging production errors where the stack trace points to minified or obfuscated code.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
parse_stack ~242
# Parse Error Stack Trace This tool allows you to parse error stack traces by providing the following: - A downloadable source map URL. - The line and column numbers from the stack trace. The tool will map the provided stack trace information to the corresponding source code location using the source map. It also supports fetching additional context lines around the error location for better debugging. ## Parameters: - **stacks**: An array of stack trace objects, each containing: - **line**: The line number in the stack trace. - **column**: The column number in the stack trace. - **sourceMapUrl**: The URL of the source map file corresponding to the stack trace. - **ctxOffset** (optional): The number of additional context lines to include before and after the error location in the source code. Defaults to 5. ## Returns: - A JSON object containing the parsed stack trace information, including the mapped source code location and context lines. - If parsing fails, an error message will be returned for the corresponding stack trace.
| Name | Type | Req | Description |
|---|---|---|---|
| stacks | array | yes | — |
No output schema declared.
No examples provided.