Perfonext Profiler MCP
NPM · @PERFONEXT/PROFILER-MCP
MCP server for analyzing V8/Chrome CPU profiles with line-level tick attribution.
Available components
Last scanned (19 hours ago)
Scores higher than 98% 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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to souvikdu/perfonext-profiler-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 70 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 894 tokens (~99/item across 9 items; 9 tools + 0 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 9 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.
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 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.
- 8 Nov 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.
- 7 Nov 26 −3
- Stability: pass → 0.83 functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 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 21 Nov 2026 · Analysed npm/@perfonext/profiler-mcp@0.7.3
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 | souvikdu/perfonext-profiler-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/souvikdu/perfonext-profiler-mcp/.github/workflows/publish.yml@refs/tags/v0.7.3 |
| Rekor log index | 2797222358 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:94c555b80ac93e8f4a293b7fdb7d53e9e399b5061166ebfcafc5e305bb4627d7017778f2f9ae96142465cc3dd23c99db9918ba9f347d2d62dd1d63ad4 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
compare_profiles Compare Profiles ~74
Compare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.
| Name | Type | Req | Description |
|---|---|---|---|
| baseProfileId | string | yes | Profile ID of the baseline (before) |
| compareProfileId | string | yes | Profile ID to compare (after) |
| limit | number | – | Number of top changes to show |
No output schema declared.
No examples provided.
explain_function Explain Function ~121
Returns detailed timing info for a specific function: self-time, total-time, callers, and callees. Use this to understand why a function is slow.
| Name | Type | Req | Description |
|---|---|---|---|
| contextLines | integer | – | Only used with includeSource: minimum lines of padding around the declaration and hot lines (default: 10) |
| functionName | string | yes | Exact function name to look up |
| includeSource | boolean | – | When true, include annotated source code lines with per-line tick counts (default: false) |
| profileId | string | yes | Profile ID returned by load_profile |
No output schema declared.
No examples provided.
get_hotspots Get Hotspots ~71
Returns the top N functions by self-time (CPU time spent directly in the function, not its callees). Use this to find performance bottlenecks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of hotspots to return (default: 10) |
| profileId | string | yes | Profile ID returned by load_profile |
No output schema declared.
No examples provided.
get_package_costs Get Package Costs ~104
Aggregate CPU self-time by npm package. Identifies which third-party dependencies are consuming the most CPU, by parsing node_modules paths from the profile. Useful for deciding which packages to replace, lazy-load, or avoid. Scoped packages (e.g. @babel/core) are handled correctly.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of packages to return, sorted by self-time (default: 10) |
| profileId | string | yes | Profile ID returned by load_profile |
No output schema declared.
No examples provided.
get_profile_summary Get Profile Summary ~122
Returns an overview of a loaded profile: duration, sample count, top-level call tree (filtered to functions >0.1% of total time), and idle time percentage. For large profiles, the call tree is limited to depth 2 and top 20 children per node to keep output manageable. Also lists all loaded profiles if no ID is given.
| Name | Type | Req | Description |
|---|---|---|---|
| profileId | string | – | Profile ID. If omitted, lists all loaded profiles. |
| treeDepth | number | – | Depth of call tree to include (default: 2, max: 5) |
No output schema declared.
No examples provided.
how_to_collect How To Collect a CPU Profile ~103
Returns a ready-to-run command and step-by-step recipe for capturing a V8 CPU profile, then loading it with load_profile. Use this when you do not yet have a .cpuprofile file. Choose the scenario that matches how the code runs.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | – | How the code under test runs. "next-server" (default) profiles a Next.js production server; "script" profiles a Next.js standalone server.js (or another Node entry). |
No output schema declared.
No examples provided.
load_profile Load CPU Profile ~70
Parse and load a V8/Chrome CPU profile from disk. Supports both .cpuprofile files and Chrome DevTools Trace JSON exports. Returns a profile ID for use with other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute or relative path to the .cpuprofile or Chrome trace .json file |
No output schema declared.
No examples provided.
read_source_context Read Source Context ~136
Read the actual source code for a hot function and annotate each line with sampled tick counts from positionTicks. The returned window is sized to cover the function's actual hot lines, not just the area around its declaration; if any ticks still fall outside it, a `warning` field reports how many and suggests a larger contextLines. Only reads files within the project root.
| Name | Type | Req | Description |
|---|---|---|---|
| contextLines | integer | – | Minimum lines of padding around the function declaration and its hot lines (default: 10) |
| functionName | string | yes | Exact function name to look up |
| profileId | string | yes | Profile ID returned by load_profile |
No output schema declared.
No examples provided.
suggest_optimizations Suggest Optimizations ~93
Analyzes the profile and returns structured optimization suggestions for the hottest functions. Detects high fan-in, recursion, dominant callers, V8-specific patterns, always reports CPU self-time cost for expensive functions, and deduplicates functions split across multiple call sites.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of functions to analyze (default: 5) |
| profileId | string | yes | Profile ID returned by load_profile |
No output schema declared.
No examples provided.
How do I install the Perfonext Profiler MCP server?
Perfonext Profiler MCP runs locally as an npm package, launched with npx -y @perfonext/profiler-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 · @perfonext/profiler-mcp
claude mcp add souvikdu-perfonext-profiler-mcp -- npx -y @perfonext/profiler-mcp
What is the Perfonext Profiler MCP server?
Perfonext Profiler MCP is listed in the public MCP registry as io.github.souvikdu/perfonext-profiler-mcp. MCP server for analyzing V8/Chrome CPU profiles with line-level tick attribution. This page covers its npm package (@perfonext/profiler-mcp).
Is the Perfonext Profiler MCP server safe to use?
Perfonext Profiler MCP scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Perfonext Profiler MCP server expose?
Perfonext Profiler MCP exposes 9 tools: load_profile, get_hotspots, explain_function, compare_profiles, suggest_optimizations, and 4 more. Their descriptions and schemas cost roughly 894 tokens of context every time the server is loaded.
Is the Perfonext Profiler MCP server still maintained?
Perfonext Profiler MCP 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 Perfonext Profiler MCP server under?
Perfonext Profiler 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 Perfonext Profiler MCP server?
VerifyMCP ran 16 checks on Perfonext Profiler 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.