io.github.vola-trebla/v8-cpu-profile-decoder-mcp
NPM · V8-CPU-PROFILE-DECODER-MCP
MCP server that decodes V8 CPU profiles into token-efficient bottleneck summaries for AI agents
Available components
Last scanned (16 hours ago)
Scores higher than 81% 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
- 30 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 169 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 986 tokens (~164/item across 6 items; 6 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 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed npm/v8-cpu-profile-decoder-mcp@0.3.0
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
analyze_async_bottlenecks ~132
Detects event-loop overhead in a V8 CPU profile by identifying V8 internal frames that represent async machinery — microtask queue processing, nextTick saturation, and timer/immediate callbacks. These frames are invisible to most profilers but consume real CPU when promise chains are deep or nextTick is overused. Use to answer: is the bottleneck async orchestration overhead rather than synchronous computation?
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the .cpuprofile file |
| threshold_percent | number | – | Async overhead percentage above which a warning is emitted in the verdict (default: 10) |
No output schema declared.
No examples provided.
analyze_call_tree_path ~115
Finds all callers of a specific function in a V8 CPU profile and returns how often each caller invoked it. Accepts partial, case-insensitive function name matching. Use to answer: what is calling my slow function and how many times?
| Name | Type | Req | Description |
|---|---|---|---|
| function_name | string | yes | Function name to search for (partial match, case-insensitive) |
| profile_path | string | yes | Absolute path to the .cpuprofile file |
| top_callers | integer | – | Number of top callers to return (default: 5) |
No output schema declared.
No examples provided.
analyze_gc_pressure ~146
Analyses a V8 .cpuprofile for garbage collection overhead. Reports total GC time as a percentage of profiling duration, broken down by GC type (Scavenger = short-lived object pressure, Mark-Sweep/Mark-Compact = old-space pressure, Incremental = high allocation rate). Flags when GC exceeds a configurable threshold and provides a targeted recommendation. Use to answer: is GC the bottleneck, and what kind of allocation pattern is causing it?
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the .cpuprofile file |
| threshold_percent | number | – | GC percentage above which exceeds_threshold is set to true and a warning is emitted (default: 10) |
No output schema declared.
No examples provided.
correlate_source_code ~129
Maps the hottest functions in a V8 CPU profile back to their original TypeScript source locations using source map files (.js.map). Falls back to compiled JS locations if no source map is found. Use to answer: which TypeScript file and line is the bottleneck actually coming from?
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the .cpuprofile file |
| sourcemap_dir | string | – | Override directory to search for .map files (default: same directory as .js file) |
| top_n | integer | – | Number of hottest functions to resolve (default: 10) |
No output schema declared.
No examples provided.
diff_profiles ~157
Compares two V8 .cpuprofile files (before and after an optimization) and returns per-function CPU time deltas, normalized against each profile's total duration. Frames are matched by call-frame coordinates (functionName + url + line + column), not by transient node IDs, so alignment is stable across profiling sessions. Use to answer: which functions improved or regressed after my change, and by how much?
| Name | Type | Req | Description |
|---|---|---|---|
| after_profile_path | string | yes | Absolute path to the optimized .cpuprofile file to compare against the baseline |
| before_profile_path | string | yes | Absolute path to the baseline .cpuprofile file |
| top_n | integer | – | Number of top improvements and regressions to return (default: 5) |
No output schema declared.
No examples provided.
extract_hottest_functions ~307
Parses a V8 .cpuprofile file and returns the top N functions ranked by exclusive CPU time (self time). Filters out V8 internals and Node.js built-ins by default, returning only user code. Framework frames (express, next.js, koa, etc.) can be collapsed into a single entry. Recursive calls to the same source location are merged with an instanceCount field. Use this first to identify which functions are consuming the most CPU in a Node.js performance profile.
| Name | Type | Req | Description |
|---|---|---|---|
| collapse_frameworks | boolean | – | Collapse all frames from known frameworks (express, next.js, koa, fastify, nestjs, react, vue, nuxt, hapi) into a single "<framework> internals>" entry per framework. Prevents dozens of small framewo… |
| collapse_recursion | boolean | – | Merge multiple nodes with the same source location (functionName + url + line + column) into one entry. instanceCount shows how many recursive instances were merged (default: true) |
| include_node_internals | boolean | – | Include V8 internals and Node.js built-ins in results (default: false) |
| min_self_percent | number | – | Minimum self time percentage to include a function (default: 0.5%) |
| profile_path | string | yes | Absolute path to the .cpuprofile file |
| top_n | integer | – | Number of hottest functions to return (default: 10) |
No output schema declared.
No examples provided.
How do I install the io.github.vola-trebla/v8-cpu-profile-decoder-mcp server?
io.github.vola-trebla/v8-cpu-profile-decoder-mcp runs locally as an npm package, launched with npx -y v8-cpu-profile-decoder-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 · v8-cpu-profile-decoder-mcp
claude mcp add vola-trebla-v8-cpu-profile-decoder-mcp -- npx -y v8-cpu-profile-decoder-mcp
What is the io.github.vola-trebla/v8-cpu-profile-decoder-mcp server?
io.github.vola-trebla/v8-cpu-profile-decoder-mcp is listed in the public MCP registry as io.github.vola-trebla/v8-cpu-profile-decoder-mcp. MCP server that decodes V8 CPU profiles into token-efficient bottleneck summaries for AI agents. This page covers its npm package (v8-cpu-profile-decoder-mcp).
Is the io.github.vola-trebla/v8-cpu-profile-decoder-mcp server safe to use?
io.github.vola-trebla/v8-cpu-profile-decoder-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.vola-trebla/v8-cpu-profile-decoder-mcp server expose?
io.github.vola-trebla/v8-cpu-profile-decoder-mcp exposes 6 tools: extract_hottest_functions, analyze_call_tree_path, correlate_source_code, analyze_gc_pressure, diff_profiles, analyze_async_bottlenecks. Their descriptions and schemas cost roughly 986 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/v8-cpu-profile-decoder-mcp server still maintained?
io.github.vola-trebla/v8-cpu-profile-decoder-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.vola-trebla/v8-cpu-profile-decoder-mcp server under?
io.github.vola-trebla/v8-cpu-profile-decoder-mcp 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.vola-trebla/v8-cpu-profile-decoder-mcp server?
VerifyMCP ran 16 checks on io.github.vola-trebla/v8-cpu-profile-decoder-mcp, 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.