# Crispy Profiling (npm · crispy-profiling)

Deterministic React render profiling: renders, wasted renders and their causes per component.

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `crispy-profiling`: 87/100 (this document), [markdown](https://verifymcp.io/servers/edgeorgie-crispy-profiling/crispy-profiling.md), [page](https://verifymcp.io/servers/edgeorgie-crispy-profiling/crispy-profiling)

## Channel facts

- Registry: `npm`
- Package: `crispy-profiling`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to edgeorgie/crispy-profiling).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 648 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 39% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Crispy Profiling MCP server?

Crispy Profiling runs locally as an npm package, launched with npx -y crispy-profiling. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add edgeorgie-crispy-profiling -- npx -y crispy-profiling
```

### Cursor

```json
{
  "mcpServers": {
    "edgeorgie-crispy-profiling": {
      "command": "npx",
      "args": [
        "-y",
        "crispy-profiling"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "edgeorgie-crispy-profiling": {
      "command": "npx",
      "args": [
        "-y",
        "crispy-profiling"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add edgeorgie-crispy-profiling -- npx -y crispy-profiling
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "edgeorgie-crispy-profiling": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "crispy-profiling"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add edgeorgie-crispy-profiling --command npx --arg -y --arg crispy-profiling
```

### Hermes

```yaml
mcp_servers:
  edgeorgie-crispy-profiling:
    command: "npx"
    args: ["-y", "crispy-profiling"]
```

### Netclaw

```json
{
  "McpServers": {
    "edgeorgie-crispy-profiling": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "crispy-profiling"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add edgeorgie-crispy-profiling -t stdio -c npx -a -y crispy-profiling
```

### Other

```json
{
  "mcpServers": {
    "edgeorgie-crispy-profiling": {
      "command": "npx",
      "args": [
        "-y",
        "crispy-profiling"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 80, +3)

- [functional improvement] Stability: unverified → 0.23

## MCP tools (6)

### `profile_url` (~177 tokens)

Profile React renders of a URL

Opens a URL in headless Chromium, optionally runs interaction steps, and reports which React components rendered, how often, why (props/state/context/parent) and which renders were wasted. Render counts are deterministic: use this before and after a change to verify a performance fix.

Input parameters:

- `outFile` (string): Optional path to write the full JSON report
- `runs` (integer)
- `steps` (array): Interactions to perform after load. Renders during them go to phase "interaction".
- `timings` (boolean): Also measure JavaScript ms per phase (varies between runs, unlike render counts): use it to tell the user how much faster an interaction got.
- `top` (integer): Components shown per phase
- `url` (string, required): Page to profile, e.g. http://localhost:5173/products

### `scan_app` (~115 tokens)

Find and profile interactions automatically

Zero-config start: opens the app, finds safe interactions on a few routes (buttons, tabs, text inputs; never delete/pay/sign-out/submit), profiles each one and returns the top root causes of avoidable renders with fixes, plus the scenarios as crispy.config.json scenarios so they can be saved and guarded with test_render_snapshots.

Input parameters:

- `maxActions` (integer): Interactions per route
- `maxRoutes` (integer)
- `url` (string, required): Start page, e.g. http://localhost:5173/

### `run_scenarios` (~78 tokens)

Run crispy.config.json scenarios

Runs the scenarios defined in a crispy.config.json (budgets included) and returns a summary. Write the report to a file to compare it later with compare_reports.

Input parameters:

- `configPath` (string)
- `outFile` (string)
- `scenarios` (array): Only run these scenario names
- `top` (integer)

### `test_render_snapshots` (~157 tokens)

Check render counts against the committed snapshot

Runs the crispy.config.json scenarios and compares render counts with the committed snapshot (crispy.snap.json), like snapshot tests for re-renders. Regressions include the unstable prop, where the component is rendered and a suggested fix. Read-only by default: it never edits an existing snapshot. With no snapshot yet, update=true records the first one (it only stores the current counts). To accept changed counts later, the USER must approve; then pass update=true together with confirm="accept-render-changes".

Input parameters:

- `configPath` (string)
- `confirm` (string): Must be "accept-render-changes" (after explicit user approval) when update=true
- `scenarios` (array)
- `update` (boolean)

### `compare_reports` (~62 tokens)

Compare two crispy reports

Diffs a baseline report against a new one and lists render regressions and improvements per component.

Input parameters:

- `basePath` (string, required)
- `headPath` (string, required)
- `minRendersDelta` (integer)
- `rendersIncreasePct` (number)

### `inspect_component` (~59 tokens)

Inspect one component in a report

Returns the full per-phase stats for one component (render causes and changed prop keys), which tells you whether to reach for React.memo, useCallback/useMemo or state colocation.

Input parameters:

- `component` (string, required)
- `reportPath` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/edgeorgie-crispy-profiling/crispy-profiling#diagnostics

## Score history

- 2026-11-04: 87
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 84
- 2026-10-29: 84
- 2026-10-28: 84
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-07: 49
- 2026-10-05: 34

## Common questions

### What is the Crispy Profiling MCP server?

Crispy Profiling is an MCP server listed in the public MCP registry as io.github.edgeorgie/crispy-profiling. Deterministic React render profiling: renders, wasted renders and their causes per component. This page covers its npm package (crispy-profiling).

### Is the Crispy Profiling MCP server safe to use?

Crispy Profiling scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Crispy Profiling MCP server expose?

Crispy Profiling exposes 6 tools: profile_url, scan_app, run_scenarios, test_render_snapshots, compare_reports, inspect_component. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.

### Is the Crispy Profiling MCP server still maintained?

Crispy Profiling is still listed as active in the MCP registry. We last reached this channel on 4 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 Crispy Profiling MCP server under?

Crispy Profiling declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/crispy-profiling
- Socket report: https://socket.dev/npm/package/crispy-profiling
- Repository: https://github.com/edgeorgie/crispy-profiling
- Changelog RSS feed: https://verifymcp.io/servers/edgeorgie-crispy-profiling/crispy-profiling.xml
- Changelog JSON feed: https://verifymcp.io/servers/edgeorgie-crispy-profiling/crispy-profiling.json
- HTML version of this page: https://verifymcp.io/servers/edgeorgie-crispy-profiling/crispy-profiling