rustore-apk-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_apk_infoA | Get latest RuStore release metadata by exact Android package name, e.g. com.yolo_price_mobile. Returns name, version, minimum Android SDK, price and source. Does not download any APK. A listing does not guarantee that a standalone APK is available. |
| download_apkA | Download the latest free standalone APK from RuStore using just its package name. Returns absolute local path, version, byte size, SHA-256, certificate and cached flag. Verifies the package/version in AndroidManifest and APK signature against RuStore. Reuses a verified cached copy of the same version. max_mib: 1..4096, default 1024. Requires Android SDK aapt/apksigner and Java on the server host. May take several minutes. Does not install or run the APK. Call sequentially for a package list; stop on HTTP 403/429. |
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
The two tools are clearly distinct: one retrieves metadata without downloading, the other downloads the APK. There is no overlap in functionality, and the descriptions explicitly differentiate their purposes.
Both tools follow a consistent verb_noun pattern: get_apk_info and download_apk. The naming is predictable and clearly indicates the action and resource.
With only two tools, the surface is thin, but for a narrowly scoped server (RuStore APK retrieval) it may be sufficient. It is borderline but not excessive; the tools cover the core operations.
The tools cover the primary operations of retrieving metadata and downloading APKs. A minor gap is the lack of a discovery/search tool, but the server's stated purpose is to work with exact package names, so this is a reasonable boundary.