package-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X402_PRIVATE_KEY | No | The agent operator's wallet private key, funded with USDC on the target network. When set, the MCP server additionally registers the paid tools (package_health and package_batch_health). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| package_snapshotA | Get a consolidated snapshot of an npm, PyPI or crates.io (Rust) package: latest version, license, description, repository, weekly downloads, maintainers, last publish date, and deprecation status. Free, no payment required. |
| package_vulnsA | List known vulnerabilities (OSV.dev) for an npm, PyPI or crates.io (Rust) package. Pass a version to scope results to that version; omit it to see every advisory ever filed against the package. Free, no payment required. |
| package_depsA | Get the dependency graph for an npm, PyPI or crates.io (Rust) package: direct and transitive dependencies with versions and counts, with deprecated direct dependencies flagged. Free, no payment required. |
| package_downloadsA | Get download counts for an npm, PyPI or crates.io (Rust) package over a time range. Free, no payment required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of package intelligence: snapshot (overview), vulns (security), deps (dependencies), and downloads (popularity). No two tools overlap in purpose.
All tools follow a consistent package_<topic> pattern with lowercase snake_case. The naming is predictable and uniform across the set.
Four tools is well-scoped for a package intelligence server, covering the core facets without unnecessary bloat. Each tool earns its place.
The four tools provide comprehensive read-only coverage of package metadata, vulnerabilities, dependencies, and downloads, leaving no obvious gaps for the stated purpose.