Qualys Cli MCP Server

qualys-cli-mcp PyPI v0.1.4

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.

Model Context Protocol (MCP) server giving any LLM secure, audited access to the Qualys Cloud Platform (VM, PM, WAS, TotalCloud, Container Security, CSAM, and more).

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 99 − adoption risk = 97/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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Hardcoded JSON Web Token in test/example/packaging MTC-SRC-008 exfiltration

2. Client adoption risk — 99 − 2 = 97. 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 1

low Hardcoded JSON Web Token in test/example/packaging (tests/test_server_unit.py)MTC-SRC-008

A hardcoded JSON Web Token (an embedded JSON Web Token (often an example or expired token)) appears in `tests/test_server_unit.py:339`. Verify whether this is a real credential; if so, remove and rotate it.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server tests/test_server_unit.py

Tools 18

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

  • ca_agent_listno sensitive capability
  • cs_image_vulnsno sensitive capability
  • csam_asset_countno sensitive capability
  • csam_riskiest_assetsno sensitive capability
  • pc_posture_listno sensitive capability
  • pm_job_listno sensitive capability
  • pm_patch_listno sensitive capability
  • qualys_clino sensitive capability
  • qualys_cli_helpno sensitive capability
  • qualys_statusno sensitive capability
Show 8 more tools ↓
  • tc_cdr_findingsno sensitive capability
  • tc_connector_listno sensitive capability
  • vm_host_detectionno sensitive capability
  • vm_host_listno sensitive capability
  • vm_kb_by_cveno sensitive capability
  • vm_kb_by_qidno sensitive capability
  • vm_scan_listno sensitive capability
  • was_finding_listno sensitive capability

What this scan could not see

Versions 2

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.1.4 latest A 97/100 1 1.13.0 2026-08-25
v0.1.3 A 97/100 1 1.12.1 2026-07-27

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 · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/qualys-cli-mcp/badge.svg)](https://mcptrustchecker.com/registry/qualys-cli-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/qualys-cli-mcp"><img src="https://mcptrustchecker.com/registry/qualys-cli-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/qualys-cli-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 qualys-cli-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools