sota-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOTA_MCP_MOCK | No | Set to '1' to enable mock mode for testing without network |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get sota-mcp service version and upstream spec version. Returns the running PyPI version of sota-mcp and the SOTA api2 endpoint contract in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol. Returns: service_name, service_version (PyPI), and spec_version (SOTA api2). |
| sota_spotsB | Get current and recent SOTA spots. Returns live spot feed with summit details. |
| sota_alertsB | Get upcoming SOTA activation alerts. |
| sota_summit_infoB | Get detailed summit information by SOTA reference code. |
| sota_summits_nearC | Find SOTA summits near a geographic location. |
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 5 tools
Each tool has a distinct purpose: version info, alerts, spots, summit details, and nearby summits. No overlap or ambiguity.
Most tools use consistent snake_case with a 'sota_' prefix, but 'get_version_info' breaks the pattern slightly. Still readable and predictable.
5 tools is well-scoped for a SOTA service, covering essential operations without unnecessary bloat.
Core functionality is covered (alerts, spots, summit info, location search). Minor gaps like filtering spots by summit or user accounts are acceptable.