io.github.yifancong/rsdoctor
NPM · @RSDOCTOR/MCP-SERVER · SCANNED AUG 3
An MCP server that provides build analysis and optimization recommendations for Rspack projects.
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 →
Supply Chain Security88
- 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
- 10 of 10 dependencies flagged as unhealthy (10 deprecated). View diagnostics → Partial
Provenance & Transparency96
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to web-infra-dev/rsdoctor). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 229 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability31
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1841 tokens (~108/item across 17 items; 15 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage62
- 93% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 0% of tool parameters carry a description.Fail
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rsdoctor/mcp-server
claude mcp add yifancong-rsdoctor -- npx -y @rsdoctor/mcp-server
codex mcp add yifancong-rsdoctor -- npx -y @rsdoctor/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yifancong-rsdoctor": {
"type": "local",
"command": [
"npx",
"-y",
"@rsdoctor/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add yifancong-rsdoctor --command npx --arg -y --arg @rsdoctor/mcp-server
mcp_servers:
yifancong-rsdoctor:
command: "npx"
args: ["-y", "@rsdoctor/mcp-server"] {
"mcpServers": {
"yifancong-rsdoctor": {
"command": "npx",
"args": [
"-y",
"@rsdoctor/mcp-server"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +12
- Malware scan: unverified → pass ▲ security
- Dependency health: 0.91 → 0.00 ▼ functional
- 31 Jul 26 −27
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +17
- Schema quality: unverified → 0 ▲ functional
- Tool coverage: unverified → 93 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Schema quality: fail functional
- 26 Jul 26 59
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 3 Aug 2026 · Analysed npm/@rsdoctor/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- web-infra-dev/rsdoctor
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/web-infra-dev/rsdoctor/.github/workflows/release.yml@refs/heads/release_mcp_v0.1.2.-beta.0
- Rekor log index:
- 545478005
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:e1ae57bdaeeb3e996da787efeb190144162890438ad81d0306e6145f28edcca2756a3fa58590afb7efbdf1320e9824c79378d4c481c1a501243ea430c
- Discovery method:
- attestation_endpoint
Dependencies 10 packages
10 packages in the resolved dependency tree · 10 deprecated · 2 stale.
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.
get_bundle_optimize ~82
getBundleOptimize calls multiple functions to provide conclusions to users: - getRuleInfo for duplicate packages - GetSimilarPackages to check if there are similar packages that need optimization - getMediaAssetPrompt to check if media assets need optimization - GetAllChunks to check if there are oversized resources and provide splitChunk suggestions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_chunk_by_id ~23
get chunk by id
| Name | Type | Req | Description |
|---|---|---|---|
| chunkId | number | yes | — |
No output schema declared.
No examples provided.
get_chunks ~12
get all chunks
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_duplicate_packages ~6
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_loader_time_all_files ~22
Get compilation time spent by each loader on individual files
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_loader_times ~15
Get compiled directories loader times
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_module_by_id ~295
get module detail by id (Rspack or Webpack module id)： - id: the id of the module (corresponds to Rspack or Webpack's internal module id) - issuerPath: the referrer chain (array of module ids, from entry to this module) - dependencies: direct dependencies (array of module ids this module imports/requires) - allDependencies: all transitive dependencies (if user asks for detail) - chunks: array of chunk ids this module belongs to - imported: array of module ids that import this module - isEntry: whether this module is an entry point - size: { sourceSize, transformedSize, parsedSize } - layer, modules, rootModule, webpackId: advanced info - bailoutReason: if present, the reason why this module is not tree-shaken or optimized away (e.g. "side effects", "dynamic import", "unknown exports", etc.) - Please use Rspack or Webpack's terminology for all fields. - If user asks for "why not tree-shaken", always return bailoutReason and explain in plain language. - If user asks for "who imported this module", return issuerPath as a dependency chain. - If user asks for "all dependencies", return allDependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| moduleId | number | yes | — |
No output schema declared.
No examples provided.
get_module_by_path ~127
get module detail by module name or path (absolute or relative, as in Rspack or Webpack stats) - If multiple modules match, return all matched module paths and stop, let user select. - Otherwise, return the same fields as getModuleById. - Always include bailoutReason if present. - If user asks for "why is this module in the bundle", show the full issuerPath chain. - If user asks for "why not tree-shaken", show bailoutReason and explain.
| Name | Type | Req | Description |
|---|---|---|---|
| modulePath | string | yes | — |
No output schema declared.
No examples provided.
get_module_issuer_path ~86
get module issuer path (who imported this module, recursively) - Return as a dependency chain (array of module ids from entry to this module) - If possible, render as a tree or graph for clarity. - For each module in the chain, show its path and (if present) bailoutReason.
| Name | Type | Req | Description |
|---|---|---|---|
| moduleId | string | yes | — |
No output schema declared.
No examples provided.
get_package_dependency ~13
get package dependency
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_package_info ~13
get package info
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_packages_by_package_name ~294
get similar packages. Similar packages are categorized as follows, with each line representing a category of similar packages. The presence of packages below does not necessarily mean there are similar packages - replacement should only be considered when packages from the same category exist: 1. cannot exist simultaneously: lodash、lodash-es、string_decode：Consider migrating to lodash-es for better Tree Shaking support. /n 2. cannot exist simultaneously: dayjs, moment, date-fns, js-joda. Consider using dayjs to replace moment for smaller bundle size. /n 3. cannot exist simultaneously: antd, material-ui, semantic-ui-react, material-ui, arco-design /n 4. cannot exist simultaneously: axios, node-fetch 5. cannot exist simultaneously: redux, mobx, Zustand, Recoil, Jotai 6. cannot exist simultaneously: chalk, colors, picocolors, kleur 7. cannot exist simultaneously: fs-extra, graceful-fs It's fine to have any of the above packages in your project, but packages from the same category (i.e. same line) should not coexist. If there are no similar packages, just return that there are no similar packages, without listing which packages exist. Please provide a simple response without listing all packages.
| Name | Type | Req | Description |
|---|---|---|---|
| packageName | string | yes | — |
No output schema declared.
No examples provided.
get_port ~16
Get the port of the MCP server
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rule_info ~540
get rules info, the rules info is a Record<{id: number, name: string, description: string, severity: string, category: string, module: string, path: string, line: number, column: number, message: string, fix: string}>, where: - id: an incremental sequence mark - name: the name of the rule - description: the description of the rule - severity: the severity of the rule - category: the category of the rule - E1001 Duplicate Packages: #### Description there is a same name package which bundled more than one version in your application. it is not good to the bundle size of your application. #### General Solution add an entry in `resolve.alias` which will configure Webpack to route any package references to a single specified path. For example, if `lodash` is duplicated in your bundle, the following configuration would render all Lodash imports to always refer to the `lodash` instance found at `./node_modules/lodash`: ```js { alias: { lodash: path.resolve(__dirname, 'node_modules/lodash') } } ``` , - E1002 Cross Chunks Packages: #### Description There is a package with the same version that is duplicated across different chunks in your application. This redundancy increases the overall bundle size, which is not optimal for performance. #### General Solution To address this issue, you can use Rspack's **SplitChunksPlugin** to extract common dependencies into a separate chunk. This ensures that the same package is not duplicated across multiple chunks, thereby reducing the bundle size. For example, if **lodash** is being duplicated across different chunks, you can configure the **optimization.splitChunks** option in your Webpack configuration to extract **lodash** into a separate chunk: ``` module.exports = { optimization: { splitChunks: { cacheGroups: { commons: { test: /[\/]node_modu…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_similar_packages ~285
get similar packages. Similar packages are categorized as follows, with each line representing a category of similar packages. The presence of packages below does not necessarily mean there are similar packages - replacement should only be considered when packages from the same category exist: 1. cannot exist simultaneously: lodash、lodash-es、string_decode：Consider migrating to lodash-es for better Tree Shaking support. /n 2. cannot exist simultaneously: dayjs, moment, date-fns, js-joda. Consider using dayjs to replace moment for smaller bundle size. /n 3. cannot exist simultaneously: antd, material-ui, semantic-ui-react, material-ui, arco-design /n 4. cannot exist simultaneously: axios, node-fetch 5. cannot exist simultaneously: redux, mobx, Zustand, Recoil, Jotai 6. cannot exist simultaneously: chalk, colors, picocolors, kleur 7. cannot exist simultaneously: fs-extra, graceful-fs It's fine to have any of the above packages in your project, but packages from the same category (i.e. same line) should not coexist. If there are no similar packages, just return that there are no similar packages, without listing which packages exist. Please provide a simple response without listing all packages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.