mobile-mcp
mcp1.0.13Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)
By mobile-next | 54 findings | Scanned 10/26/2026 | tooltrust-scanner/v0.3.20 | 10.0k
Repository health
Popularity and maintenance signals alongside the security grade.
10.0k
current snapshot
Not collected
GitHub metadata pending
Not collected
GitHub metadata pending
Not collected
GitHub metadata pending
Not collected
GitHub metadata pending
Not collected
Latest GitHub release
Stars trend
Daily star additions · githubarchive_bq · observed through Oct 26, 2026 · export updated Oct 26, 2026
Pull request activity
Weekly PR events · githubarchive_bq · observed through Oct 26, 2026 · export updated Oct 26, 2026
Data quality: observed_events. Charts show observed events, not a reconstructed historical total.
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (54)
tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
mobile_list_available_devicesmobile_login_to_cloud_providermobile_list_remote_devicesmobile_release_remote_devicemobile_open_urlmobile_set_locationmobile_batch_commandsFix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.
No metadata.dependencies or repo_url were exposed by this MCP server, and no local project manifest could be inferred from the launch command.
get_more_toolsmobile_list_available_devicesmobile_login_to_cloud_providermobile_list_remote_devicesmobile_allocate_remote_devicemobile_release_remote_devicemobile_list_appsmobile_get_foreground_appmobile_launch_appmobile_terminate_appmobile_install_appmobile_uninstall_appmobile_get_screen_sizemobile_click_on_screen_at_coordinatesmobile_double_tap_on_screenmobile_long_press_on_screen_at_coordinatesmobile_list_elements_on_screenmobile_press_buttonmobile_open_urlmobile_swipe_on_screenmobile_type_keysmobile_save_screenshotmobile_take_screenshotmobile_set_orientationmobile_fold_devicemobile_set_locationmobile_clipboardmobile_get_device_logsmobile_get_orientationmobile_start_screen_recordingmobile_stop_screen_recordingmobile_list_crashesmobile_get_crashmobile_batch_commandsFix: Review and remediate the identified issue.
declared capabilities: network access
mobile_list_available_devicesmobile_login_to_cloud_providermobile_list_remote_devicesmobile_allocate_remote_devicemobile_open_urlmobile_batch_commandsdeclared capabilities: network access, filesystem access
mobile_release_remote_devicedeclared capabilities: filesystem access
mobile_install_appmobile_swipe_on_screenmobile_save_screenshotmobile_get_device_logsmobile_stop_screen_recordingdeclared capabilities: HTTP requests
mobile_set_locationFix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y mobile-mcp"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)