@paretools/build

MCPattested
v0.22.2UnknownMITUpdated 8mo agonpmGitHub

MCP server for build tools — structured TypeScript, esbuild, vite, and webpack output for AI agents

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.
8mo agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.22.2
Sourcenpm+mcp-registry
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 · 39620a5
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · none privileged
Security scan✓ Cleanv0.22.2 · 29d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 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.22.2 · 29d 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.

buildRuns a build command and returns structured success/failure with errors and warnings.

Runs a build command and returns structured success/failure with errors and warnings.

No input schema was published for this tool.

esbuildRuns the esbuild bundler and returns structured errors, warnings, and output files.

Runs the esbuild bundler and returns structured errors, warnings, and output files.

No input schema was published for this tool.

tscRuns the TypeScript compiler and returns structured diagnostics (file, line, column, code, message).

Runs the TypeScript compiler and returns structured diagnostics (file, line, column, code, message).

No input schema was published for this tool.

vite-buildRuns Vite production build and returns structured output files with sizes.

Runs Vite production build and returns structured output files with sizes.

No input schema was published for this tool.

webpackRuns webpack build with JSON stats output and returns structured assets, errors, and warnings.

Runs webpack build with JSON stats output and returns structured assets, errors, and warnings.

No input schema was published for this tool.

turboRuns Turborepo tasks and returns structured per-package results with cache hit/miss info.

Runs Turborepo tasks and returns structured per-package results with cache hit/miss info.

No input schema was published for this tool.

lernaRuns Lerna monorepo commands (list, run, changed, version) and returns structured package information.

Runs Lerna monorepo commands (list, run, changed, version) and returns structured package information.

No input schema was published for this tool.

rollupRuns Rollup bundler and returns structured bundle output with errors and warnings.

Runs Rollup bundler and returns structured bundle output with errors and warnings.

No input schema was published for this tool.

nxRuns Nx workspace commands and returns structured per-project task results with cache status.

Runs Nx workspace commands and returns structured per-project task results with cache status.

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 build tools — structured TypeScript, esbuild, vite, and webpack output for AI agents

Keywords
mcpmcp-servermodel-context-protocolstructured-outputaiai-agentclaudecursorcopilottoken-efficientdevtoolsclibuildtypescriptesbuildvitewebpackbundler
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

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

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

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