# @perfonext/render-mcp

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

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.5.2
- **Author:** io.github.souvikdu
- **License:** MIT
- **npm:** @perfonext/render-mcp
- **Source:** https://github.com/souvikdu/perfonext-render-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 16 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-07T15:51:05.452Z
- **Version scanned:** 0.5.2
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `begin_render_analysis` — Entry point for render profiling. Choose an approach:
- `compare_renders` — Diff two loaded render profiles and rank the biggest regressions, improvements, additions, and removals.
- `get_captured_renders` — Optional diagnostic: peek at the live progress of a render-capture session without stopping it.
- `get_hot_commits` — Rank the most expensive commits in a loaded render profile and show the top components inside each spike.
- `get_render_summary` — Summarize the loaded Next.js render profile, including top components by render cost and detected render issues (rerender storms, commit spikes).
- `get_rerender_causes` — Highlight components with repeated rerenders and explain likely causes using heuristics derived from the exported profile.
- `get_slow_components` — Return the slowest components in a loaded Next.js render profile, ranked by total actual render time.
- `load_render_profile` — Load a React DevTools Profiler JSON export.
- `run_render_capture` — Called after instrumentation is wired up (steps 1–3 of begin_render_analysis).
- `stop_render_capture` — Stop a live render-capture session, finalize the buffered events into a render profile,

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"render\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@perfonext/render-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40perfonext%2Frender-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40perfonext%2Frender-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40perfonext%2Frender-mcp
- HTML page: https://forgeregistry.com/registry/%40perfonext%2Frender-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.