--- title: "Qualys VMDR MCP server for AI agents - actionlake" description: "Give Claude 115 Qualys VMDR actions through one MCP server: assets, host assets. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/qualys-vmdr updated: 2026-10-22 --- Connectors · Identity & security # Qualys VMDR MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Qualys VMDR and the rest of your systems. It gives your agent 115 Qualys VMDR actions (40 reads, 51 writes and 24 that wait for a confirmation) and holds the Qualys VMDR credential itself, so the agent never does. It paces Qualys VMDR's limits and records every call. [Connect Qualys VMDR free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "qualys_vmdr.host_assets.search", intent: "check which Qualys VMDR account is connected" } # Search host assets · read · 1 upstream call ``` - 115 actions in one signed file - 40 read look, never change - 51 write create and update - 24 wait for a yes destructive, confirmed first Set up ## Connect Qualys VMDR in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Qualys VMDR. Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `username` Qualys user name with API access - `password` That user's password - `host` Where your Qualys VMDR lives: your host ``` account { op: "connections.requirements", service: "qualys_vmdr" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "qualys_vmdr.host_assets.search" } # search host assets · read · 1 upstream call check { action: "qualys_vmdr.host_assets.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Qualys VMDR at a glance **Sign-in** Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `username` `password` **Setup fields** `host` **Limits we pace to** 300 calls an hour, per connection **API covered** Qualys Asset Management & Tagging API v2/v3 (QPS) and Cloud Agent API (QPS 1.0), at your Qualys VMDR instance's API base URL, which you enter when connecting **Built from** Qualys VMDR's documentation, read 22 October 2026[docs.qualys.com](https://docs.qualys.com/en/am/api/) [docs.qualys.com](https://docs.qualys.com/en/ca/api/) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 40 of 40 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 1, so ask can line Qualys VMDR up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Qualys VMDR. 115 actions in 19 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **40** read look, never change - **51** write create and update - **24** destructive wait for a confirmation 1. ### Assets 13 3 read · 6 write · 4 destructive Count assets · Search assets · Activate modules on an asset · Activate modules on assets by filter 2. ### Host assets 12 3 read · 5 write · 4 destructive Search host assets · Get a host asset · Create a host asset · Update a host asset 3. ### Aws connectors V3 10 3 read · 5 write · 2 destructive Create an AWS connector 3.0 · Search AWS connector 3.0s · Download the AWS CloudFormation template (JSON) · Get an AWS connector 3.0 4. ### Tags 10 3 read · 5 write · 2 destructive Count tags · Create a tag · Search tags · Re-evaluate a tag 5. ### Asset data connectors 9 3 read · 4 write · 2 destructive Count asset data connectors · Search asset data connectors · Get an asset data connector · Run an asset data connector 6. ### Azure connectors V3 9 2 read · 5 write · 2 destructive Create an Azure connector 3.0 · Search Azure connector 3.0s · Get an Azure connector 3.0 · Run an Azure connector 3.0 7. ### GCP connectors V3 9 2 read · 5 write · 2 destructive Create a GCP connector 3.0 · Search GCP connector 3.0s · Get a GCP connector 3.0 · Run a GCP connector 3.0 8. ### Aws connectors 8 3 read · 3 write · 2 destructive Count AWS asset data connector (v2)s · Create an AWS asset data connector (v2) · Search AWS asset data connector (v2)s · Get an AWS asset data connector (v2) **11 more areas · 35 actions** - Activation keys **7** - Azure connectors **7** - Agent configs **5** - Global scan configurations **3** - Host instance vulns **3** - Users **3** - Agent scans **2** - Aws base accounts V3 **2** - Agent binaries **1** - Connector errors V3 **1** - Portal **1** Top actions ## The Qualys VMDR API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 8 of Qualys VMDR's 9 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `qualys_vmdr.host_assets.search` Search host assets | Search host assets matching QPS filter criteria (one page; see preferences). | read | `device.endpoint.search` 8 connectors | | `qualys_vmdr.host_assets.get` Get a host asset | Return one host asset by id. | read | `device.endpoint.get` 57 connectors | | `qualys_vmdr.host_assets.create` Create a host asset | Create a host asset. | write | `device.endpoint.create` 12 connectors | | `qualys_vmdr.host_assets.delete` Delete a host asset | Delete one host asset by id. | destructive | `device.endpoint.delete` 35 connectors | | `qualys_vmdr.host_instance_vulns.get` Get a host instance vulnerability | Return one host instance vulnerability by id. | read | `security.vulnerability.get` 11 connectors | | `qualys_vmdr.host_instance_vulns.search` Search host instance vulnerabilitys | Search host instance vulnerabilitys matching QPS filter criteria (one page; see preferences). | read | `security.vulnerability.search` 4 connectors | | `qualys_vmdr.tags.count` Count tags | Count tags matching QPS filter criteria. | read | this connector | | `qualys_vmdr.tags.create` Create a tag | Create a tag. | write | this connector | | `qualys_vmdr.users.count` Count user (with tags)s | Count user (with tags)s matching QPS filter criteria. | read | this connector | | `qualys_vmdr.assets.count` Count assets | Count assets matching QPS filter criteria. | read | this connector | | `qualys_vmdr.users.search` Search user (with tags)s | Search user (with tags)s matching QPS filter criteria (one page; see preferences). | read | this connector | | `qualys_vmdr.agent_scans.launch` Launch an on-demand agent scan on one asset | Launch an on-demand Cloud Agent scan on one agent asset. | write | this connector | Try it ## Prompts to paste into Claude. Each one names the Qualys VMDR actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Qualys VMDR devices have not checked in for a week? calls `qualys_vmdr.host_assets.search` 2. Write write Create a host asset in Qualys VMDR. Show me exactly what you will send before you save it. calls `qualys_vmdr.host_assets.create` Governance for Qualys VMDR ## Destructive actions wait for a yes. 24 Qualys VMDR actions are destructive. These are all of them: - Delete a host asset `qualys_vmdr.host_assets.delete` - Delete a tag `qualys_vmdr.tags.delete` - Delete an asset `qualys_vmdr.assets.delete` - Uninstall the agent on an asset `qualys_vmdr.assets.uninstall` - Delete tags by filter `qualys_vmdr.tags.delete_many` - Delete assets by filter `qualys_vmdr.assets.delete_many` - Delete a Cloud Agent configuration profile `qualys_vmdr.agent_configs.delete` - Uninstall the agent on assets by filter `qualys_vmdr.assets.uninstall_many` - Delete an AWS asset data connector (v2) `qualys_vmdr.aws_connectors.delete` - Uninstall the agent on a host asset `qualys_vmdr.host_assets.uninstall` - Delete a Cloud Agent activation key `qualys_vmdr.activation_keys.delete` - Delete an Azure asset data connector (v2) `qualys_vmdr.azure_connectors.delete` - Delete host assets by filter `qualys_vmdr.host_assets.delete_many` - Delete an AWS connector 3.0 `qualys_vmdr.aws_connectors_v3.delete` - Delete a GCP connector 3.0 `qualys_vmdr.gcp_connectors_v3.delete` - Delete AWS asset data connector (v2)s by filter `qualys_vmdr.aws_connectors.delete_many` - Delete an Azure connector 3.0 `qualys_vmdr.azure_connectors_v3.delete` - Uninstall the agent on host assets by filter `qualys_vmdr.host_assets.uninstall_many` - Delete an asset data connector `qualys_vmdr.asset_data_connectors.delete` - Delete Azure asset data connector (v2)s by filter `qualys_vmdr.azure_connectors.delete_many` - Delete AWS connector 3.0s by filter `qualys_vmdr.aws_connectors_v3.delete_many` - Delete GCP connector 3.0s by filter `qualys_vmdr.gcp_connectors_v3.delete_many` - Delete Azure connector 3.0s by filter `qualys_vmdr.azure_connectors_v3.delete_many` - Delete asset data connectors by filter `qualys_vmdr.asset_data_connectors.delete_many` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do qualys_vmdr.host_assets.delete confirm_policy: **human** Delete a host asset? **intent:** the user asked me to delete a host asset run suspended · waiting for a named person · key _qualys-vmdr-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "qualys-vmdr-agent", allowed_actions: ["qualys_vmdr.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "qualys_vmdr.host_assets.delete", approver: "lead@example.com" }, { match: "qualys_vmdr.tags.delete", approver: "lead@example.com" }, { match: "qualys_vmdr.assets.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Qualys VMDR only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Qualys VMDR costs on actionlake. Every Qualys VMDR action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Qualys VMDR refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 115 Qualys VMDR actions - 115 actions page each page of a long list is one call - 40 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Qualys VMDR action. 115 actions by area: the id your agent calls, what it does, and its effect. **Assets 13** - `qualys_vmdr.assets.activate` Activate modules on an asset write - `qualys_vmdr.assets.activate_many` Activate modules on assets by filter write - `qualys_vmdr.assets.count` Count assets read - `qualys_vmdr.assets.deactivate` Deactivate agent modules on an asset write - `qualys_vmdr.assets.deactivate_many` Deactivate agent modules on assets by filter write - `qualys_vmdr.assets.delete` Delete an asset destructive - `qualys_vmdr.assets.delete_many` Delete assets by filter destructive - `qualys_vmdr.assets.get` Get an asset read - `qualys_vmdr.assets.search` Search assets read - `qualys_vmdr.assets.uninstall` Uninstall the agent on an asset destructive - `qualys_vmdr.assets.uninstall_many` Uninstall the agent on assets by filter destructive - `qualys_vmdr.assets.update` Update an asset write - `qualys_vmdr.assets.update_many` Update assets by filter write **Host assets 12** - `qualys_vmdr.host_assets.activate` Activate modules on a host asset write - `qualys_vmdr.host_assets.activate_many` Activate modules on host assets by filter write - `qualys_vmdr.host_assets.count` Count host assets read - `qualys_vmdr.host_assets.create` Create a host asset write - `qualys_vmdr.host_assets.delete` Delete a host asset destructive - `qualys_vmdr.host_assets.delete_many` Delete host assets by filter destructive - `qualys_vmdr.host_assets.get` Get a host asset read - `qualys_vmdr.host_assets.search` Search host assets read - `qualys_vmdr.host_assets.uninstall` Uninstall the agent on a host asset destructive - `qualys_vmdr.host_assets.uninstall_many` Uninstall the agent on host assets by filter destructive - `qualys_vmdr.host_assets.update` Update a host asset write - `qualys_vmdr.host_assets.update_many` Update host assets by filter write **Aws connectors V3 10** - `qualys_vmdr.aws_connectors_v3.cloudformation_template` Download the AWS CloudFormation template (JSON) read - `qualys_vmdr.aws_connectors_v3.create` Create an AWS connector 3.0 write - `qualys_vmdr.aws_connectors_v3.delete` Delete an AWS connector 3.0 destructive - `qualys_vmdr.aws_connectors_v3.delete_many` Delete AWS connector 3.0s by filter destructive - `qualys_vmdr.aws_connectors_v3.get` Get an AWS connector 3.0 read - `qualys_vmdr.aws_connectors_v3.run` Run an AWS connector 3.0 write - `qualys_vmdr.aws_connectors_v3.run_many` Run AWS connector 3.0s by filter write - `qualys_vmdr.aws_connectors_v3.search` Search AWS connector 3.0s read - `qualys_vmdr.aws_connectors_v3.update` Update an AWS connector 3.0 write - `qualys_vmdr.aws_connectors_v3.update_many` Update AWS connector 3.0s by filter write **Tags 10** - `qualys_vmdr.tags.count` Count tags read - `qualys_vmdr.tags.create` Create a tag write - `qualys_vmdr.tags.delete` Delete a tag destructive - `qualys_vmdr.tags.delete_many` Delete tags by filter destructive - `qualys_vmdr.tags.evaluate` Re-evaluate a tag write - `qualys_vmdr.tags.evaluate_many` Re-evaluate tags by filter write - `qualys_vmdr.tags.get` Get a tag read - `qualys_vmdr.tags.search` Search tags read - `qualys_vmdr.tags.update` Update a tag write - `qualys_vmdr.tags.update_many` Update tags by filter write **Asset data connectors 9** - `qualys_vmdr.asset_data_connectors.count` Count asset data connectors read - `qualys_vmdr.asset_data_connectors.delete` Delete an asset data connector destructive - `qualys_vmdr.asset_data_connectors.delete_many` Delete asset data connectors by filter destructive - `qualys_vmdr.asset_data_connectors.get` Get an asset data connector read - `qualys_vmdr.asset_data_connectors.run` Run an asset data connector write - `qualys_vmdr.asset_data_connectors.run_many` Run asset data connectors by filter write - `qualys_vmdr.asset_data_connectors.search` Search asset data connectors read - `qualys_vmdr.asset_data_connectors.update` Update an asset data connector write - `qualys_vmdr.asset_data_connectors.update_many` Update asset data connectors by filter write **Azure connectors V3 9** - `qualys_vmdr.azure_connectors_v3.create` Create an Azure connector 3.0 write - `qualys_vmdr.azure_connectors_v3.delete` Delete an Azure connector 3.0 destructive - `qualys_vmdr.azure_connectors_v3.delete_many` Delete Azure connector 3.0s by filter destructive - `qualys_vmdr.azure_connectors_v3.get` Get an Azure connector 3.0 read - `qualys_vmdr.azure_connectors_v3.run` Run an Azure connector 3.0 write - `qualys_vmdr.azure_connectors_v3.run_many` Run Azure connector 3.0s by filter write - `qualys_vmdr.azure_connectors_v3.search` Search Azure connector 3.0s read - `qualys_vmdr.azure_connectors_v3.update` Update an Azure connector 3.0 write - `qualys_vmdr.azure_connectors_v3.update_many` Update Azure connector 3.0s by filter write **GCP connectors V3 9** - `qualys_vmdr.gcp_connectors_v3.create` Create a GCP connector 3.0 write - `qualys_vmdr.gcp_connectors_v3.delete` Delete a GCP connector 3.0 destructive - `qualys_vmdr.gcp_connectors_v3.delete_many` Delete GCP connector 3.0s by filter destructive - `qualys_vmdr.gcp_connectors_v3.get` Get a GCP connector 3.0 read - `qualys_vmdr.gcp_connectors_v3.run` Run a GCP connector 3.0 write - `qualys_vmdr.gcp_connectors_v3.run_many` Run GCP connector 3.0s by filter write - `qualys_vmdr.gcp_connectors_v3.search` Search GCP connector 3.0s read - `qualys_vmdr.gcp_connectors_v3.update` Update a GCP connector 3.0 write - `qualys_vmdr.gcp_connectors_v3.update_many` Update GCP connector 3.0s by filter write **Aws connectors 8** - `qualys_vmdr.aws_connectors.count` Count AWS asset data connector (v2)s read - `qualys_vmdr.aws_connectors.create` Create an AWS asset data connector (v2) write - `qualys_vmdr.aws_connectors.delete` Delete an AWS asset data connector (v2) destructive - `qualys_vmdr.aws_connectors.delete_many` Delete AWS asset data connector (v2)s by filter destructive - `qualys_vmdr.aws_connectors.get` Get an AWS asset data connector (v2) read - `qualys_vmdr.aws_connectors.search` Search AWS asset data connector (v2)s read - `qualys_vmdr.aws_connectors.update` Update an AWS asset data connector (v2) write - `qualys_vmdr.aws_connectors.update_many` Update AWS asset data connector (v2)s by filter write **Activation keys 7** - `qualys_vmdr.activation_keys.change` Change the activation key of agents write - `qualys_vmdr.activation_keys.create` Create a Cloud Agent activation key write - `qualys_vmdr.activation_keys.delete` Delete a Cloud Agent activation key destructive - `qualys_vmdr.activation_keys.get` Get a Cloud Agent activation key read - `qualys_vmdr.activation_keys.search` Search Cloud Agent activation keys read - `qualys_vmdr.activation_keys.update` Update a Cloud Agent activation key write - `qualys_vmdr.activation_keys.update_many` Update Cloud Agent activation keys by filter write **Azure connectors 7** - `qualys_vmdr.azure_connectors.create` Create an Azure asset data connector (v2) write - `qualys_vmdr.azure_connectors.delete` Delete an Azure asset data connector (v2) destructive - `qualys_vmdr.azure_connectors.delete_many` Delete Azure asset data connector (v2)s by filter destructive - `qualys_vmdr.azure_connectors.get` Get an Azure asset data connector (v2) read - `qualys_vmdr.azure_connectors.search` Search Azure asset data connector (v2)s read - `qualys_vmdr.azure_connectors.update` Update an Azure asset data connector (v2) write - `qualys_vmdr.azure_connectors.update_many` Update Azure asset data connector (v2)s by filter write **Agent configs 5** - `qualys_vmdr.agent_configs.create` Create a Cloud Agent configuration profile write - `qualys_vmdr.agent_configs.delete` Delete a Cloud Agent configuration profile destructive - `qualys_vmdr.agent_configs.get` Get a Cloud Agent configuration profile read - `qualys_vmdr.agent_configs.search` Search Cloud Agent configuration profiles read - `qualys_vmdr.agent_configs.update_many` Update Cloud Agent configuration profiles by filter write **Global scan configurations 3** - `qualys_vmdr.global_scan_configurations.create` Create a global scan configuration write - `qualys_vmdr.global_scan_configurations.search` Search global scan configurations read - `qualys_vmdr.global_scan_configurations.update_many` Update global scan configurations by filter write **Host instance vulns 3** - `qualys_vmdr.host_instance_vulns.count` Count host instance vulnerabilitys read - `qualys_vmdr.host_instance_vulns.get` Get a host instance vulnerability read - `qualys_vmdr.host_instance_vulns.search` Search host instance vulnerabilitys read **Users 3** - `qualys_vmdr.users.count` Count user (with tags)s read - `qualys_vmdr.users.get` Get a user (with tags) read - `qualys_vmdr.users.search` Search user (with tags)s read **Agent scans 2** - `qualys_vmdr.agent_scans.launch` Launch an on-demand agent scan on one asset write - `qualys_vmdr.agent_scans.launch_many` Launch an on-demand agent scan on assets by filter write **Aws base accounts V3 2** - `qualys_vmdr.aws_base_accounts_v3.get` Get an AWS base account read - `qualys_vmdr.aws_base_accounts_v3.search` Search AWS base accounts read **Agent binaries 1** - `qualys_vmdr.agent_binaries.info` Get Cloud Agent binary information read **Connector errors V3 1** - `qualys_vmdr.connector_errors_v3.search` Search connector errors read **Portal 1** - `qualys_vmdr.portal.version` Get the Qualys portal and API version read Questions ## The Qualys VMDR MCP server, answered. **Is there a Qualys VMDR MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 115 Qualys VMDR actions across assets, host assets, aws connectors V3 and tags, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Qualys VMDR. **What do I need to connect Qualys VMDR?** Qualys user name with API access and That user's password. Plus your host. The free call account { op: "connections.requirements", service: "qualys_vmdr" } lists exactly what to paste. **Can an AI agent delete or change things in Qualys VMDR?** Only if its key allows it, and only with an explicit confirmation. 24 Qualys VMDR actions are destructive, including delete a host asset, delete a tag and delete an asset. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Qualys VMDR API limit?** actionlake paces every call to the limits in the Qualys VMDR service file: 300 calls an hour per connection. Repeated reads are answered from cache (40 Qualys VMDR actions can be), which never reaches Qualys VMDR. **What does a Qualys VMDR action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (115 Qualys VMDR actions page). Cache hits, searches, dry runs and calls Qualys VMDR refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Qualys VMDR API does it cover?** The Qualys Asset Management & Tagging API v2/v3 (QPS) and Cloud Agent API (QPS 1.0) at your Qualys VMDR instance's API base URL, which you enter when connecting. It is built from Qualys VMDR's documentation as read on 22 October 2026. 115 actions in 19 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Qualys VMDR data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Qualys VMDR credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Qualys VMDR Shares the most action names with - [Microsoft Defender for Endpoint 3](https://actionlake.com/connectors/microsoft-defender-for-endpoint) - [Trend Vision One 3](https://actionlake.com/connectors/trend-vision-one) - [LimaCharlie 2](https://actionlake.com/connectors/limacharlie) - [VMware Carbon Black Cloud 2](https://actionlake.com/connectors/vmware-carbon-black-cloud) - [ProjectDiscovery Cloud 2](https://actionlake.com/connectors/projectdiscovery-cloud) - [Microsoft Intune 1](https://actionlake.com/connectors/microsoft-intune) Joins with, on shared entities - [NinjaOne 1](https://actionlake.com/connectors/ninjaone) - [TP-Link Omada Open API 1](https://actionlake.com/connectors/tp-link-omada-open-api) - [Commvault Cloud 1](https://actionlake.com/connectors/commvault-cloud) - [HPE Aruba Networking Central 1](https://actionlake.com/connectors/hpe-aruba-networking-central) - [Apple App Store Connect 1](https://actionlake.com/connectors/apple-app-store-connect) - [Jamf Pro 1](https://actionlake.com/connectors/jamf-pro) Browse - [All Identity & security connectors](https://actionlake.com/connectors/category/identity-and-security) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Qualys VMDR; the name is the vendor's own. Counts are from the Qualys VMDR service file, version 1.0.0. ## Give your agent Qualys VMDR today. [Connect Qualys VMDR free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/qualys-vmdr More: https://actionlake.com/llms.txt