# @perfonext/profiler-mcp

MCP server for loading and analyzing V8 and Chrome CPU profiles for GitHub Copilot and other MCP clients

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.7.2
- **Author:** Unknown
- **License:** MIT
- **npm:** @perfonext/profiler-mcp
- **Source:** https://github.com/souvikdu/perfonext-profiler-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: 0 days

## Security scan

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

## Tools

9 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `compare_profiles` — Compare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.
- `explain_function` — Returns detailed timing info for a specific function: self-time, total-time, callers, and callees. Use this to understand why a function is slow.
- `get_hotspots` — Returns the top N functions by self-time (CPU time spent directly in the function, not its callees). Use this to find performance bottlenecks.
- `get_package_costs` — Aggregate CPU self-time by npm package. Identifies which third-party
- `get_profile_summary` — Returns an overview of a loaded profile: duration, sample count, top-level call tree (filtered to functions >0.1% of total time), and idle time percentage. For 
- `how_to_collect` — Returns a ready-to-run command and step-by-step recipe for capturing a V8
- `load_profile` — Parse and load a V8/Chrome CPU profile from disk. Supports both .cpuprofile files and Chrome DevTools Trace JSON exports. Returns a profile ID for use with othe
- `read_source_context` — Read the actual source code for a hot function and annotate each line with
- `suggest_optimizations` — Analyzes the profile and returns structured optimization suggestions for the hottest

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"profiler\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@perfonext/profiler-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%2Fprofiler-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40perfonext%2Fprofiler-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40perfonext%2Fprofiler-mcp
- HTML page: https://forgeregistry.com/registry/%40perfonext%2Fprofiler-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.