Shipshape MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Your RapidAPI key, used to authenticate requests to the Shipshape API via the RapidAPI marketplace | |
| API_MARKET_KEY | No | Your api.market key, used when RAPIDAPI_KEY is not set | |
| HFL_MARKETPLACE | No | Either 'rapidapi' or 'apimarket', used to select the marketplace when both keys are set |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Lint a Dockerfile or Kubernetes manifest before you hand it over: root in the final stage, unpinned base images, curl | sh, secrets in ENV/ARG, Pod Security Standards, resources and probes. Every finding has the line, a fix and the standard behind it, and the file gets an A–F grade. Content is processed in memory and not stored. Each call is one request on the user's Shipshape plan.
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 |
|---|---|
| lintA | Lint a Dockerfile or Kubernetes manifest. Returns the grade, score, |
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 1 tool
There is only one tool, so there is no ambiguity or overlapping purpose to resolve. Its purpose is clearly stated: lint a Dockerfile or Kubernetes manifest.
The single tool uses a concise, predictable verb-style name (`lint`) that directly describes its action. With only one tool there are no conflicting naming conventions.
A single lint tool is reasonable for a narrowly scoped linting server. The surface is thin, but the tool is well-defined and earns its place for the stated purpose.
The tool covers the core linting workflow and returns grade, score, pass/fail, findings, fixes, and references. It lacks operations like autofix or batch linting, but those are minor gaps for a focused linter.