# k11 Appium QA (pypi · k11-appium-qa-mcp)

Self-healing Appium locators for Android and iOS apps, healed on the screen each test failed on.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `k11-appium-qa-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp.md), [page](https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp)

## Channel facts

- Registry: `pypi`
- Package: `k11-appium-qa-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K11-Software-Solutions/k11techlab-appium-qa-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 659 tokens (~94/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the k11 Appium QA MCP server?

k11 Appium QA runs locally as a PyPI package, launched with uvx k11-appium-qa-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add k11-software-solutions-appium-qa -- uvx k11-appium-qa-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "k11-software-solutions-appium-qa": {
      "command": "uvx",
      "args": [
        "k11-appium-qa-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k11-software-solutions-appium-qa": {
      "command": "uvx",
      "args": [
        "k11-appium-qa-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k11-software-solutions-appium-qa -- uvx k11-appium-qa-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k11-software-solutions-appium-qa": {
      "type": "local",
      "command": [
        "uvx",
        "k11-appium-qa-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k11-software-solutions-appium-qa --command uvx --arg k11-appium-qa-mcp
```

### Hermes

```yaml
mcp_servers:
  k11-software-solutions-appium-qa:
    command: "uvx"
    args: ["k11-appium-qa-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "k11-software-solutions-appium-qa": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "k11-appium-qa-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k11-software-solutions-appium-qa -t stdio -c uvx -a k11-appium-qa-mcp
```

### Other

```json
{
  "mcpServers": {
    "k11-software-solutions-appium-qa": {
      "command": "uvx",
      "args": [
        "k11-appium-qa-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-20 (score 63, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 78, +1)

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

### 2026-11-18 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 62, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-16 (score 76)

First indexed and scored.

## MCP tools (7)

### `inspect_screen` (~99 tokens)

Inspect screen

List a screen's elements with locators verified to match exactly one element, most stable first
(accessibility id, resource id, text, XPath). screen: a saved page source XML in the project; omit to read
the live device. lang: python (default) or java, for how locators are written.

Input parameters:

- `interactive_only` (boolean)
- `lang`
- `max_elements` (integer)
- `screen`

### `check_locator` (~77 tokens)

Check locator

How many elements an Appium locator matches on a screen (1 = good) and whether it's visible. Accepts Python
(AppiumBy.X, "v"), Java AppiumBy.x("v") and @AndroidFindBy / @iOSXCUITFindBy forms.

Input parameters:

- `locator` (string, required)
- `screen`

### `capture_baseline` (~92 tokens)

Capture locator baselines

While tests pass, record what each locator's element looks like (accessibility id, resource id, text, hint,
class) in .qa-mcp/appium-baselines.json, per platform. heal_locator and heal-ci use these after the app
changes. Run it on each screen your tests use (or on screens saved from passing runs).

Input parameters:

- `locators` (array, required)
- `screen`

### `heal_locator` (~96 tokens)

Heal locator

For a locator that no longer matches (or matches several elements), find the intended element on the screen
and suggest a verified replacement with a confidence score, reasons, the runner-up and alternatives (accessibility
ids preferred). screen: the page source saved when the test failed (see run_tests), or omit for the live device.
Never edits files.

Input parameters:

- `lang`
- `locator` (string, required)
- `screen`

### `accessibility_check` (~44 tokens)

Accessibility check

Tappable elements a screen reader can't name, and duplicate accessibility ids. These hurt users AND make tests
fragile (no stable accessibility id to target).

Input parameters:

- `screen`

### `save_screen` (~54 tokens)

Save screen

Save the live device's current screen (page source) to .qa-mcp/appium-screens/<name>.xml, to inspect, heal or
capture baselines later without a device.

Input parameters:

- `name` (string, required)

### `run_tests` (~57 tokens)

Run tests

Run the project's pytest + Appium suite. Failures caused by a missing element include the locator, the line,
the platform and the screen saved at that moment (pass it to heal_locator).

Input parameters:

- `keyword`
- `targets`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 63
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 62
- 2026-11-16: 76

## Common questions

### What is the k11 Appium QA MCP server?

k11 Appium QA is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/appium-qa. Self-healing Appium locators for Android and iOS apps, healed on the screen each test failed on. This page covers its PyPI package (k11-appium-qa-mcp).

### Is the k11 Appium QA MCP server safe to use?

k11 Appium QA scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 k11 Appium QA MCP server expose?

k11 Appium QA exposes 7 tools: inspect_screen, check_locator, capture_baseline, heal_locator, accessibility_check, and 2 more. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

### Is the k11 Appium QA MCP server still maintained?

k11 Appium QA is still listed as active in the MCP registry. We last reached this channel on 21 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 k11 Appium QA MCP server under?

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

### What did VerifyMCP test on the k11 Appium QA MCP server?

VerifyMCP ran 16 checks on k11 Appium QA, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/k11-appium-qa-mcp/
- Socket report: https://socket.dev/pypi/package/k11-appium-qa-mcp
- Repository: https://github.com/K11-Software-Solutions/k11techlab-appium-qa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp.json
- HTML version of this page: https://verifymcp.io/servers/k11-software-solutions-appium-qa/k11-appium-qa-mcp
