@perfonext/profiler-mcp

MCPattested

v0.7.2UnknownMITUpdated 2d agonpm GitHub

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

Works in

ClaudeCursorCopilotGemini

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.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

329Downloads/wk

2d agoLast update

Package

AuthorUnknown

LicenseMIT

Version0.7.2

Sourcenpm+mcp-registry

npm@perfonext/profiler-mcp

GitHubsouvikdu/perfonext-profiler-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

A

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 04a36fe

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface9 tools · none privileged

Security scan✓ Cleanv0.7.2 · todayHow well does this scan work?

EvalsNone

IndexedSep 7, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged

Statically extracted from the published packagev0.7.2 · 2h ago

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.

Filter toolsPrivileged only

compare_profilesCompare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.

Compare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.

No input schema was published for this tool.

explain_functionReturns detailed timing info for a specific function: self-time, total-time, callers, and callees. Use this to understand why a function is slow.

Returns detailed timing info for a specific function: self-time, total-time, callers, and callees. Use this to understand why a function is slow.

No input schema was published for this tool.

get_hotspotsReturns the top N functions by self-time (CPU time spent directly in the function, not its callees). Use this to find performance bottlenecks.

Returns the top N functions by self-time (CPU time spent directly in the function, not its callees). Use this to find performance bottlenecks.

No input schema was published for this tool.

get_package_costsAggregate CPU self-time by npm package. Identifies which third-party

Aggregate CPU self-time by npm package. Identifies which third-party

No input schema was published for this tool.

get_profile_summaryReturns 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 large profiles, the call tree is limited to depth 2 and top 20 children per node to keep output manageable. Also lists all loaded profiles…

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 large profiles, the call tree is limited to depth 2 and top 20 children per node to keep output manageable. Also lists all loaded profiles…

No input schema was published for this tool.

how_to_collectReturns a ready-to-run command and step-by-step recipe for capturing a V8

Returns a ready-to-run command and step-by-step recipe for capturing a V8

No input schema was published for this tool.

load_profileParse 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 other tools.

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 other tools.

No input schema was published for this tool.

read_source_contextRead the actual source code for a hot function and annotate each line with

Read the actual source code for a hot function and annotate each line with

No input schema was published for this tool.

suggest_optimizationsAnalyzes the profile and returns structured optimization suggestions for the hottest

Analyzes the profile and returns structured optimization suggestions for the hottest

No input schema was published for this tool.

9 of 9 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.

About

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

Keywords

mcpgithub-copilotcpu-profilerprofilingv8chromecpuprofileperformancenextjs

Alternatives

Comparing tool surfaces…

Tools exposed

9 tools · none privileged · observed 2026-09-07 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

compare_profiles
explain_function
get_hotspots
get_package_costs
get_profile_summary
how_to_collect
load_profile
read_source_context
suggest_optimizations

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-07 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.7
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

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)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+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.

Topics

Related in git & code hosting

github/awesome-copilotCommunity-contributed instructions, agents, skills, and configurations to help you make th
io.github.github/github-mcp-serverConnect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural
github/github-mcp-serverGitHub's official MCP Server
OthmanAdi/planning-with-filesPersistent file-based planning for AI coding agents and long-running agentic tasks. Crash-
yusufkaraaslan/Skill_SeekersConvert documentation websites, GitHub repositories, and PDFs into Claude AI skills with a
@zereight/mcp-gitlabGitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and mor
idosal/git-mcpPut an end to code hallucinations! GitMCP is a free, open-source, remote MCP server for an
gotalab/cc-sddTurn approved specs into long-running autonomous implementation. A minimal, adaptable SDD