io.github.vola-trebla/react-render-profile-mcp
NPM · REACT-RENDER-PROFILE-MCP
Decodes React DevTools Profiler exports into render summaries and memoization advice for AI agents.
Available components
Last scanned (5 hours ago)
Scores higher than 76% of npm servers
Category Testing and QA
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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via ts-morph > @ts-morph/common > minimatch. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 166 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1251 tokens (~96/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 −2
- CVE-2026-118764 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/react-render-profile-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 32 |
| 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 →
analyze_compiler_efficacy ~86
Evaluates React Compiler or manual React.memo efficacy by tracking spurious renders. Calculates the Invalidation Index for each component to identify where unstable prop references trigger wasteful renders.
| Name | Type | Req | Description |
|---|---|---|---|
| invalid_threshold | number | – | Minimum invalidation index threshold to report (default: 10) |
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
audit_compiler_rules ~82
Audits a React component file to check if it violates compiler memoization safety guidelines (e.g., Date.now(), Math.random(), useRef mutations in render, 'use no memo' bails).
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | yes | Name of the React component to audit |
| file_path | string | yes | Absolute path to the React component file on disk |
No output schema declared.
No examples provided.
correlate_chrome_trace ~88
Aligns React commits with Chrome Performance trace events (re-layout, paint, style calculations) using blink.user_timing ⚛ markers to calculate Core Web Vitals (INP/CLS) impact.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
| trace_path | string | yes | Absolute path to Chrome performance timeline trace export (.json) |
No output schema declared.
No examples provided.
diagnose_hydration_and_suspense ~83
Detects server-client hydration mismatches and sequential nested Suspense waterfalls by analyzing mount durations, unmount events, and timelines.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
| waterfall_threshold_ms | number | – | Timeline delta threshold in ms to detect Suspense waterfalls (default: 100) |
No output schema declared.
No examples provided.
evaluate_external_store_performance ~88
Analyzes useSyncExternalStore performance, identifying selector reference instability and concurrency bypasses where heavy store updates block the high-priority main thread.
| Name | Type | Req | Description |
|---|---|---|---|
| max_blocking_task_ms | number | – | Maximum duration budget in ms for synchronous tasks before flagging bypass (default: 50) |
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
find_spurious_renders ~123
Finds React components that re-rendered without any meaningful prop, state, context, or hook changes. These are wasted renders caused by unstable references (inline objects/functions/arrays) passed from a parent. Returns component name, total render count, spurious count, and wasted milliseconds. Use to identify the highest-ROI targets for React.memo.
| Name | Type | Req | Description |
|---|---|---|---|
| min_render_count | number | – | Only include components with at least this many total renders (default: 1) |
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
get_hottest_components ~101
Returns the top N React components ranked by self CPU time (excluding children) across the entire profiling session. Includes total self ms, average per render, and percentage of total profile time. Use to find which components are the most expensive to render, regardless of cause.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
| top_n | number | – | Number of components to return (default: 10) |
No output schema declared.
No examples provided.
get_render_summary ~87
Returns a high-level overview of a React DevTools Profiler export: total commits, total render time, top 5 slowest components by self time, and total spurious (wasted) render count. Use this first to understand the scale of the performance problem before drilling into specifics.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
profile_rsc_stream ~80
Analyzes a React Server Components (RSC) Flight stream text log. Detects bloated chunks (>50KB), sequential Waterfall request bottlenecks, and security hazards like constructor traversing exploits (CVE-2025-55182 / React2Shell).
| Name | Type | Req | Description |
|---|---|---|---|
| stream_payload | string | yes | Raw line-separated Flight stream text payload |
No output schema declared.
No examples provided.
remediate_component ~141
Automatically optimizes a React component's AST by hoisting static declarations, wrapping unstable callbacks/objects in useCallback/useMemo, and wrapping the component in React.memo if the ROI score is above 1.5. Mutates the file on disk.
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | yes | Name of the React component to optimize |
| file_path | string | yes | Absolute path to the React component file on disk |
| roi_score | number | yes | Estimated ROI score from profiling (usually 0 to 5) justifying memoization overhead |
| unstable_props | string | yes | Comma-separated or space-separated list of props to memoize/wrap in hooks |
No output schema declared.
No examples provided.
suggest_memoization ~103
Analyzes the profiling data and returns concrete memoization suggestions. Currently detects React.memo candidates: components with spurious renders above the wasted ms threshold. Each suggestion explains why the component re-renders unnecessarily and what to do about it.
| Name | Type | Req | Description |
|---|---|---|---|
| min_wasted_ms | number | – | Only suggest for components wasting more than this many ms total (default: 0) |
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
trace_render_cascade ~112
For a specific React commit (render cycle), shows what triggered it and lists every component that re-rendered as a result, sorted by actual duration descending. Reveals propagation — e.g. a context update cascading into 40 children. Call get_render_summary first to find total_commits, then use 0-based commit_index.
| Name | Type | Req | Description |
|---|---|---|---|
| commit_index | number | yes | Zero-based index of the commit to inspect |
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
trace_state_cascade_footprint ~77
Reconstructs the virtual parent/owner tree traversal to measure the depth and consumer count of a state update cascade for a specific commit index.
| Name | Type | Req | Description |
|---|---|---|---|
| commit_index | number | yes | Zero-based index of the commit to trace |
| profile_path | string | yes | Absolute path to the React DevTools Profiler export (.json) |
No output schema declared.
No examples provided.
How do I install the io.github.vola-trebla/react-render-profile-mcp server?
io.github.vola-trebla/react-render-profile-mcp runs locally as an npm package, launched with npx -y react-render-profile-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 · react-render-profile-mcp
claude mcp add vola-trebla-react-render-profile-mcp -- npx -y react-render-profile-mcp
What is the io.github.vola-trebla/react-render-profile-mcp server?
io.github.vola-trebla/react-render-profile-mcp is listed in the public MCP registry as io.github.vola-trebla/react-render-profile-mcp. Decodes React DevTools Profiler exports into render summaries and memoization advice for AI agents. This page covers its npm package (react-render-profile-mcp).
Is the io.github.vola-trebla/react-render-profile-mcp server safe to use?
io.github.vola-trebla/react-render-profile-mcp scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.vola-trebla/react-render-profile-mcp server expose?
io.github.vola-trebla/react-render-profile-mcp exposes 13 tools: get_render_summary, find_spurious_renders, get_hottest_components, trace_render_cascade, suggest_memoization, and 8 more. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/react-render-profile-mcp server still maintained?
io.github.vola-trebla/react-render-profile-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.vola-trebla/react-render-profile-mcp server under?
io.github.vola-trebla/react-render-profile-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.