MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
begin_render_analysisEntry point for render profiling. Choose an approach:Entry point for render profiling. Choose an approach:
No input schema was published for this tool.
compare_rendersDiff two loaded render profiles and rank the biggest regressions, improvements, additions, and removals.Diff two loaded render profiles and rank the biggest regressions, improvements, additions, and removals.
No input schema was published for this tool.
get_captured_rendersOptional diagnostic: peek at the live progress of a render-capture session without stopping it.Optional diagnostic: peek at the live progress of a render-capture session without stopping it.
No input schema was published for this tool.
get_hot_commitsRank the most expensive commits in a loaded render profile and show the top components inside each spike.Rank the most expensive commits in a loaded render profile and show the top components inside each spike.
No input schema was published for this tool.
get_render_summarySummarize the loaded Next.js render profile, including top components by render cost and detected render issues (rerender storms, commit spikes).Summarize the loaded Next.js render profile, including top components by render cost and detected render issues (rerender storms, commit spikes).
No input schema was published for this tool.
get_rerender_causesHighlight components with repeated rerenders and explain likely causes using heuristics derived from the exported profile.Highlight components with repeated rerenders and explain likely causes using heuristics derived from the exported profile.
No input schema was published for this tool.
get_slow_componentsReturn the slowest components in a loaded Next.js render profile, ranked by total actual render time.Return the slowest components in a loaded Next.js render profile, ranked by total actual render time.
No input schema was published for this tool.
load_render_profileLoad a React DevTools Profiler JSON export.Load a React DevTools Profiler JSON export.
No input schema was published for this tool.
run_render_captureCalled after instrumentation is wired up (steps 1–3 of begin_render_analysis).Called after instrumentation is wired up (steps 1–3 of begin_render_analysis).
No input schema was published for this tool.
stop_render_captureStop a live render-capture session, finalize the buffered events into a render profile,Stop a live render-capture session, finalize the buffered events into a render profile,
No input schema was published for this tool.
10 of 10 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+41 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.