Auvik
OCI · GHCR.IO/WYRE-AI/AUVIK-MCP:V1.4.4 · SCANNED SEP 20
MCP server for the Auvik network monitoring API — devices, alerts, statistics, billing.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- 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.Unverified
- Install-script risk not yet assessed.Unverified
- 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.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 25 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2122 tokens (~78/item across 27 items; 27 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
oci · ghcr.io/wyre-ai/auvik-mcp:v1.4.4
claude mcp add wyre-ai-auvik-mcp -- docker run --rm -i ghcr.io/wyre-ai/auvik-mcp:v1.4.4
{
"mcpServers": {
"wyre-ai-auvik-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/auvik-mcp:v1.4.4"
]
}
}
} {
"servers": {
"wyre-ai-auvik-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/auvik-mcp:v1.4.4"
]
}
}
} codex mcp add wyre-ai-auvik-mcp -- docker run --rm -i ghcr.io/wyre-ai/auvik-mcp:v1.4.4
{
"$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
}
}
} mcp_servers:
wyre-ai-auvik-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/auvik-mcp:v1.4.4"] {
"McpServers": {
"wyre-ai-auvik-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/auvik-mcp:v1.4.4"
]
}
}
} {
"mcpServers": {
"wyre-ai-auvik-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/auvik-mcp:v1.4.4"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/auvik-mcp:v1.4.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
auvik_alerts_dismiss ~49
Dismiss/acknowledge an alert
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | string | yes | The Auvik alert ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_alerts_get ~46
Get details about a specific alert
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | string | yes | The Auvik alert ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_alerts_list ~263
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_billing_client_usage ~60
Get client billing usage information
| Name | Type | Req | Description |
|---|---|---|---|
| fromDate | string | yes | Start date (YYYY-MM-DD) |
| tenants | string | – | Comma-separated tenant IDs (optional) |
| thruDate | string | yes | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
auvik_billing_device_usage ~77
Get billing usage information for a specific device
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | The Auvik device ID |
| fromDate | string | yes | Start date (YYYY-MM-DD) |
| tenants | string | – | Comma-separated tenant IDs (optional) |
| thruDate | string | yes | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
auvik_configurations_get ~45
Get a specific device configuration
| Name | Type | Req | Description |
|---|---|---|---|
| configId | string | yes | The Auvik configuration ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_configurations_list ~79
List device configurations managed by Auvik
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_devices_get ~46
Get basic information about a specific device
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | The Auvik device ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_devices_get_details ~47
Get detailed information about a specific device
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | The Auvik device ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_devices_get_lifecycle ~48
Get lifecycle information for a specific device
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | The Auvik device ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_devices_get_warranty ~48
Get warranty information for a specific device
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | yes | The Auvik device ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_devices_list ~131
List network devices managed by Auvik
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_entities_list_audits ~82
List audit logs for Auvik entities
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_entities_list_notes ~80
List notes attached to Auvik entities
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_interfaces_list ~95
List network interfaces discovered by Auvik
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_navigate ~21
Get navigation links to Auvik UI and documentation
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
auvik_networks_get ~46
Get information about a specific network
| Name | Type | Req | Description |
|---|---|---|---|
| networkId | string | yes | The Auvik network ID |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_networks_list ~101
List networks discovered by Auvik
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
auvik_raw_request ~208
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}).
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON request body (POST only, optional) |
| method | string | – | HTTP method (default GET) |
| path | string | yes | 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) |
No output schema declared.
No examples provided.
auvik_statistics_device ~130
Get device statistics and performance metrics
| Name | Type | Req | Description |
|---|---|---|---|
| filter_devices | string | – | Filter by device ID(s) (optional) |
| fromTime | string | yes | Start time (ISO 8601) |
| interval | string | yes | Reporting interval: minute, hour, day, month, or year |
| statId | string | yes | 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) |
No output schema declared.
No examples provided.
auvik_statistics_interface ~127
Get interface statistics and performance metrics
| Name | Type | Req | Description |
|---|---|---|---|
| filter_interfaces | string | – | Filter by interface ID(s) (optional) |
| fromTime | string | yes | Start time (ISO 8601) |
| interval | string | yes | Reporting interval: minute, hour, day, month, or year |
| statId | string | yes | 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) |
No output schema declared.
No examples provided.
auvik_statistics_service ~117
Get service statistics and performance metrics
| Name | Type | Req | Description |
|---|---|---|---|
| filter_services | string | – | Filter by service ID(s) (optional) |
| fromTime | string | yes | Start time (ISO 8601) |
| interval | string | yes | Reporting interval: minute, hour, day, month, or year |
| statId | string | yes | Statistic to fetch (path segment) |
| tenants | string | – | Comma-separated tenant IDs (optional) |
| thruTime | string | – | End time (ISO 8601, optional; defaults to now) |
No output schema declared.
No examples provided.
auvik_statistics_snmp_poller ~72
Get SNMP poller statistics and metrics
| Name | Type | Req | Description |
|---|---|---|---|
| filter_pollers | string | – | Filter by SNMP poller / OID (optional) |
| statId | string | yes | OID statistic to fetch (path segment) |
| tenants | string | – | Comma-separated tenant IDs (optional) |
No output schema declared.
No examples provided.
auvik_status ~19
Check Auvik MCP server status and configuration
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
auvik_tenants_detail ~33
Get detailed information about a specific tenant
| Name | Type | Req | Description |
|---|---|---|---|
| tenantId | string | yes | The Auvik tenant ID |
No output schema declared.
No examples provided.
auvik_tenants_get ~33
Get basic information about a specific tenant
| Name | Type | Req | Description |
|---|---|---|---|
| tenantId | string | yes | The Auvik tenant ID |
No output schema declared.
No examples provided.
auvik_tenants_list ~19
List all accessible Auvik tenants
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.