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": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
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. |
| sota_spotsB | Get current and recent SOTA spots. Returns live spot feed with summit details. |
| sota_alertsB | Get upcoming SOTA activation alerts. |
| sota_summit_infoA | 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 targets a distinct resource or action: version metadata, live spots, upcoming alerts, summit lookup by reference, and geographic summit search. The spots-vs-alerts overlap is resolved by descriptions (current/recent vs upcoming), leaving no realistic misselection risk.
All names use snake_case and four of five share a clear `sota_` domain prefix, which groups the domain tools well. However, `get_version_info` follows a verb_noun pattern while the others are bare noun phrases, and `sota_summits_near` is an odd suffix-style construction rather than a verb-led name.
Five tools is a lean, well-scoped surface for a read-only SOTA feed-and-reference API, and each tool covers a distinct access pattern. It sits at the low end but does not feel artificially thin.
Core read paths are covered (spots, alerts, summit by reference code, nearby summits), but there is no way to search summits by name, list associations/regions, or filter spots/alerts by band, mode, or association. Agents without a known reference code or coordinates have limited discovery paths.