Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MobiLoop

OCI · GHCR.IO/ENESSUBASS/MOBILOOP-MCP

Guarded AI mobile Appium testing, security scanning, verification, and fix-retest MCP tools.

+4 this week 46 Trust /100

Last scanned (2 hours ago)

Scores higher than 65% of OCI servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 20 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4907 tokens (~59/item across 83 items; 83 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "device.uninstall_app" implies "uninstall" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 83 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/enessubass/mobiloop-mcp@0.1.0-alpha.15

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 83 exposed · ~4,907 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
flow.read_memory ~21

Read recorded flow checkpoints, runs, and code-flow analyses.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

flow.record_checkpoint ~122

[workspace write][risk:write] Record a runtime screen checkpoint from Appium source/session and optional action needed to reach the next checkpoint.

NameTypeReqDescription
actionToNextobject––
checkpointIdstring––
namestringyes–
ordernumber––
prefixstring––
screenshotPathstring––
serverUrlstring––
sessionIdstring––
sourcestring––
sourcePathstring––
testNamestringyes–

No output schema declared.

No examples provided.

flow.record_test_run ~92

[workspace write][risk:write] Record the ordered checkpoint ids for a test run. The latest passed run becomes the default replay path.

NameTypeReqDescription
artifactsarray––
checkpointIdsarrayyes–
finishedAtstring––
runIdstring––
startedAtstring––
statusstringyes–
testNamestringyes–

No output schema declared.

No examples provided.

flow.replay_to_checkpoint ~99

[approval required][device mutation][risk:dangerous] Auto-advance an Appium session from a previously seen screen to the latest or requested checkpoint.

NameTypeReqDescription
delayMsnumber––
dryRunboolean––
minimumScorenumber––
serverUrlstring––
sessionIdstringyes–
targetCheckpointIdstring––
testNamestring––

No output schema declared.

No examples provided.

flow.run_script ~114

[approval required][device mutation][risk:dangerous] Run a high-level JSON flow DSL over an Appium session: waitText, tapText, type, hideKeyboard, assertText, observe, collectEvidence, back, swipe, checkpoint.

NameTypeReqDescription
delayMsnumber––
prefixstring––
serverUrlstring––
sessionIdstringyes–
stepsarrayyes–
stopOnFailureboolean––
testNamestring––

No output schema declared.

No examples provided.

ios.boot_simulator ~58

[approval required][device mutation][risk:dangerous] Boot an iOS simulator and optionally wait until boot completes.

NameTypeReqDescription
devicestringyes–
timeoutMsnumber––
waitForBootboolean––

No output schema declared.

No examples provided.

ios.build_app ~100

[device mutation][risk:device] Build an iOS simulator app with xcodebuild into MCP artifacts.

NameTypeReqDescription
buildSettingsobject––
configurationstring––
derivedDataPathstring––
destinationstring––
projectstring––
schemestringyes–
sdkstring––
workspacestring––
xcodebuildArgsarray––

No output schema declared.

No examples provided.

ios.capture_screenshot ~33

Capture an iOS simulator screenshot into artifacts.

NameTypeReqDescription
devicestring––
prefixstring––

No output schema declared.

No examples provided.

ios.collect_logs ~44

Collect recent simulator logs into artifacts.

NameTypeReqDescription
devicestring––
laststring––
predicatestring––
prefixstring––

No output schema declared.

No examples provided.

ios.install_app ~47

[approval required][device mutation][risk:dangerous] Install an .app bundle on an iOS simulator.

NameTypeReqDescription
appPathstringyes–
devicestring––

No output schema declared.

No examples provided.

ios.launch_app ~55

[approval required][device mutation][risk:dangerous] Launch an installed iOS simulator app by bundle id.

NameTypeReqDescription
bundleIdstringyes–
devicestring––
terminateRunningboolean––

No output schema declared.

No examples provided.

ios.list_simulators ~23

List available iOS simulators via xcrun simctl.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ios.shutdown_simulator ~35

[approval required][device mutation][risk:dangerous] Shutdown an iOS simulator.

NameTypeReqDescription
devicestringyes–

No output schema declared.

No examples provided.

loop.generate_report ~47

[workspace write][risk:write] Generate a Markdown report from recorded iterations.

NameTypeReqDescription
finalStatusstring––
summarystring––
titlestring––

No output schema declared.

No examples provided.

loop.read_iterations ~14

Read recorded loop iterations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

loop.record_iteration ~104

[workspace write][risk:write] Append one build-test-verify loop iteration as JSONL evidence.

NameTypeReqDescription
artifactsarray––
buildstring––
devicestring––
failurestring––
fixstring––
goalstringyes–
iterationnumberyes–
reteststring––
root_causestring––
test_resultstringyes–

No output schema declared.

No examples provided.

orchestrator.run_android_validation_loop ~233

[approval required][device mutation][risk:dangerous] Run build -> install -> Appium scripted test -> verification -> evidence -> loop record for Android.

NameTypeReqDescription
apiChecksarray––
apkPathstring––
appiumCapabilitiesobject––
appiumStepsarray––
avdNamestring––
buildDebugApkboolean––
clearAppDataboolean––
collectEvidenceboolean––
expectedTextsarray––
flowReplayBeforeStepsboolean––
flowReplayMinimumScorenumber––
flowReplayTargetCheckpointIdstring––
flowReplayTestNamestring––
goalstringyes–
installDependenciesboolean––
iterationOffsetnumber––
kindstring––
maxTestIterationsnumber––
packageNamestring––
runLintboolean––
runUnitTestsboolean––
serialstring––

No output schema declared.

No examples provided.

orchestrator.run_ios_validation_loop ~358

[approval required][device mutation][risk:dangerous] Run iOS simulator build -> install/launch -> Appium XCUITest scripted test -> verification -> evidence -> loop record.

NameTypeReqDescription
appPathstring––
appiumCapabilitiesobject––
appiumStepsarray––
bootSimulatorboolean––
buildIosAppboolean––
buildSettingsobject––
bundleIdstring––
captureSimulatorScreenshotboolean––
collectEvidenceboolean––
collectSimulatorLogsboolean––
configurationstring––
derivedDataPathstring––
destinationstring––
devicestring––
evidenceTimeoutMsnumber––
expectedTextsarray––
flowReplayBeforeStepsboolean––
flowReplayMinimumScorenumber––
flowReplayTargetCheckpointIdstring––
flowReplayTestNamestring––
goalstringyes–
installAppboolean––
installDependenciesboolean––
iterationOffsetnumber––
kindstring––
launchAppboolean––
maxTestIterationsnumber––
projectstring––
runLintboolean––
runUnitTestsboolean––
schemestring––
sdkstring––
simulatorDevicestring––
simulatorLogLaststring––
simulatorLogPredicatestring––
workspacestring––
xcodebuildArgsarray––

No output schema declared.

No examples provided.

policy.list_tools ~53

List effective tool policy metadata for MCP clients and approval gates.

NameTypeReqDescription
includeDescriptionsboolean––
requiresApprovalboolean––
riskLevelstring––
toolNamestring––

No output schema declared.

No examples provided.

security.compare_scans ~49

Re-run the deterministic source scan and compare it with a baseline report after fixes.

NameTypeReqDescription
baselinePathstringyes–
maxFilesnumber––
pathsarray––

No output schema declared.

No examples provided.

security.generate_test_plan ~39

Generate a deterministic mobile security test plan from a source-scan report for an AI or engineer to execute.

NameTypeReqDescription
reportPathstringyes–

No output schema declared.

No examples provided.

security.release_gate ~42

Evaluate a source-scan report against a severity threshold before release or merge.

NameTypeReqDescription
failAtOrAbovestring––
reportPathstringyes–

No output schema declared.

No examples provided.

security.scan_source ~39

Scan mobile source and platform configuration for deterministic security signals without running target code.

NameTypeReqDescription
maxFilesnumber––
pathsarray––

No output schema declared.

No examples provided.

verify.assert_accessibility_labels ~56

Assert clickable or input-like nodes have a text, label, name, content-desc, or resource-id.

NameTypeReqDescription
serverUrlstring––
sessionIdstring––
sourcePathstring––

No output schema declared.

No examples provided.

verify.assert_api_response ~81

[network][risk:network] Call an API and assert status and optional body substrings.

NameTypeReqDescription
bodystring––
bodyContainsarray––
expectedStatusnumber––
headersobject––
methodstring––
timeoutMsnumber––
urlstringyes–

No output schema declared.

No examples provided.

verify.assert_appium_session_healthy ~47

Assert the Appium session and page source are reachable, distinguishing automation failures from app crashes.

NameTypeReqDescription
serverUrlstring––
sessionIdstringyes–

No output schema declared.

No examples provided.

verify.assert_navigation_reached ~56

Assert a navigation target by expected Appium page source text.

NameTypeReqDescription
expectedTextstringyes–
serverUrlstring––
sessionIdstringyes–
sourceEvidencePrefixstring––

No output schema declared.

No examples provided.

verify.assert_no_crash_in_logcat ~50

Assert logcat or a saved log file has no crash signatures.

NameTypeReqDescription
logPathstring––
packageNamestring––
serialstring––

No output schema declared.

No examples provided.

verify.assert_screen_contains_text ~44

Assert current Appium page source contains expected text.

NameTypeReqDescription
serverUrlstring––
sessionIdstringyes–
textstringyes–

No output schema declared.

No examples provided.

verify.assert_screenshot_diff ~61

Compare two PNG screenshots and assert the pixel diff ratio is at or below maxDiffRatio.

NameTypeReqDescription
actualPathstringyes–
baselinePathstringyes–
maxDiffRationumber––
thresholdnumber––

No output schema declared.

No examples provided.

verify.assert_sqlite_query ~56

Run a read-only sqlite query and assert exact output or expected substring.

NameTypeReqDescription
databasePathstringyes–
expectedOutputstring––
outputContainsstring––
querystringyes–

No output schema declared.

No examples provided.

verify.collect_evidence ~61

Collect screenshot, page source, and logcat evidence where available.

NameTypeReqDescription
packageNamestring––
prefixstring––
serialstring––
serverUrlstring––
sessionIdstring––

No output schema declared.

No examples provided.

verify.hash_artifact ~29

Compute SHA-256 for a workspace artifact or evidence file.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

Install

How do I install the MobiLoop MCP server?

MobiLoop runs locally as a container image, launched with docker run --rm -i -e MOBILOOP_WORKSPACE_ROOT -e APPIUM_SERVER_URL ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.15. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/enessubass/mobiloop-mcp

# add to Claude Code
claude mcp add enessubass-mobiloop-mcp -- docker run --rm -i -e MOBILOOP_WORKSPACE_ROOT -e APPIUM_SERVER_URL ghcr.io/enessubass/mobiloop-mcp:0.1.0-alpha.15

This image reads MOBILOOP_WORKSPACE_ROOT and APPIUM_SERVER_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the MobiLoop MCP server?

MobiLoop is an MCP server listed in the public MCP registry as io.github.enessubass/mobiloop-mcp. Guarded AI mobile Appium testing, security scanning, verification, and fix-retest MCP tools. This page covers its container image (ghcr.io/enessubass/mobiloop-mcp).

Is the MobiLoop MCP server safe to use?

MobiLoop scores 46 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MobiLoop MCP server expose?

MobiLoop exposes 83 tools: code.read_file, code.search_code, code.apply_patch, code.git_diff, code.create_branch, and 78 more. Their descriptions and schemas cost roughly 4,907 tokens of context every time the server is loaded.

Is the MobiLoop MCP server still maintained?

MobiLoop is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the MobiLoop MCP server under?

MobiLoop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.