ship-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 |
|---|---|
| echoA | Echo a message back — the hello-world of MCP tools. |
| fetch_jsonA | Fetch a JSON payload from an HTTPS URL and return it prettified. |
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 2 tools
echo and fetch_json are completely distinct operations with no functional overlap. An agent can easily tell them apart based on purpose alone.
Both tool names are short imperative verbs, but 'echo' is a bare verb while 'fetch_json' follows a verb_noun pattern. The inconsistency is minor and readability remains high.
At 2 tools, the server feels thin and borderline for a general-purpose utility set. However, the tools are simple and self-contained, so the count is not drastically mismatched for a minimal demo server.
The name 'ship-mcp' suggests a deployment or shipping workflow, but the tools only cover echoing and fetching JSON. There are no operations related to shipping, deploying, or managing releases, leaving the apparent domain severely undercovered.