# Perfonext Profiler MCP (npm · @perfonext/profiler-mcp)

MCP server for analyzing V8/Chrome CPU profiles with line-level tick attribution.

- Trust score: 90/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@perfonext/profiler-mcp`: 90/100 (this document), [markdown](https://verifymcp.io/servers/souvikdu-perfonext-profiler-mcp/perfonext-profiler-mcp.md), [page](https://verifymcp.io/servers/souvikdu-perfonext-profiler-mcp/perfonext-profiler-mcp)

## Channel facts

- Registry: `npm`
- Package: `@perfonext/profiler-mcp`
- Version: `0.7.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to souvikdu/perfonext-profiler-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 894 tokens (~99/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add souvikdu-perfonext-profiler-mcp -- npx -y @perfonext/profiler-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "souvikdu-perfonext-profiler-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perfonext/profiler-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "souvikdu-perfonext-profiler-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perfonext/profiler-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add souvikdu-perfonext-profiler-mcp -- npx -y @perfonext/profiler-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "souvikdu-perfonext-profiler-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@perfonext/profiler-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add souvikdu-perfonext-profiler-mcp --command npx --arg -y --arg @perfonext/profiler-mcp
```

### Hermes

```yaml
mcp_servers:
  souvikdu-perfonext-profiler-mcp:
    command: "npx"
    args: ["-y", "@perfonext/profiler-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "souvikdu-perfonext-profiler-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@perfonext/profiler-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add souvikdu-perfonext-profiler-mcp -t stdio -c npx -a -y @perfonext/profiler-mcp
```

### Other

```json
{
  "mcpServers": {
    "souvikdu-perfonext-profiler-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perfonext/profiler-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 85, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 70, −12)

- [security regression] Malware scan: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.7.2 → 0.7.3

### 2026-09-04 (score 82)

First indexed and scored.

## MCP tools (9)

### `load_profile` (~70 tokens)

Load CPU Profile

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.

Input parameters:

- `filePath` (string, required): Absolute or relative path to the .cpuprofile or Chrome trace .json file

### `get_hotspots` (~71 tokens)

Get Hotspots

Returns the top N functions by self-time (CPU time spent directly in the function, not its callees). Use this to find performance bottlenecks.

Input parameters:

- `limit` (number): Number of hotspots to return (default: 10)
- `profileId` (string, required): Profile ID returned by load_profile

### `explain_function` (~121 tokens)

Explain Function

Returns detailed timing info for a specific function: self-time, total-time, callers, and callees. Use this to understand why a function is slow.

Input parameters:

- `contextLines` (integer): Only used with includeSource: minimum lines of padding around the declaration and hot lines (default: 10)
- `functionName` (string, required): Exact function name to look up
- `includeSource` (boolean): When true, include annotated source code lines with per-line tick counts (default: false)
- `profileId` (string, required): Profile ID returned by load_profile

### `compare_profiles` (~74 tokens)

Compare Profiles

Compare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.

Input parameters:

- `baseProfileId` (string, required): Profile ID of the baseline (before)
- `compareProfileId` (string, required): Profile ID to compare (after)
- `limit` (number): Number of top changes to show

### `suggest_optimizations` (~93 tokens)

Suggest Optimizations

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.

Input parameters:

- `limit` (number): Number of functions to analyze (default: 5)
- `profileId` (string, required): Profile ID returned by load_profile

### `get_profile_summary` (~122 tokens)

Get Profile Summary

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.

Input parameters:

- `profileId` (string): Profile ID. If omitted, lists all loaded profiles.
- `treeDepth` (number): Depth of call tree to include (default: 2, max: 5)

### `read_source_context` (~136 tokens)

Read Source Context

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.

Input parameters:

- `contextLines` (integer): Minimum lines of padding around the function declaration and its hot lines (default: 10)
- `functionName` (string, required): Exact function name to look up
- `profileId` (string, required): Profile ID returned by load_profile

### `get_package_costs` (~104 tokens)

Get Package Costs

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.

Input parameters:

- `limit` (integer): Maximum number of packages to return, sorted by self-time (default: 10)
- `profileId` (string, required): Profile ID returned by load_profile

### `how_to_collect` (~103 tokens)

How To Collect a CPU Profile

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.

Input parameters:

- `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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/souvikdu-perfonext-profiler-mcp/perfonext-profiler-mcp#diagnostics

## Score history

- 2026-09-21: 90
- 2026-09-20: 89
- 2026-09-19: 89
- 2026-09-18: 88
- 2026-09-17: 88
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 86
- 2026-09-13: 86
- 2026-09-12: 85
- 2026-09-11: 70
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 82
- 2026-09-07: 82
- 2026-09-06: 82
- 2026-09-05: 82
- 2026-09-04: 82

## Common questions

### 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 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 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 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.

## Links

- npm package: https://www.npmjs.com/package/@perfonext/profiler-mcp
- Socket report: https://socket.dev/npm/package/@perfonext/profiler-mcp
- Repository: https://github.com/souvikdu/perfonext-profiler-mcp
- Changelog RSS feed: https://verifymcp.io/servers/souvikdu-perfonext-profiler-mcp/perfonext-profiler-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/souvikdu-perfonext-profiler-mcp/perfonext-profiler-mcp.json
- HTML version of this page: https://verifymcp.io/servers/souvikdu-perfonext-profiler-mcp/perfonext-profiler-mcp