pkg-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_healthA | Get a health report for an npm or PyPI package: weekly downloads, last publish date, deprecation/yank status, license, and a healthy/caution/avoid verdict with reasons. Use this before recommending or installing a package. |
| compare_packagesA | Compare 2-5 packages from the same registry (npm or PyPI) side by side on adoption, maintenance freshness, deprecation status, and bundle size (npm only). Returns a structured comparison and a recommendation. Use when choosing between alternative libraries. |
| bundle_sizeA | Get the minified and gzipped bundle size of an npm package (via bundlephobia), plus its dependency count. npm only — bundle size has no PyPI equivalent. Use when frontend bundle weight matters. |
| deprecation_checkA | Check whether an npm package is deprecated or a PyPI package is yanked, including the message which often names the recommended replacement. |
| vulnerability_checkA | Check a package for known security vulnerabilities via OSV.dev. Give a version to check that exact version, or omit it to check the latest release. Returns advisory IDs, CVEs, severity, and fixed versions. Use before recommending a package or when auditing dependencies. |
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 5 tools
Tools are mostly distinct, but deprecation_check overlaps with package_health since the latter already includes deprecation status. The other tools—compare_packages, bundle_size, and vulnerability_check—target clearly separate concerns, so an agent can usually pick correctly.
Naming mixes patterns: compare_packages is verb_noun while the rest are noun_noun or adjective_noun (package_health, bundle_size, deprecation_check, vulnerability_check). The convention is readable but not consistently verb-first.
Five tools is well within the ideal range for a focused package-intelligence server. Each tool serves a concrete evaluation need without bloating the surface.
Covers key evaluation aspects: health, security, deprecation, bundle size, and comparison. Minor gaps like raw metadata (description, homepage) or version history are absent, but they are not critical for the server's stated purpose.