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

AWT (AI Watch Tester)

PYPI · AAT-DEVQA · SCANNED AUG 3

AI-powered E2E testing MCP server. Detects and auto-fixes UI bugs via DevQA Loop and Vision AI.

Available components

−21 this week 12 Trust /100
Trust breakdown (6 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 →

Supply Chain Security19
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects pillow 11.3.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Install-script risk not yet assessed.Unverified
  • 6 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · aat-devqa

# add to Claude Code
claude mcp add ksgisang-awt -- uvx aat-devqa
# add to Codex CLI
codex mcp add ksgisang-awt -- uvx aat-devqa
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ksgisang-awt": {
      "type": "local",
      "command": [
        "uvx",
        "aat-devqa"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ksgisang-awt --command uvx --arg aat-devqa
# ~/.hermes/config.yaml
mcp_servers:
  ksgisang-awt:
    command: "uvx"
    args: ["aat-devqa"]
// mcp.json
{
  "mcpServers": {
    "ksgisang-awt": {
      "command": "uvx",
      "args": [
        "aat-devqa"
      ]
    }
  }
}
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.

  • 3 Aug 26 −9
    • CVE-2026-42309 affects this package: high security
    • CVE-2026-59197 affects this package: high security
    • CVE-2026-40192 affects this package: high security
    • CVE-2026-55380 affects this package: high security
    • CVE-2026-42308 affects this package: high security
    • CVE-2026-54060 affects this package: high security
    • CVE-2026-25990 affects this package: high security
    • CVE-2026-59200 affects this package: high security
    • CVE-2026-55798 affects this package: high security
    • CVE-2026-55379 affects this package: high security
    • CVE-2026-59199 affects this package: high security
    • CVE-2026-54059 affects this package: high security
    • CVE-2026-54058 affects this package: high security
    • CVE-2026-59205 affects this package: high security
    • CVE-2026-59198 affects this package: high security
    • CVE-2026-42311 affects this package: high security
    • CVE-2026-59204 affects this package: high security
    • CVE-2026-42310 affects this package: high security
    • Known CVEs: unverified → fail security
    • Malware scan: pass → unverified security
    • Dependency health: unverified → 0.94 functional
  • 2 Aug 26 +9
    • Provenance: fail → unverified security
    • Known CVEs: fail → unverified security
    • Malware scan: unverified → pass security
    • Maintenance: pass → unverified functional
    • Dependency health: 0.94 → unverified functional
    • License: fail → unverified functional
    • Licence: GNU Affero General Public License v3 functional
  • 1 Aug 26 0
    • CVE-2026-40192 affects this package: high security
    • CVE-2026-59197 affects this package: high security
    • CVE-2026-54060 affects this package: high security
    • CVE-2026-42309 affects this package: high security
    • CVE-2026-42310 affects this package: high security
    • CVE-2026-59204 affects this package: high security
    • CVE-2026-42311 affects this package: high security
    • CVE-2026-59198 affects this package: high security
    • CVE-2026-59205 affects this package: high security
    • CVE-2026-54058 affects this package: high security
    • CVE-2026-54059 affects this package: high security
    • CVE-2026-59199 affects this package: high security
    • CVE-2026-55379 affects this package: high security
    • CVE-2026-55798 affects this package: high security
    • CVE-2026-59200 affects this package: high security
    • CVE-2026-25990 affects this package: high security
    • CVE-2026-42308 affects this package: high security
    • CVE-2026-55380 affects this package: high security
  • 31 Jul 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −22
    • CVE-2026-55380 affects this package: high security
    • CVE-2026-42308 affects this package: high security
    • CVE-2026-25990 affects this package: high security
    • CVE-2026-59200 affects this package: high security
    • CVE-2026-55798 affects this package: high security
    • CVE-2026-55379 affects this package: high security
    • CVE-2026-59199 affects this package: high security
    • CVE-2026-54059 affects this package: high security
    • CVE-2026-54058 affects this package: high security
    • CVE-2026-59205 affects this package: high security
    • CVE-2026-59198 affects this package: high security
    • CVE-2026-42311 affects this package: high security
    • CVE-2026-59204 affects this package: high security
    • CVE-2026-42310 affects this package: high security
    • CVE-2026-42309 affects this package: high security
    • CVE-2026-54060 affects this package: high security
    • CVE-2026-59197 affects this package: high security
    • CVE-2026-40192 affects this package: high security
    • Provenance: unverified → fail security
    • Malware scan: pass → unverified security
    • Known CVEs: partial → fail security
    • Security disclosure: unverified → fail functional
    • License: unverified → fail functional
    • Maintenance: unverified → pass functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: GNU Affero General Public License v3 functional
  • 29 Jul 26 +4
    • Provenance: fail → unverified security
    • Known CVEs: fail → partial security
    • Maintenance: pass → unverified functional
    • License: fail → unverified functional
    • Security disclosure: fail → unverified functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Licence: GNU Affero General Public License v3 functional
  • 28 Jul 26 0
    • CVE-2026-42311 affects this package: high security
    • CVE-2026-59198 affects this package: high security
    • CVE-2026-59205 affects this package: high security
    • CVE-2026-54058 affects this package: high security
    • CVE-2026-54059 affects this package: high security
    • CVE-2026-59199 affects this package: high security
    • CVE-2026-55379 affects this package: high security
    • CVE-2026-55798 affects this package: high security
    • CVE-2026-59200 affects this package: high security
    • CVE-2026-25990 affects this package: high security
    • CVE-2026-42308 affects this package: high security
    • CVE-2026-55380 affects this package: high security
    • CVE-2026-40192 affects this package: high security
    • CVE-2026-59197 affects this package: high security
    • CVE-2026-54060 affects this package: high security
    • CVE-2026-42309 affects this package: high security
    • CVE-2026-42310 affects this package: high security
    • CVE-2026-59204 affects this package: high security
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
  • 27 Jul 26 33

    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 3 Aug 2026 · Analysed pypi/[email protected]

Provenance none

Ecosystem: pypi · Outcome: none

Vulnerabilities 36 findings
ID CVE Severity Vector Fix available
GHSA-45hq-cxwh-f6vc CVE-2026-55379 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4x4j-2g7c-83w6 CVE-2026-55798 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L yes
GHSA-5x94-69rx-g8h2 CVE-2026-54060 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5xmw-vc9v-4wf2 CVE-2026-42309 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-62p4-gmf7-7g93 CVE-2026-54058 high yes
GHSA-6r8x-57c9-28j4 CVE-2026-59199 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8v84-f9pq-wr9x CVE-2026-54059 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9hw9-ch79-4vh6 CVE-2026-59205 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-cfh3-3jmp-rvhc CVE-2026-25990 high yes
GHSA-fj7v-r99m-22gq CVE-2026-59198 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L yes
GHSA-jjj6-mw9f-p565 CVE-2026-59200 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-phj9-mv4w-65pm CVE-2026-55380 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-pwv6-vv43-88gr CVE-2026-42311 high yes
GHSA-r73j-pqj5-w3x7 CVE-2026-42310 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vjc4-5qp5-m44j CVE-2026-59204 high yes
GHSA-whj4-6x5x-4v2j CVE-2026-40192 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-wjx4-4jcj-g98j CVE-2026-42308 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xj96-63gp-2gmr CVE-2026-59197 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H yes
PYSEC-2026-165 CVE-2026-42308 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2249 CVE-2026-25990 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2250 CVE-2026-40192 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2251 CVE-2026-42309 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2252 CVE-2026-42311 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2253 CVE-2026-54059 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2254 CVE-2026-54060 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2255 CVE-2026-55379 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2256 CVE-2026-55380 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2257 CVE-2026-55798 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L yes
PYSEC-2026-2874 CVE-2026-42310 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3451 CVE-2026-59199 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3453 CVE-2026-59205 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3454 CVE-2026-59197 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H yes
PYSEC-2026-3493 CVE-2026-54058 none yes
PYSEC-2026-3494 CVE-2026-59198 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L yes
PYSEC-2026-3495 CVE-2026-59200 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3496 CVE-2026-59204 none yes
Dependencies 45 packages

45 packages in the resolved dependency tree · 6 stale.

MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.