io.github.MasonChow/source-map-parser-mcp
NPM · SOURCE-MAP-PARSER-MCP · SCANNED SEP 25
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 → Why this is hard to 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 & Transparency43
- 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 361 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.MasonChow/source-map-parser-mcp server?
io.github.MasonChow/source-map-parser-mcp runs locally as an npm package, launched with npx -y source-map-parser-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 · source-map-parser-mcp
claude mcp add masonchow-source-map-parser-mcp -- npx -y source-map-parser-mcp
{
"mcpServers": {
"masonchow-source-map-parser-mcp": {
"command": "npx",
"args": [
"-y",
"source-map-parser-mcp"
]
}
}
} {
"servers": {
"masonchow-source-map-parser-mcp": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"source-map-parser-mcp"
]
}
}
} assistant mcp add masonchow-source-map-parser-mcp -t stdio -c npx -a -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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.83 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 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.
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 25 Sept 2026 · Analysed npm/source-map-parser-mcp@1.3.2
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 1 package
| Packages resolved | 1 |
|---|---|
| No linked repository | 1 |
| 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 →
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.
What is the io.github.MasonChow/source-map-parser-mcp server?
io.github.MasonChow/source-map-parser-mcp is listed in the public MCP registry as io.github.MasonChow/source-map-parser-mcp. Parse JavaScript error stack traces back to original source code using source maps. This page covers its npm package (source-map-parser-mcp).
Is the io.github.MasonChow/source-map-parser-mcp server safe to use?
io.github.MasonChow/source-map-parser-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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.MasonChow/source-map-parser-mcp server expose?
io.github.MasonChow/source-map-parser-mcp exposes 2 tools: operating_guide, parse_stack. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Is the io.github.MasonChow/source-map-parser-mcp server still maintained?
io.github.MasonChow/source-map-parser-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 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.MasonChow/source-map-parser-mcp server under?
io.github.MasonChow/source-map-parser-mcp declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.