# Auvik (oci · ghcr.io/wyre-ai/auvik-mcp:v1.4.4)

MCP server for the Auvik network monitoring API — devices, alerts, statistics, billing.

- Trust score: 50/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/wyre-ai/auvik-mcp:v1.4.4`: 50/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-auvik-mcp/ghcr-io-wyre-ai-auvik-mcp-v1-4-4.md), [page](https://verifymcp.io/servers/wyre-ai-auvik-mcp/ghcr-io-wyre-ai-auvik-mcp-v1-4-4)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/auvik-mcp:v1.4.4`
- 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**: 35/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 25 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2122 tokens (~78/item across 27 items; 27 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 27 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 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: 1 category.** A category scored 0 because we could not verify it: 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 Auvik MCP server?

Auvik runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/auvik-mcp:v1.4.4. 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-auvik-mcp -- docker run --rm -i ghcr.io/wyre-ai/auvik-mcp:v1.4.4
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

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

## 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-19 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (27)

### `auvik_status` (~19 tokens)

Check Auvik MCP server status and configuration

### `auvik_navigate` (~21 tokens)

Get navigation links to Auvik UI and documentation

### `auvik_tenants_list` (~19 tokens)

List all accessible Auvik tenants

### `auvik_tenants_get` (~33 tokens)

Get basic information about a specific tenant

Input parameters:

- `tenantId` (string, required): The Auvik tenant ID

### `auvik_tenants_detail` (~33 tokens)

Get detailed information about a specific tenant

Input parameters:

- `tenantId` (string, required): The Auvik tenant ID

### `auvik_devices_list` (~131 tokens)

List network devices managed by Auvik

Input parameters:

- `filter_deviceType` (string): Filter by device type (optional)
- `filter_modifiedAfter` (string): Filter devices modified after this date (ISO 8601, optional)
- `filter_onlineStatus` (string): Filter by online status (optional)
- `filter_vendorName` (string): Filter by vendor name (optional)
- `page` (number): Page number (optional)
- `pageSize` (number): Number of items per page (1-1000, optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_devices_get` (~46 tokens)

Get basic information about a specific device

Input parameters:

- `deviceId` (string, required): The Auvik device ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_devices_get_details` (~47 tokens)

Get detailed information about a specific device

Input parameters:

- `deviceId` (string, required): The Auvik device ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_devices_get_warranty` (~48 tokens)

Get warranty information for a specific device

Input parameters:

- `deviceId` (string, required): The Auvik device ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_devices_get_lifecycle` (~48 tokens)

Get lifecycle information for a specific device

Input parameters:

- `deviceId` (string, required): The Auvik device ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_networks_list` (~101 tokens)

List networks discovered by Auvik

Input parameters:

- `filter_modifiedAfter` (string): Filter networks modified after this date (ISO 8601, optional)
- `filter_networkType` (string): Filter by network type (optional)
- `page` (number): Page number (optional)
- `pageSize` (number): Number of items per page (1-1000, optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_networks_get` (~46 tokens)

Get information about a specific network

Input parameters:

- `networkId` (string, required): The Auvik network ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_interfaces_list` (~95 tokens)

List network interfaces discovered by Auvik

Input parameters:

- `filter_interfaceType` (string): Filter by interface type (optional)
- `filter_parentDevice` (string): Filter by parent device ID (optional)
- `page` (number): Page number (optional)
- `pageSize` (number): Number of items per page (1-1000, optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_configurations_list` (~79 tokens)

List device configurations managed by Auvik

Input parameters:

- `filter_devices` (string): Filter by device IDs (optional)
- `page` (number): Page number (optional)
- `pageSize` (number): Number of items per page (1-1000, optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_configurations_get` (~45 tokens)

Get a specific device configuration

Input parameters:

- `configId` (string, required): The Auvik configuration ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_entities_list_notes` (~80 tokens)

List notes attached to Auvik entities

Input parameters:

- `filter_entityId` (string): Filter by entity ID (optional)
- `page` (number): Page number (optional)
- `pageSize` (number): Number of items per page (1-1000, optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_entities_list_audits` (~82 tokens)

List audit logs for Auvik entities

Input parameters:

- `filter_entityId` (string): Filter by entity ID (optional)
- `page` (number): Page number (optional)
- `pageSize` (number): Number of items per page (1-1000, optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_alerts_list` (~263 tokens)

List alert history from Auvik monitoring. Scope to a recent window with filter_detectedTimeAfter/Before. Alert history is cursor-paginated: pass pageSize for page size and follow nextPageAfter (returned when more pages exist) via pageAfter. There is no page-number jumping.

Input parameters:

- `filter_detectedTimeAfter` (string): Only alerts detected at/after this time (ISO 8601, optional). Best way to scope to recent alerts.
- `filter_detectedTimeBefore` (string): Only alerts detected at/before this time (ISO 8601, optional)
- `filter_severity` (string): Filter by severity (optional)
- `filter_status` (string): Filter by alert status (optional)
- `pageAfter` (string): Cursor for next page; pass the nextPageAfter value from a previous response (optional)
- `pageSize` (number): Items per page; Auvik caps alert history at ~100. Follow nextPageAfter for full coverage (optional)
- `sort` (string): Best-effort sort passthrough, e.g. "-detectedTime". Honored only if Auvik supports it (optional)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_alerts_get` (~46 tokens)

Get details about a specific alert

Input parameters:

- `alertId` (string, required): The Auvik alert ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_alerts_dismiss` (~49 tokens)

Dismiss/acknowledge an alert

Input parameters:

- `alertId` (string, required): The Auvik alert ID
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_statistics_device` (~130 tokens)

Get device statistics and performance metrics

Input parameters:

- `filter_devices` (string): Filter by device ID(s) (optional)
- `fromTime` (string, required): Start time (ISO 8601)
- `interval` (string, required): Reporting interval: minute, hour, day, month, or year
- `statId` (string, required): Statistic to fetch (path segment), e.g. cpuUtilization, bandwidth, storageUtilization
- `tenants` (string): Comma-separated tenant IDs (optional)
- `thruTime` (string): End time (ISO 8601, optional; defaults to now)

### `auvik_statistics_interface` (~127 tokens)

Get interface statistics and performance metrics

Input parameters:

- `filter_interfaces` (string): Filter by interface ID(s) (optional)
- `fromTime` (string, required): Start time (ISO 8601)
- `interval` (string, required): Reporting interval: minute, hour, day, month, or year
- `statId` (string, required): Statistic to fetch (path segment), e.g. bandwidth, packetLoss, utilization
- `tenants` (string): Comma-separated tenant IDs (optional)
- `thruTime` (string): End time (ISO 8601, optional; defaults to now)

### `auvik_statistics_service` (~117 tokens)

Get service statistics and performance metrics

Input parameters:

- `filter_services` (string): Filter by service ID(s) (optional)
- `fromTime` (string, required): Start time (ISO 8601)
- `interval` (string, required): Reporting interval: minute, hour, day, month, or year
- `statId` (string, required): Statistic to fetch (path segment)
- `tenants` (string): Comma-separated tenant IDs (optional)
- `thruTime` (string): End time (ISO 8601, optional; defaults to now)

### `auvik_statistics_snmp_poller` (~72 tokens)

Get SNMP poller statistics and metrics

Input parameters:

- `filter_pollers` (string): Filter by SNMP poller / OID (optional)
- `statId` (string, required): OID statistic to fetch (path segment)
- `tenants` (string): Comma-separated tenant IDs (optional)

### `auvik_billing_client_usage` (~60 tokens)

Get client billing usage information

Input parameters:

- `fromDate` (string, required): Start date (YYYY-MM-DD)
- `tenants` (string): Comma-separated tenant IDs (optional)
- `thruDate` (string, required): End date (YYYY-MM-DD)

### `auvik_billing_device_usage` (~77 tokens)

Get billing usage information for a specific device

Input parameters:

- `deviceId` (string, required): The Auvik device ID
- `fromDate` (string, required): Start date (YYYY-MM-DD)
- `tenants` (string): Comma-separated tenant IDs (optional)
- `thruDate` (string, required): End date (YYYY-MM-DD)

### `auvik_raw_request` (~208 tokens)

Make a raw request to any Auvik API endpoint using the configured credentials. Returns the unmodified JSON:API response. Use this for endpoints or query params the typed tools do not expose. Methods: GET (default) or POST. `path` is relative to the Auvik API base (e.g. "/alert/history/info"). `query` keys are exact Auvik param names including brackets (e.g. {"filter[detectedTimeAfter]":"2026-06-01","page[first]":100}).

Input parameters:

- `body` (object): JSON request body (POST only, optional)
- `method` (string): HTTP method (default GET)
- `path` (string, required): API path relative to the Auvik base URL, e.g. "/alert/history/info"
- `query` (object): Query parameters as exact Auvik names, e.g. {"filter[detectedTimeAfter]":"2026-06-01"} (optional)

## Diagnostics

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

## Score history

- 2026-09-20: 50
- 2026-09-19: 50
- 2026-09-18: 49
- 2026-09-17: 49
- 2026-09-16: 48
- 2026-09-15: 48
- 2026-09-14: 47
- 2026-09-13: 47
- 2026-09-12: 46
- 2026-09-11: 46
- 2026-09-10: 46
- 2026-09-09: 45
- 2026-09-08: 45
- 2026-09-07: 44
- 2026-09-06: 44
- 2026-09-05: 43
- 2026-09-04: 43
- 2026-09-03: 42
- 2026-09-02: 39
- 2026-09-01: 39
- 2026-08-31: 39
- 2026-08-30: 39
- 2026-08-29: 39
- 2026-08-28: 39
- 2026-08-27: 39
- 2026-08-26: 39

## Common questions

### What is the Auvik MCP server?

Auvik is an MCP server listed in the public MCP registry as io.github.WYRE-AI/auvik-mcp. MCP server for the Auvik network monitoring API, devices, alerts, statistics, billing. This page covers its container image (ghcr.io/wyre-ai/auvik-mcp:v1.4.4).

### Is the Auvik MCP server safe to use?

Auvik scores 50 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 Auvik MCP server expose?

Auvik exposes 27 tools: auvik_status, auvik_navigate, auvik_tenants_list, auvik_tenants_get, auvik_tenants_detail, and 22 more. Their descriptions and schemas cost roughly 2,122 tokens of context every time the server is loaded.

### Is the Auvik MCP server still maintained?

Auvik 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 Auvik MCP server under?

Auvik 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/auvik-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-auvik-mcp/ghcr-io-wyre-ai-auvik-mcp-v1-4-4.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-auvik-mcp/ghcr-io-wyre-ai-auvik-mcp-v1-4-4.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-auvik-mcp/ghcr-io-wyre-ai-auvik-mcp-v1-4-4