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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/qso-graph/sota-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server