Perfonext Render MCP
NPM · @PERFONEXT/RENDER-MCP · SCANNED SEP 20
MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components.
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 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 95 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-render-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1093 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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.
npm · @perfonext/render-mcp
claude mcp add souvikdu-perfonext-render-mcp -- npx -y @perfonext/render-mcp
{
"mcpServers": {
"souvikdu-perfonext-render-mcp": {
"command": "npx",
"args": [
"-y",
"@perfonext/render-mcp"
]
}
}
} {
"servers": {
"souvikdu-perfonext-render-mcp": {
"command": "npx",
"args": [
"-y",
"@perfonext/render-mcp"
]
}
}
} codex mcp add souvikdu-perfonext-render-mcp -- npx -y @perfonext/render-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"souvikdu-perfonext-render-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@perfonext/render-mcp"
],
"enabled": true
}
}
} openclaw mcp add souvikdu-perfonext-render-mcp --command npx --arg -y --arg @perfonext/render-mcp
mcp_servers:
souvikdu-perfonext-render-mcp:
command: "npx"
args: ["-y", "@perfonext/render-mcp"] {
"McpServers": {
"souvikdu-perfonext-render-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@perfonext/render-mcp"
]
}
}
} assistant mcp add souvikdu-perfonext-render-mcp -t stdio -c npx -a -y @perfonext/render-mcp
{
"mcpServers": {
"souvikdu-perfonext-render-mcp": {
"command": "npx",
"args": [
"-y",
"@perfonext/render-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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +4
- Stability: unverified → 0.30 ▲ functional
- 4 Sept 26 82
First indexed and scored.
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 20 Sept 2026 · Analysed npm/@perfonext/render-mcp@0.5.2
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-render-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/souvikdu/perfonext-render-mcp/.github/workflows/publish.yml@refs/tags/v0.5.2 |
| Rekor log index | 2716933491 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d79045c6a09eb5bdcfdd718042e231665d2d14e43fa116c147ad2dd81655706a04b548dd628f041bed3f3e632e57e435e63e488d66ff733da5ed52de2 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
begin_render_analysis Begin Render Analysis ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| approach | string | yes | "live": react-scan/lite live capture (richer data, needs npm install). "manual": React DevTools Profiler JSON export (no install, less detailed). |
No output schema declared.
No examples provided.
compare_renders Compare Renders ~104
Diff two loaded render profiles and rank the biggest regressions, improvements, additions, and removals.
| Name | Type | Req | Description |
|---|---|---|---|
| baseProfileId | string | yes | Baseline profile ID from load_render_profile |
| currentProfileId | string | yes | 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. |
No output schema declared.
No examples provided.
get_captured_renders Get Captured Renders ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The sessionId returned by begin_render_analysis |
No output schema declared.
No examples provided.
get_hot_commits Get Hot Commits ~130
Rank the most expensive commits in a loaded render profile and show the top components inside each spike.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Profile ID from load_render_profile |
No output schema declared.
No examples provided.
get_render_summary Get Render Summary ~76
Summarize the loaded Next.js render profile, including top components by render cost and detected render issues (rerender storms, commit spikes).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many top components to include. Defaults to 10. |
| profileId | string | – | Profile ID from load_render_profile. Omit to list loaded profiles. |
No output schema declared.
No examples provided.
get_rerender_causes Get Rerender Causes ~108
Highlight components with repeated rerenders and explain likely causes using heuristics derived from the exported profile.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Profile ID from load_render_profile |
No output schema declared.
No examples provided.
get_slow_components Get Slow Components ~144
Return the slowest components in a loaded Next.js render profile, ranked by total actual render time.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Profile ID from load_render_profile |
| sortBy | string | – | Sort metric: "total" = total render time (default), "average" = average per render, "max" = peak single render time. |
No output schema declared.
No examples provided.
load_render_profile Load Render Profile ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute or relative path to the exported React Profiler JSON file |
No output schema declared.
No examples provided.
run_render_capture Run Render Capture ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | "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 | yes | The sessionId returned by begin_render_analysis. |
No output schema declared.
No examples provided.
stop_render_capture Stop Render Capture ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The sessionId returned by begin_render_analysis |
No output schema declared.
No examples provided.
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.