GoMobSec MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOMOBSEC_API_KEY | Yes | Required. Your GoMobSec API key. Create one under API keys in GoMobSec. | |
| GOMOBSEC_API_URL | No | Change this only for a dedicated or on-prem GoMobSec | https://api.gomobsec.ai |
| GOMOBSEC_APP_URL | No | Base URL for the report links | https://gomobsec.ai |
| GOMOBSEC_DOWNLOAD_DIR | No | The only folder download_report writes to | ~/Downloads/gomobsec |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Show which GoMobSec account is connected and its plan. |
| get_usageB | How many scans the account has used this month against its plan limit. |
| list_scansA | List the account's most recent scans, newest first (1-50). |
| get_scanB | Status of one scan and, once complete, its findings count by severity. |
| get_findingsA | Findings of a completed scan: severity, title, CWE, MASVS category, CVSS, location and description, most severe first. Optionally filter by severity. False positives are left out unless include_false_positives is true. |
| wait_for_scanA | Wait until a scan finishes (or the timeout passes, 1-60 minutes), reporting progress, then return its status and findings count. Scans can take longer than one wait; call it again if the scan is still running. |
| start_scanA | Upload a local Android (.apk, .xapk, .apks, .apkm) or iOS (.ipa) app to GoMobSec and start a security scan. Uses one scan from the account's plan — confirm with the user first. 'quick' and 'static' work on every plan; 'full' (static + dynamic) needs a paid plan. Returns the scan id; follow it with wait_for_scan. |
| download_reportA | Download the full report of a completed scan — DOCX (pentest report), XLSX, JSON or SARIF (for code-scanning tools) — into the GoMobSec download folder (GOMOBSEC_DOWNLOAD_DIR, default ~/Downloads/gomobsec). Never overwrites an existing file. Returns the saved path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| security_review | Review a completed scan and propose a prioritised fix plan. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct action/resource: account identity, usage, scan listing, individual scan status, findings, waiting, starting scans, and report download. The only potentially neighboring tools—get_scan, wait_for_scan, and get_findings—are clearly differentiated by description: status polling versus blocking wait versus detailed findings.
Most names follow a clear snake_case verb_noun pattern (get_scan, list_scans, start_scan, download_report). The only deviation is 'whoami', which is a well-known conventional command but not part of the same pattern.
Eight tools is well-scoped for a focused mobile security scanning service. Each tool has a clear role in the scan lifecycle and there is no obvious filler.
The surface covers account checks, scan creation, waiting, status/findings retrieval, and report download, forming a complete core workflow. Minor gaps exist, such as scan cancellation or deletion, but these are not necessary for the main lifecycle.