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 Selenium QA

PYPI · K11-SELENIUM-QA-MCP

Selenium tests from user stories (Python or Java) and self-healing locators with an audit trail.

+4 this week 68 Trust /100

Last scanned (18 hours ago)

Scores higher than 61% 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 Security50
  • Malware scan not yet available for this package.Unverified
  • 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
  • 3 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
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-selenium-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 Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 677 tokens (~84/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 15% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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 (15)

  • 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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

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 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +2
    • Stability: unverified → 0.10 ▲ functional
    • Package version: 0.2.1 → 0.2.2 functional
  • 13 Nov 26 64

    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-selenium-qa-mcp@0.2.2

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-selenium-qa-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/K11-Software-Solutions/k11techlab-selenium-qa-mcp/.github/workflows/release.yml@refs/tags/v0.2.2
Rekor log index 3933576735
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:4868e206a5395e4ae39ea778608ea15a59a0879cb7d729ee54371e0cff968edd

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 39 packages
Packages resolved 39
Stale 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~589 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
capture_baseline ~69

While tests pass, fingerprint the element each locator matches (.qa-mcp/baselines.json) so healing can find it later.

NameTypeReqDescription
locatorsarrayyes–
session––Optional: reach a page behind a login or several steps into a flow
urlstringyes–

No output schema declared.

No examples provided.

check_locator ~61

Count what a Selenium locator matches on a page (1 = good) and whether it is visible.

NameTypeReqDescription
locatorstringyes–
session––Optional: reach a page behind a login or several steps into a flow
urlstringyes–

No output schema declared.

No examples provided.

explore_page ~72

Open a URL and list elements with Selenium locators verified to match exactly one element, most stable first.

NameTypeReqDescription
max_elementsinteger––
only_interactiveboolean––
session––Optional: reach a page behind a login or several steps into a flow
urlstringyes–

No output schema declared.

No examples provided.

heal_locator ~73

Find the element a broken Selenium locator meant after a UI change and suggest a verified replacement, with confidence, reasons and the runner-up candidates. Never edits files.

NameTypeReqDescription
locatorstringyes–
session––Optional: reach a page behind a login or several steps into a flow
urlstringyes–

No output schema declared.

No examples provided.

parse_user_story ~74

Turn a user story, Gherkin scenarios or acceptance criteria into scenarios and a test skeleton: pytest for Python projects, JUnit 5 or TestNG for Java projects (package/class_name apply to Java).

NameTypeReqDescription
class_name–––
package–––
storystringyes–
url–––

No output schema declared.

No examples provided.

run_tests ~83

Run the project's tests. Python: pytest (target = file or node id; keyword = -k). Java: Maven or Gradle (target = Class, pkg.Class or Class#method). Failing tests include the exact Selenium locator they were waiting for and where it is used.

NameTypeReqDescription
keyword–––
target–––
timeout_sinteger––

No output schema declared.

No examples provided.

save_login_state ~75

Log in once with steps and save cookies + localStorage to .qa-mcp/auth/<name>.json for other tools. Use ${ENV:NAME} for credentials; values are never echoed.

NameTypeReqDescription
namestring––
stepsarrayyes–
success_locator–––
urlstringyes–

No output schema declared.

No examples provided.

write_test ~82

Write a test file. Python: into tests/ as test_*.py, *_test.py or conftest.py. Java: into src/test/java/ as a .java file (tests and Page Objects). Refuses other paths; won't overwrite unless asked.

NameTypeReqDescription
codestringyes–
overwriteboolean––
pathstringyes–

No output schema declared.

No examples provided.

Install

How do I install the k11 Selenium QA MCP server?

k11 Selenium QA runs locally as a PyPI package, launched with uvx k11-selenium-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-selenium-qa-mcp

# add to Claude Code
claude mcp add k11-software-solutions-selenium-qa -- uvx k11-selenium-qa-mcp
Common questions

What is the k11 Selenium QA MCP server?

k11 Selenium QA is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/selenium-qa. Selenium tests from user stories (Python or Java) and self-healing locators with an audit trail. This page covers its PyPI package (k11-selenium-qa-mcp).

Is the k11 Selenium QA MCP server safe to use?

k11 Selenium QA scores 68 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 Selenium QA MCP server expose?

k11 Selenium QA exposes 8 tools: explore_page, check_locator, save_login_state, parse_user_story, write_test, and 3 more. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.

Is the k11 Selenium QA MCP server still maintained?

k11 Selenium 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 Selenium QA MCP server under?

k11 Selenium 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 Selenium QA MCP server?

VerifyMCP ran 15 checks on k11 Selenium QA, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about k11 Selenium QA: Malware scan. 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.