$ loading_
Check package versions and assess package quality across multiple language ecosystems.
This MCP tool is described as checking package versions and quality across multiple package ecosystems. The materials indicate no required secrets and no declared remote endpoints, but as an MCP tool with code execution characteristics it still warrants normal caution; open source under MIT is a positive signal, while low adoption and unknown maintenance limit supply-chain confidence.
The materials explicitly state that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication data are requested, so credential exposure appears minimal.
Its stated purpose is to check package versions and quality across PyPI, npm, pub.dev, and crates.io, which would normally involve network access to those ecosystem services. Although the system field says there are no remote endpoints, the described functionality suggests likely routine outbound requests to those known services, so users should be aware of what query data may be sent out.
The system flags it as executes-code, meaning it can run code locally or start an MCP server process. This is a common inherent capability for MCP tools; the provided materials do not show privileged behavior beyond its stated function, but it should still run in a constrained environment.
The materials do not specify any required access to local files, directories, or other data resources, nor do they declare broad read/write permissions. However, as a locally executed MCP tool, it may inherit the default access of the account running it, so least-privilege deployment is advisable.
The project is open source and MIT-licensed, which is a meaningful risk-reducing factor because the code is auditable. However, it comes from a third-party registry, has 0 GitHub stars, unknown maintenance status, and no README content provided, so supply-chain transparency and maturity are only moderate; code review and dependency pinning are recommended.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "MCP Package Hero" yet — see the docs or source repo.
Please check the latest versions, maintenance activity, and overall quality scores for requests, react, http, and serde, then compare them in a table.
A comparison table across PyPI, npm, pub.dev, and crates.io with versions, activity, and quality metrics.
I want to use a JavaScript state management library in a new project. Check zustand for package quality, version stability, maintenance status, and summarize whether it is suitable for production.
A quality assessment summary explaining whether the package is recommended for production use and why.
Please check the current versions and quality signals for the Python dependency candidates flask, fastapi, and django, and point out any outdated or maintenance risks.
An overview of each package’s version and quality, with potential outdated or maintenance risks highlighted.
Get real-time package health, vulnerabilities, and dependency insights for safer decisions.
Analyze PyPI packages for dependencies, security, licenses, health, and trends.
Search npm packages, audit dependencies, and compare package details and size.
Check live package health and risk scores while you code.
Query PyPI packages, dependencies, compatibility, and download trend insights.
Access live NPM package data for version checks and dependency risk reviews.