# Bitdefender GravityZone (oci · ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0)

MCP server for Bitdefender GravityZone's JSON-RPC API.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0`: 38/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-bitdefender-mcp/ghcr-io-wyre-ai-bitdefender-mcp-v1-0-0.md), [page](https://verifymcp.io/servers/wyre-ai-bitdefender-mcp/ghcr-io-wyre-ai-bitdefender-mcp-v1-0-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1435 tokens (~143/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Bitdefender GravityZone MCP server?

Bitdefender GravityZone runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-bitdefender-mcp -- docker run --rm -i ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-bitdefender-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-bitdefender-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-bitdefender-mcp -- docker run --rm -i ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-bitdefender-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-bitdefender-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-bitdefender-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-bitdefender-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 38)

First indexed and scored.

## MCP tools (10)

### `bitdefender_list_endpoints` (~234 tokens)

List managed/unmanaged endpoints (computers, VMs, EC2 instances) - name, FQDN, IP, MAC addresses, AD SID, group, and installed-agent flags. Endpoint IDs from this response are required by bitdefender_get_endpoint. Scope to a group with parentId (from bitdefender_list_custom_groups); omit for the root of the Network Inventory. Returns a paginated envelope: page/pagesCount/perPage/total/items.

Input parameters:

- `filters` (object): Optional filters, structured in sections/subsections (any selected filter within a subsection matches; matches across sections AND). Some filters require a specific GravityZone license to be active,…
- `isManaged` (boolean): True to return only managed endpoints. Omit to return both managed and unmanaged.
- `page` (number): Results page number (1-based). Defaults to 1.
- `parentId` (string): Group ID to scope the listing to. Defaults to Computers and Groups (root).
- `perPage` (number): Items per page (max 100). Defaults to 30.

### `bitdefender_get_endpoint` (~78 tokens)

Get full detail for one managed endpoint: power state, IP, last-seen timestamp, and the installed security agent's engine/product versions, license status, and update/outdated flags. Requires an endpoint ID from bitdefender_list_endpoints.

Input parameters:

- `endpointId` (string, required): Endpoint ID, from bitdefender_list_endpoints.

### `bitdefender_list_custom_groups` (~110 tokens)

List the child groups directly under a group in the Network Inventory tree. Omit parentId to list the top-level 'Computers and Groups' and 'Deleted' groups. Group IDs from this response can be passed as parentId to bitdefender_list_endpoints and bitdefender_list_network_inventory. Returns a plain array (not a paginated envelope), each entry {id, name}.

Input parameters:

- `parentId` (string): Parent group ID. Omit for the top-level groups.

### `bitdefender_list_network_inventory` (~188 tokens)

List Network Inventory items (groups, computers, virtual machines, EC2 instances) under a container, with per-type detail. Broader than bitdefender_list_endpoints, which returns only endpoints - this also returns group nodes and lets you filter by item type. Returns a paginated envelope: page/pagesCount/perPage/total/items.

Input parameters:

- `filters` (object): Optional filters, structured in sections/subsections (any selected filter within a subsection matches; matches across sections AND). Some filters require a specific GravityZone license to be active,…
- `page` (number): Results page number (1-based). Defaults to 1.
- `parentId` (string): Container ID to scope the listing to. Defaults to the root of the Network Inventory.
- `perPage` (number): Items per page (max 100). Defaults to 30.

### `bitdefender_list_scan_tasks` (~165 tokens)

List previously created on-demand scan tasks and their status (1=Pending, 2=In progress, 3=Finished). Read-only - this connector never creates a scan task (createScanTask is excluded; see README's Scope section). Returns a paginated envelope: page/pagesCount/perPage/total/items.

Input parameters:

- `name` (string): Filter by task name. Prefix with '*' to match anywhere in the name; otherwise matches names starting with the keyword.
- `page` (number): Results page number (1-based). Defaults to 1.
- `perPage` (number): Items per page (max 100). Defaults to 30.
- `status` (number): 1=Pending, 2=In progress, 3=Finished.

### `bitdefender_list_policies` (~94 tokens)

List security policies available to the account (id, name, owning company). Policy IDs from this response are required by bitdefender_get_policy. Returns a paginated envelope: page/pagesCount/perPage/total/items.

Input parameters:

- `page` (number): Results page number (1-based). Defaults to 1.
- `perPage` (number): Items per page (max 100). Defaults to 30.

### `bitdefender_get_policy` (~64 tokens)

Get full detail for one security policy: creator, created/last-modified dates, and its complete settings object. Requires a policy ID from bitdefender_list_policies.

Input parameters:

- `policyId` (string, required): Policy ID, from bitdefender_list_policies.

### `bitdefender_list_blocklist_items` (~134 tokens)

List file hashes present in the account's Blocklist - hash, hash algorithm (SHA256/MD5), source (incident/import/manual), source description, and filename where known. Read-only - this connector never adds to or removes from the Blocklist (addToBlocklist/removeFromBlocklist are excluded; see README's Scope section). Returns a paginated envelope: page/pagesCount/perPage/total/items.

Input parameters:

- `page` (number): Results page number (1-based). Defaults to 1.
- `perPage` (number): Items per page (max 100). Defaults to 30.

### `bitdefender_list_reports` (~257 tokens)

List scheduled/instant reports configured on the account - id, name, report type, and run occurrence (hourly/daily/weekly/monthly). Report IDs from this response are required by bitdefender_get_report_download_links. Returns a paginated envelope: page/pagesCount/perPage/total/items.

Input parameters:

- `name` (string): Filter by report name.
- `page` (number): Results page number (1-based). Defaults to 1.
- `perPage` (number): Items per page (max 100). Defaults to 30.
- `type` (number): Filter by report type: 1 Antiphishing Activity, 2 Blocked Applications, 3 Blocked Websites, 5 Data Protection, 6 Device Control Activity, 7 Endpoint Modules Status, 8 Endpoint Protection Status, 9 Fi…

### `bitdefender_get_report_download_links` (~111 tokens)

Check whether a report is ready for download and, if so, get its download URL(s) - readyForDownload, lastInstanceUrl (most recent instance), and allInstancesUrl (scheduled reports only). Both URLs require the same HTTP Basic auth as the API itself (API key as username, empty password) and return a CSV+PDF archive. Requires a report ID from bitdefender_list_reports.

Input parameters:

- `reportId` (string, required): Report ID, from bitdefender_list_reports.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-bitdefender-mcp/ghcr-io-wyre-ai-bitdefender-mcp-v1-0-0#diagnostics

## Score history

- 2026-09-20: 38

## Common questions

### What is the Bitdefender GravityZone MCP server?

Bitdefender GravityZone is an MCP server listed in the public MCP registry as io.github.WYRE-AI/bitdefender-mcp. MCP server for Bitdefender GravityZone's JSON-RPC API. This page covers its container image (ghcr.io/wyre-ai/bitdefender-mcp:v1.0.0).

### Is the Bitdefender GravityZone MCP server safe to use?

Bitdefender GravityZone scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Bitdefender GravityZone MCP server expose?

Bitdefender GravityZone exposes 10 tools: bitdefender_list_endpoints, bitdefender_get_endpoint, bitdefender_list_custom_groups, bitdefender_list_network_inventory, bitdefender_list_scan_tasks, and 5 more. Their descriptions and schemas cost roughly 1,435 tokens of context every time the server is loaded.

### Is the Bitdefender GravityZone MCP server still maintained?

Bitdefender GravityZone is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Bitdefender GravityZone MCP server under?

Bitdefender GravityZone declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- Repository: https://github.com/WYRE-AI/bitdefender-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-bitdefender-mcp/ghcr-io-wyre-ai-bitdefender-mcp-v1-0-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-bitdefender-mcp/ghcr-io-wyre-ai-bitdefender-mcp-v1-0-0.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-bitdefender-mcp/ghcr-io-wyre-ai-bitdefender-mcp-v1-0-0
