Perfonext Build MCP
NPM · @PERFONEXT/BUILD-MCP · SCANNED SEP 20
MCP server for Next.js build stats, chunk attribution, and bundle optimization advice.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to souvikdu/perfonext-build-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 994 tokens (~90/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
How do I install the Perfonext Build MCP server?
Perfonext Build MCP runs locally as an npm package, launched with npx -y @perfonext/build-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 · @perfonext/build-mcp
claude mcp add souvikdu-perfonext-build-mcp -- npx -y @perfonext/build-mcp
{
"mcpServers": {
"souvikdu-perfonext-build-mcp": {
"command": "npx",
"args": [
"-y",
"@perfonext/build-mcp"
]
}
}
} {
"servers": {
"souvikdu-perfonext-build-mcp": {
"command": "npx",
"args": [
"-y",
"@perfonext/build-mcp"
]
}
}
} codex mcp add souvikdu-perfonext-build-mcp -- npx -y @perfonext/build-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"souvikdu-perfonext-build-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@perfonext/build-mcp"
],
"enabled": true
}
}
} openclaw mcp add souvikdu-perfonext-build-mcp --command npx --arg -y --arg @perfonext/build-mcp
mcp_servers:
souvikdu-perfonext-build-mcp:
command: "npx"
args: ["-y", "@perfonext/build-mcp"] {
"McpServers": {
"souvikdu-perfonext-build-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@perfonext/build-mcp"
]
}
}
} assistant mcp add souvikdu-perfonext-build-mcp -t stdio -c npx -a -y @perfonext/build-mcp
{
"mcpServers": {
"souvikdu-perfonext-build-mcp": {
"command": "npx",
"args": [
"-y",
"@perfonext/build-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 13 Sept 26 +4
- Stability: unverified → 0.30 ▲ functional
- 4 Sept 26 81
First indexed and scored.
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 20 Sept 2026 · Analysed npm/@perfonext/build-mcp@0.6.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | souvikdu/perfonext-build-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/souvikdu/perfonext-build-mcp/.github/workflows/publish.yml@refs/tags/v0.6.2 |
| Rekor log index | 2716839906 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b23261252d3b57e43bae0dc8994edff75d11e28689084437519c6afa48aab3ee794c59a069045e5593d8ab630a7955434767ec8c376cc6291cb85db2c |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
compare_builds Compare Builds ~96
Compare two loaded Next.js builds and show which routes and chunks grew or shrank the most.
| Name | Type | Req | Description |
|---|---|---|---|
| baselineBuildId | string | – | Baseline build ID from load_build_stats. Omit to list loaded builds. |
| currentBuildId | string | – | Current build ID from load_build_stats. Omit to list loaded builds. |
| limit | integer | – | How many route and chunk deltas to include. Defaults to 10. |
No output schema declared.
No examples provided.
explain_growth Explain Growth ~109
Identify which routes and chunks are responsible for bundle size growth between two loaded builds. Returns severity-ranked route findings, the top growing chunks, and an overall regression summary.
| Name | Type | Req | Description |
|---|---|---|---|
| baselineBuildId | string | – | Baseline build ID from load_build_stats. Omit to list loaded builds. |
| currentBuildId | string | – | Current build ID from load_build_stats. Omit to list loaded builds. |
| limit | integer | – | Max route findings and top growing chunks to return. Defaults to 10. |
No output schema declared.
No examples provided.
explain_shared_chunks Explain Shared Chunks ~107
Show which npm packages and app code dominate the shared chunks loaded by many routes, to identify what bloats common bundles. Each package reports its unminified webpack module size, its share of the chunk's module bytes, and that share applied to the chunk's emitted size. Requires load_build_stats and load_webpack_stats first.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | Build ID returned by load_build_stats |
| limit | integer | – | Maximum shared chunks to analyse. Defaults to 5. |
No output schema declared.
No examples provided.
find_duplicates Find Duplicate Packages ~68
Find npm packages whose code is bundled into more than one chunk, wasting bytes, ranked by wasted bytes. Requires load_webpack_stats first.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | Build ID returned by load_build_stats |
| limit | integer | – | Maximum duplicate packages to return. Defaults to 20. |
No output schema declared.
No examples provided.
get_largest_routes Get Largest Routes ~67
Rank the heaviest user-facing routes in a loaded Next.js build by emitted chunk bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | – | Build ID returned from load_build_stats. Omit to list loaded builds. |
| limit | integer | – | How many routes to include. Defaults to 10. |
No output schema declared.
No examples provided.
get_shared_chunks Get Shared Chunks ~69
Rank the heaviest shared chunks in a loaded Next.js build and show which routes depend on them.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | – | Build ID returned from load_build_stats. Omit to list loaded builds. |
| limit | integer | – | How many shared chunks to include. Defaults to 10. |
No output schema declared.
No examples provided.
how_to_collect_stats How To Collect Webpack Stats ~105
Explain how to generate the webpack stats file (.next/stats.json) required by the bundle attribution tools. Choose manual (a recipe you apply yourself) or automatic (an action plan Copilot executes).
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | manual: return a recipe to apply yourself. automatic: return an action plan for Copilot to execute. |
| scenario | string | – | Collection context. Defaults to webpack. Use turbopack if the app builds with --turbopack. |
No output schema declared.
No examples provided.
load_build_stats Load Build Stats ~74
Parse a Next.js .next directory and load route and chunk footprint data for later analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| buildDir | string | yes | Absolute or relative path to the project .next build directory, not .next/standalone |
| buildOutputPath | string | – | Optional path to captured next build terminal output for deriving build duration |
No output schema declared.
No examples provided.
load_webpack_stats Load Webpack Stats ~85
Parse the webpack module stats file (.next/stats.json) and link it to a build loaded with load_build_stats. Unlocks the stats-powered tools: suggest_optimizations (enriched), find_duplicates, explain_shared_chunks, and trace_import.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | Build ID returned by load_build_stats; the stats.json is read from that build directory |
No output schema declared.
No examples provided.
suggest_optimizations Suggest Optimizations ~105
Aggregate route, chunk, and (when loaded) webpack-stats evidence into severity-ranked, evidence-backed bundle optimizations tied to concrete Next.js actions. Every suggestion is sized in emitted on-disk bytes. Works on manifests alone; load_webpack_stats first for dedupe, shared-chunk, and package-import suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | Build ID returned by load_build_stats |
| limit | integer | – | Maximum suggestions to return. Defaults to 15. |
No output schema declared.
No examples provided.
trace_import Trace Import ~109
Explain why a module is bundled by tracing its import chain from an entry point to the module. moduleSizeBytes is the unminified webpack module size, not emitted chunk size. Requires load_webpack_stats first.
| Name | Type | Req | Description |
|---|---|---|---|
| buildId | string | yes | Build ID returned by load_build_stats |
| limit | integer | – | Maximum matching modules to trace. Defaults to 10. |
| moduleName | string | yes | Module or package name to search for (case-insensitive substring), e.g. "lodash" |
No output schema declared.
No examples provided.
What is the Perfonext Build MCP server?
Perfonext Build MCP is listed in the public MCP registry as io.github.souvikdu/perfonext-build-mcp. MCP server for Next.js build stats, chunk attribution, and bundle optimization advice. This page covers its npm package (@perfonext/build-mcp).
Is the Perfonext Build MCP server safe to use?
Perfonext Build MCP scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Perfonext Build MCP server expose?
Perfonext Build MCP exposes 11 tools: load_build_stats, get_largest_routes, get_shared_chunks, compare_builds, explain_growth, and 6 more. Their descriptions and schemas cost roughly 994 tokens of context every time the server is loaded.
Is the Perfonext Build MCP server still maintained?
Perfonext Build MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Perfonext Build MCP server under?
Perfonext Build 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.