Openqa MCP Server

openqa-mcp PyPI v0.6.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Local openQA mcp client

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 40

Each tool and what it can reach — statically extracted from the published source.

  • add_group_commentno sensitive capability
  • add_job_commentno sensitive capability
  • add_parent_group_commentno sensitive capability
  • cancel_jobno sensitive capability
  • cancel_jobsno sensitive capability
  • cancel_scheduled_productno sensitive capability
  • create_bugno sensitive capability
  • delete_jobno sensitive capability
  • delete_job_commentno sensitive capability
  • duplicate_jobno sensitive capability
Show 30 more tools ↓
  • find_jobs_by_settingno sensitive capability
  • get_assetno sensitive capability
  • get_iso_job_statsno sensitive capability
  • get_jobno sensitive capability
  • get_job_commentsno sensitive capability
  • get_job_detailsno sensitive capability
  • get_job_groupno sensitive capability
  • get_job_group_build_resultsno sensitive capability
  • get_job_statusno sensitive capability
  • get_parent_groupno sensitive capability
  • get_scheduled_productno sensitive capability
  • list_assetsno sensitive capability
  • list_bugsno sensitive capability
  • list_group_commentsno sensitive capability
  • list_job_group_jobsno sensitive capability
  • list_job_groupsno sensitive capability
  • list_jobsno sensitive capability
  • list_jobs_overviewno sensitive capability
  • list_machinesno sensitive capability
  • list_parent_group_commentsno sensitive capability
  • list_parent_groupsno sensitive capability
  • list_productsno sensitive capability
  • list_test_suitesno sensitive capability
  • list_workersno sensitive capability
  • restart_jobsno sensitive capability
  • restart_jobs_bulkno sensitive capability
  • searchno sensitive capability
  • set_job_priorityno sensitive capability
  • trigger_isosno sensitive capability
  • update_job_commentno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.6.0 latest A 98/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/openqa-mcp/badge.svg)](https://mcptrustchecker.com/registry/openqa-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/openqa-mcp"><img src="https://mcptrustchecker.com/registry/openqa-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/openqa-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan openqa-mcp --online --registry pypi

Use the free API → How scoring works

More in Security & Testing