ReadyStack Compliance Linters (40 MCP servers)
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_textA | Kubernetes Removed API Lint - run all 15 checks on a text (free) |
| check_fileB | Kubernetes Removed API Lint - run all checks on one file by path (free) |
| check_dirB | Kubernetes Removed API Lint - sweep a folder and return every finding (licence; the full run is free for 7 days) |
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 input type (text, file, directory) for the same lint operation, leaving no ambiguity about which to use based on the data source.
All tools follow a consistent 'check_<input>' pattern, making the naming predictable and easy to learn.
Three tools is perfectly scoped for the server's purpose of running Kubernetes removed API lints on different input forms; each tool earns its place.
The tool set covers all common input scenarios (text, single file, directory) for the linting domain, and the fixed 15-check set means no missing functionality for the stated purpose.