FreshStack 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_stackA | Detect Python version, package manager, resolved dependencies, and supported libraries. Args: project_dir: Root directory of the Python project to inspect (defaults to current directory). Returns: JSON string containing StackInfo with resolved versions and evidence sources. |
| resolve_constraintsA | Determine exact project dependency versions and retrieve authoritative version-specific constraints. Identifies version-specific APIs, deprecated/forbidden patterns, recommended patterns, and authoritative evidence sources (documentation URLs, changelogs). Args: task_description: Description of the coding task or feature to implement. libraries: Optional list or mapping of specific libraries to inspect (e.g. ['fastapi', 'pydantic']). project_dir: Root directory of the Python project (defaults to current directory). Returns: JSON string containing ResolvedConstraints with verified rules and evidence. |
| freshness_auditA | Analyze Python code to detect deprecated APIs, version mismatches, and outdated patterns. Uses deterministic static AST analysis grounded in authoritative documentation. Args: code: Python source code snippet or module to audit. project_dir: Root directory of the Python project to ground version context against. Returns: JSON string containing FreshnessAuditReport with detected violations, severity, and replacements. |
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 has a clearly distinct role: one inspects the environment, one resolves authoritative constraints for a task, and one audits existing code. The only conceptual overlap (deprecated patterns in resolve_constraints and freshness_audit) is separated by input type and purpose.
inspect_stack and resolve_constraints follow a clear verb_noun pattern, but freshness_audit uses a noun_noun form and breaks the convention. The overall set is still readable and predictable.
Three tools is well-scoped for a focused analysis and guidance server, covering environment discovery, constraint resolution, and code audit without redundancy. Each tool earns its place.
The workflow is complete for its apparent domain: inspect the stack, resolve version-specific rules, then audit code against them. No dead ends remain because the audit returns violations and replacements; a remediation/write tool would be outside this server's stated analysis scope.