# Perfonext Render MCP (npm · @perfonext/render-mcp)

MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@perfonext/render-mcp`
- Version: `0.5.2`
- 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-20.

- **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-render-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1093 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Render MCP server?

Perfonext Render MCP runs locally as an npm package, launched with npx -y @perfonext/render-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-render-mcp -- npx -y @perfonext/render-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "souvikdu-perfonext-render-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@perfonext/render-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-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, +4)

- [functional improvement] Stability: unverified → 0.30

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

First indexed and scored.

## MCP tools (10)

### `load_render_profile` (~106 tokens)

Load Render Profile

Load a React DevTools Profiler JSON export. This is the entry point for the manual profiling path: open React DevTools in the browser → Profiler tab → Record → interact → Stop → Export JSON → share the file path here. Returns a profileId for use with get_render_summary, get_slow_components, get_rerender_causes, and the other analysis tools.

Input parameters:

- `filePath` (string, required): Absolute or relative path to the exported React Profiler JSON file

### `compare_renders` (~104 tokens)

Compare Renders

Diff two loaded render profiles and rank the biggest regressions, improvements, additions, and removals.

Input parameters:

- `baseProfileId` (string, required): Baseline profile ID from load_render_profile
- `currentProfileId` (string, required): Current profile ID from load_render_profile
- `limit` (integer): How many changed components to include. Defaults to 10.
- `minDeltaMs` (number): Minimum absolute total render delta in ms for changed components. Defaults to 0.

### `get_render_summary` (~76 tokens)

Get Render Summary

Summarize the loaded Next.js render profile, including top components by render cost and detected render issues (rerender storms, commit spikes).

Input parameters:

- `limit` (integer): How many top components to include. Defaults to 10.
- `profileId` (string): Profile ID from load_render_profile. Omit to list loaded profiles.

### `get_hot_commits` (~130 tokens)

Get Hot Commits

Rank the most expensive commits in a loaded render profile and show the top components inside each spike.

Input parameters:

- `componentLimit` (integer): How many top components to include per commit. Defaults to 3.
- `limit` (integer): How many commits to include. Defaults to 10.
- `priorityLevel` (string): Filter to commits with this priority level only. Common values: "Immediate" (synchronous, input-blocking), "Normal" (async, e.g. API responses). Omit to include all priorities.
- `profileId` (string, required): Profile ID from load_render_profile

### `get_slow_components` (~144 tokens)

Get Slow Components

Return the slowest components in a loaded Next.js render profile, ranked by total actual render time.

Input parameters:

- `limit` (integer): How many components to return. Defaults to 10.
- `minSelfDuration` (number): Minimum total self duration in ms to include — the same metric the default "total" sort ranks by, excluding time spent in children. Filters sub-millisecond noise. Defaults to 0.
- `profileId` (string, required): Profile ID from load_render_profile
- `sortBy` (string): Sort metric: "total" = total render time (default), "average" = average per render, "max" = peak single render time.

### `get_rerender_causes` (~108 tokens)

Get Rerender Causes

Highlight components with repeated rerenders and explain likely causes using heuristics derived from the exported profile.

Input parameters:

- `limit` (integer): How many components to include. Defaults to 10.
- `minActualDuration` (number): Minimum total actual duration in ms for a component to appear — render time including its children, the same metric this tool ranks cost by. Filters sub-millisecond noise. Defaults to 0.
- `profileId` (string, required): Profile ID from load_render_profile

### `begin_render_analysis` (~124 tokens)

Begin Render Analysis

Entry point for render profiling. Choose an approach:
  live   — react-scan/lite streams events in real time; exact rerender causes, source locations, changeDescription.
  manual — no install needed; user exports a JSON from the React DevTools Profiler tab and shares the file path.
Ask the user which approach they prefer before calling this tool.

Input parameters:

- `approach` (string, required): "live": react-scan/lite live capture (richer data, needs npm install). "manual": React DevTools Profiler JSON export (no install, less detailed).

### `run_render_capture` (~135 tokens)

Run Render Capture

Called after instrumentation is wired up (steps 1–3 of begin_render_analysis). Ask the user how they want to generate renders before calling this tool:
  manual-interaction — start the dev server and the user clicks through the app.
  test-suite         — run an existing automated test suite against the running app.

Input parameters:

- `method` (string, required): "manual-interaction": user navigates the app manually (fast, focused). "test-suite": run an existing test suite (automated; scope to one file/feature to keep payload manageable).
- `sessionId` (string, required): The sessionId returned by begin_render_analysis.

### `stop_render_capture` (~72 tokens)

Stop Render Capture

Stop a live render-capture session, finalize the buffered events into a render profile, and return a profileId you can use with get_render_summary, get_slow_components, get_rerender_causes, and compare_renders.

Input parameters:

- `sessionId` (string, required): The sessionId returned by begin_render_analysis

### `get_captured_renders` (~94 tokens)

Get Captured Renders

Optional diagnostic: peek at the live progress of a render-capture session without stopping it. Returns commit count, components seen, whether actualDuration is populating, and an unknownEvents count (non-zero = instrumentation may not be wired correctly). Only call this if something seems wrong — it is not a required step before stop_render_capture.

Input parameters:

- `sessionId` (string, required): The sessionId returned by begin_render_analysis

## Diagnostics

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

## Score history

- 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: 82
- 2026-09-11: 82
- 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 Render MCP server?

Perfonext Render MCP is listed in the public MCP registry as io.github.souvikdu/perfonext-render-mcp. MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components. This page covers its npm package (@perfonext/render-mcp).

### Is the Perfonext Render MCP server safe to use?

Perfonext Render MCP scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 Render MCP server expose?

Perfonext Render MCP exposes 10 tools: load_render_profile, compare_renders, get_render_summary, get_hot_commits, get_slow_components, and 5 more. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.

### Is the Perfonext Render MCP server still maintained?

Perfonext Render MCP is still listed as active in the MCP registry. We last reached this channel on 20 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 Render MCP server under?

Perfonext Render 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/render-mcp
- Socket report: https://socket.dev/npm/package/@perfonext/render-mcp
- Repository: https://github.com/souvikdu/perfonext-render-mcp
- Changelog RSS feed: https://verifymcp.io/servers/souvikdu-perfonext-render-mcp/perfonext-render-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/souvikdu-perfonext-render-mcp/perfonext-render-mcp.json
- HTML version of this page: https://verifymcp.io/servers/souvikdu-perfonext-render-mcp/perfonext-render-mcp