Vanta MCP
by SVolsa
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADB_PATH | No | Path to the adb executable when adb is not available on PATH. | |
| JAVA_HOME | No | Java home to use when Java is outside the standard SDK paths for APK inspection. | |
| VANTA_SERIAL | Yes | The ADB serial of the authorized Android device to use. | |
| VANTA_RISH_PATH | No | Device path to the exported rish and rish_shizuku.dex files when using the Shizuku connection mode. | |
| VANTA_TRANSPORT | Yes | Transport mode for the Android connection, such as adb or shizuku. | |
| ANDROID_NDK_HOME | No | Android NDK home to use when the LLVM tools are outside the standard SDK paths for ELF inspection. | |
| VANTA_INSPECTION_DIR | No | Directory for inspection and replay reports. Defaults to out/inspection/ for a source checkout or ~/.vanta-mcp/inspection/ for an npm installation. | |
| VANTA_RISH_APPLICATION_ID | No | Caller application ID for Shizuku, such as com.android.shell for ordinary ADB. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues