⚠️ Unofficial project. This is a personal project to showcase the viability of connecting AI assistants to Qualys via the Model Context Protocol. It is not affiliated with, endorsed by, or supported by Qualys, Inc.
An MCP server that connects AI assistants to Qualys security data. 7 workflow tools covering vulnerability management, cloud security, containers, compliance, remediation, and more. Pure Python, zero config beyond credentials.
MCP server for Qualys — real-time vulnerability, cloud, endpoint, and compliance data via natural language
Advanced: If you need to override the auto-derived URLs, set QUALYS_BASE_URL and QUALYS_GATEWAY_URL explicitly instead of QUALYS_POD. Explicit URLs take priority.
Requires uv: brew install uv or curl -LsSf https://astral.sh/uv/install.sh | sh
Updating
uvx caches the resolved build, so a plain uvx qualys-mcp keeps running the
version it first downloaded — it does not auto-upgrade when a new release
ships. To move to the latest version, clear the cache and restart Claude Desktop:
uv cache clean qualys-mcp
To pin (and control) the version explicitly, set it in your config args:
pip install -U qualys-mcp only updates a pip-installed copy — it has no effect
on the uvx-launched server.
Alternative
pip install qualys-mcp
qualys-mcp
Self-Signed Certificates
For environments with self-signed certs, add "QUALYS_SSL_VERIFY": "false" to the env block.
Run with Docker (Streamable HTTP)
Prefer a persistent, network-reachable server over the uvx stdio setup above? Run it as a container instead:
docker build -t qualys-mcp:latest .
cp .env.example .env
$EDITOR .env # set your Qualys credentials
docker compose up -d
claude mcp add --transport http qualys http://127.0.0.1:8000/mcp/
See docs/DOCKER.md for the full guide: environment variables, connecting other MCP clients, security notes, and troubleshooting.
Tools
7 workflow tools that intelligently dispatch to 42 internal aggregators across all Qualys modules. Each tool handles routing, concurrent API calls, cross-domain correlation, and response synthesis automatically.
depth — quick (~10s) / standard (~20s) / deep (~45s)
scope — all / vulns / threats / assets / edr / fim
assess_risk
scope — all / cloud / containers / web / certs / assets
tag / asset_group — filter by business group
provider — aws / azure / gcp (cloud scope)
asset_id — single asset deep-dive
check_compliance
framework — PCI / HIPAA / CIS / NIST / SOC2
include_exceptions — include risk acceptances
plan_remediation
scope — all / patches / mitigations / program
severity — critical / high / moderate
cves / qids — check mitigation coverage for specific vulns
security_overview
period — today / week / month
quick — fast snapshot (~2s) vs full briefing
Example Conversations
Daily Operations
"Give me a security overview" → security_overview(quick=True)
"What happened this week?" → security_overview(period="week")
"What should we patch first?" → plan_remediation(scope="patches", severity="critical")
"How's our compliance?" → check_compliance()
Investigation
"Tell me about CVE-2024-3400" → investigate(target="CVE-2024-3400")
"Are we exposed to ransomware?" → investigate(target="ransomware")
"What do we know about Iranian threats?" → investigate(target="iran")
"Investigate this host: 10.0.0.1" → investigate(target="10.0.0.1", scope="edr")
"Are we PCI compliant?" → check_compliance(framework="PCI")
"What's our patch coverage?" → plan_remediation(scope="patches")
"Is there a mitigation for CVE-2024-3400?" → plan_remediation(cves=["CVE-2024-3400"])
"What security gaps do we have?" → plan_remediation(scope="program")
Multi-Step Workflows
"New critical CVE dropped — what do I need to know?"
→ investigate(target="CVE-...") → plan_remediation(cves=["CVE-..."]) → check_compliance()
"Prepare me for the weekly security standup"
→ security_overview(period="week") → assess_risk(scope="all") → plan_remediation(scope="patches")
"PCI audit prep"
→ check_compliance(framework="PCI", include_exceptions=True) → assess_risk(scope="all") → plan_remediation()
Returns prioritized findings and recommended actions
Performance
Tested on an 89,000-asset environment (US2 POD):
Workflow
Time
security_overview(quick=True)
1.7s
assess_risk(scope="cloud")
1.3s
assess_risk(scope="containers")
3.1s
check_compliance()
<1ms (cached)
plan_remediation(scope="patches")
2.6s
investigate(target="CVE-2024-3400")
~33s
assess_risk(scope="all")
4.9s
Cold start: The first query after launching takes 2-10s longer while the bearer token is acquired and caches warm up. A background thread pre-fetches VMDR detections on startup. After the first query, responses are significantly faster. Ask security_overview(quick=True) first to warm caches.
Eval Harness
300 routing test questions + 900 variants + 30 multi-turn conversation workflows for automated evaluation.
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo Qualys?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Qualys precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte Qualys usa?
Qualys roda localmente via stdio.
Quando Qualys foi verificado pela última vez?
Última verificação: 2026-10-27. MCP server for Qualys — real-time vulnerability, cloud, endpoint, and compliance data via natural language