Qualys Cli MCP Server
qualys-cli-mcp
PyPI
v0.1.3
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.
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 − 24.1 = 76. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −22 | Hardcoded JSON Web Token in server code MTC-SRC-008 | exfiltration |
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
2. Client adoption risk — 76 − 5 = 71. 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:
| Points | Adoption-risk factor |
|---|---|
| ✓ | capability blast radius (minimal) — client exposure if the model is manipulated |
| −5 | publisher verification (unlocatable) — no provenance and no public repository to inspect |
| ✓ | inspection depth (source) — how much of the target the scan could see |
Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
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 2
high Hardcoded JSON Web Token in server code (tests/test_server_unit.py)MTC-SRC-008
A live-looking JSON Web Token is hardcoded in `tests/test_server_unit.py:193`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
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
low Package has no source repositoryMTC-SUP-011
"qualys-cli-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package qualys-cli-mcp
Tools 18
Each tool and what it can reach — statically extracted from the published source.
ca_agent_listno sensitive capabilitycs_image_vulnsno sensitive capabilitycsam_asset_countno sensitive capabilitycsam_riskiest_assetsno sensitive capabilitypc_posture_listno sensitive capabilitypm_job_listno sensitive capabilitypm_patch_listno sensitive capabilityqualys_clino sensitive capabilityqualys_cli_helpno sensitive capabilityqualys_statusno sensitive capabilitytc_cdr_findingsno sensitive capabilitytc_connector_listno sensitive capabilityvm_host_detectionno sensitive capabilityvm_host_listno sensitive capabilityvm_kb_by_cveno sensitive capabilityvm_kb_by_qidno sensitive capabilityvm_scan_listno sensitive capabilitywas_finding_listno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (18 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.3 latest |
C 71/100 | 2 | 1.8.0 | 2026-07-23 |
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.
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 pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Agent MCP server.