why-did-you-render-mcp

Bridges unnecessary React re-render data from the browser to coding agents, enabling performance diagnosis and optimization through MCP tools.

→ 0x1f320/why-did-you-render-mcp · listed on glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama PulseMCP

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

// required environment variables

This server reads these from process.env. You'll be asked to provide them before it can run.

configWDYR_WS_PORT— 4649 WebSocket server port

// full audit trail

The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/0x1f320-why-did-you-render-mcp-1oja0n)](https://m8ven.ai/mcp/0x1f320-why-did-you-render-mcp-1oja0n)

commit: a8d1696f8727bcba055790b089680581009a0b5c

code hash: 2d06d8c7af715614cd54e73e93448d96b4683d37d0ff25354b0abf5eb5168835

verified: 7/20/2026, 9:24:17 AM

view raw JSON →