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.

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.

Available components

79 Trust /100

Last scanned (13 hours ago)

Scores higher than 75% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to K11-Software-Solutions/k11techlab-appium-qa-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 659 tokens (~94/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +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.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 76

    First indexed and scored.

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 21 Nov 2026 · Analysed pypi/k11-appium-qa-mcp@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo K11-Software-Solutions/k11techlab-appium-qa-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/K11-Software-Solutions/k11techlab-appium-qa-mcp/.github/workflows/release.yml@refs/tags/v0.1.0
Rekor log index 3933045442
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:8d09b73a2cdeeeab8f81c0177ae4392f03c07486e6fb18441a34b4faf0ea026a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~519 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
accessibility_check ~44

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).

NameTypeReqDescription
screen–––

No output schema declared.

No examples provided.

capture_baseline ~92

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).

NameTypeReqDescription
locatorsarrayyes–
screen–––

No output schema declared.

No examples provided.

check_locator ~77

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.

NameTypeReqDescription
locatorstringyes–
screen–––

No output schema declared.

No examples provided.

heal_locator ~96

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.

NameTypeReqDescription
lang–––
locatorstringyes–
screen–––

No output schema declared.

No examples provided.

inspect_screen ~99

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.

NameTypeReqDescription
interactive_onlyboolean––
lang–––
max_elementsinteger––
screen–––

No output schema declared.

No examples provided.

run_tests ~57

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).

NameTypeReqDescription
keyword–––
targets–––

No output schema declared.

No examples provided.

save_screen ~54

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.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

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.

pypi · k11-appium-qa-mcp

# add to Claude Code
claude mcp add k11-software-solutions-appium-qa -- uvx k11-appium-qa-mcp
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.