stackcheck-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTPS_PROXY | No | HTTPS proxy URL, honoured for registry requests. | |
| SSL_CERT_DIR | No | Path to an SSL certificate directory, honoured for registry requests. | |
| SSL_CERT_FILE | No | Path to an SSL certificate file, honoured for registry requests. | |
| STACKCHECK_CACHE_DIR | No | On-disk cache directory for reduced registry data. Defaults to the platform cache directory (via platformdirs). | |
| STACKCHECK_CACHE_TTL | No | Cache time-to-live in seconds. 0 disables the cache. Default 21600 (6 hours). | 21600 |
| STACKCHECK_CACHE_MAX_AGE | No | Maximum age in days for cache entries; entries unused for longer are deleted at startup (at most once a day). 0 never prunes. Default 60. | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Before pinning or upgrading dependencies, call check_stack once with the whole stack and use the versions it returns. Each issue explains an incompatibility with an indicative fix (suggestion/alternative); issues without severity are errors.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_stackB | Latest stable versions plus incompatibilities between the packages and their shared deps (peer deps, requires_dist, engines, requires_python, wheels, BOM). Example: {"npm": ["react", "typescript", "typescript-eslint", "vite@^8"], "pypi": ["fastapi"]} |
| get_runtime_infoB | Latest, LTS (lts_eol: true if that LTS is end-of-life), next LTS, maintained cycles and EOL date of the recommended cycle, from endoflife.date. Example: {"products": ["nodejs", "python", "eclipse-temurin"]} |
| explain_issueB | Declared peer deps/engines (npm), requires_dist/requires_python (PyPI) or parent and dependencies (Maven) of one version, to dig into an issue. Example: {"ecosystem": "npm", "package": "typescript-eslint", "version": "8.72.1"} |
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 3 tools
Each tool targets a distinct job: bulk stack compatibility checking, runtime/language lifecycle and EOL data, and single-package dependency drill-down. The only mild overlap is that explain_issue is essentially a detail view of what check_stack surfaces, but the descriptions make the boundary clear enough to avoid misselection.
All three names follow a snake_case verb_noun pattern (check_stack, get_runtime_info, explain_issue). The verbs differ (check/get/explain) but the variation is semantically meaningful rather than inconsistent.
Three tools is on the lean side but each maps to a clearly different diagnostic step, with no redundancy. It sits at the low end of the comfortable 3-15 range rather than being under-scoped.
The surface covers diagnosis well (compatibility, lifecycle/EOL, per-version dependency inspection) but stops at reporting: there is no remediation tool to suggest compatible version combinations, no way to look up a single package's latest version outside a stack, and no lockfile/manifest ingestion. These are notable gaps an agent would hit when asked to actually fix a conflict.