io.github.yifancong/rsdoctor
NPM · @RSDOCTOR/MCP-SERVER · SCANNED SEP 20
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 → Why this is hard to score →
Supply Chain Security99
- 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
- 2 of 10 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- 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 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability38
- 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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.yifancong/rsdoctor MCP server?
io.github.yifancong/rsdoctor runs locally as an npm package, launched with npx -y @rsdoctor/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rsdoctor/mcp-server
claude mcp add yifancong-rsdoctor -- npx -y @rsdoctor/mcp-server
{
"mcpServers": {
"yifancong-rsdoctor": {
"command": "npx",
"args": [
"-y",
"@rsdoctor/mcp-server"
]
}
}
} {
"servers": {
"yifancong-rsdoctor": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@rsdoctor/mcp-server"
]
}
}
} assistant mcp add yifancong-rsdoctor -t stdio -c npx -a -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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Security disclosure: unverified → pass ▲ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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/@rsdoctor/mcp-server@0.1.2-beta.0
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 | 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 |
Background: How many MCP packages publish verified provenance →
Dependencies 10 packages
| Packages resolved | 10 |
|---|---|
| Stale | 2 |
| 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 →
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.
What is the io.github.yifancong/rsdoctor MCP server?
io.github.yifancong/rsdoctor is an MCP server listed in the public MCP registry as io.github.yifancong/rsdoctor. An MCP server that provides build analysis and optimization recommendations for Rspack projects. This page covers its npm package (@rsdoctor/mcp-server).
Is the io.github.yifancong/rsdoctor MCP server safe to use?
io.github.yifancong/rsdoctor scores 83 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 io.github.yifancong/rsdoctor MCP server expose?
io.github.yifancong/rsdoctor exposes 15 tools: get_chunks, get_chunk_by_id, get_module_by_id, get_module_by_path, get_module_issuer_path, and 10 more. Their descriptions and schemas cost roughly 1,829 tokens of context every time the server is loaded.
Is the io.github.yifancong/rsdoctor MCP server still maintained?
io.github.yifancong/rsdoctor 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 io.github.yifancong/rsdoctor MCP server under?
io.github.yifancong/rsdoctor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.