PRTG
OCI · GHCR.IO/WYRE-AI/PRTG-MCP:V1.0.0 · SCANNED SEP 20
MCP server for Paessler PRTG's REST API v2 - network/infrastructure monitoring for MSPs.
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 & Transparency32
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1582 tokens (~105/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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: 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.
How do I install the PRTG MCP server?
PRTG runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/prtg-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.
oci · ghcr.io/wyre-ai/prtg-mcp:v1.0.0
claude mcp add wyre-ai-prtg-mcp -- docker run --rm -i ghcr.io/wyre-ai/prtg-mcp:v1.0.0
{
"mcpServers": {
"wyre-ai-prtg-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/prtg-mcp:v1.0.0"
]
}
}
} {
"servers": {
"wyre-ai-prtg-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/prtg-mcp:v1.0.0"
]
}
}
} codex mcp add wyre-ai-prtg-mcp -- docker run --rm -i ghcr.io/wyre-ai/prtg-mcp:v1.0.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wyre-ai-prtg-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/prtg-mcp:v1.0.0"
],
"enabled": true
}
}
} mcp_servers:
wyre-ai-prtg-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/prtg-mcp:v1.0.0"] {
"McpServers": {
"wyre-ai-prtg-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/prtg-mcp:v1.0.0"
]
}
}
} {
"mcpServers": {
"wyre-ai-prtg-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/prtg-mcp:v1.0.0"
]
}
}
} 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.
- 20 Sept 26 39
First indexed and scored.
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/prtg-mcp:v1.0.0
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 →
prtg_get_channel ~95
Get the metrics and settings (units, limits, current value) of a single channel on a sensor by ID. Channel IDs appear in prtg_get_sensor_data and prtg_get_sensor results.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Channel ID. |
| include | string | – | Comma-separated list of additional settings sections to include, e.g. 'all_sections' or 'path'. Omit for just the most relevant fields. |
No output schema declared.
No examples provided.
prtg_get_device ~74
Get the metrics and settings of a single device by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Device ID (from prtg_list_devices). |
| include | string | – | Comma-separated list of additional settings sections to include, e.g. 'all_sections' or 'path'. Omit for just the most relevant fields. |
No output schema declared.
No examples provided.
prtg_get_group ~74
Get the metrics and settings of a single group by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Group ID (from prtg_list_groups). |
| include | string | – | Comma-separated list of additional settings sections to include, e.g. 'all_sections' or 'path'. Omit for just the most relevant fields. |
No output schema declared.
No examples provided.
prtg_get_object_sensor_summary ~59
Get a sensor-state summary scoped to one probe, group, or device.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Probe, group, or device ID (from prtg_list_probes, prtg_list_groups, or prtg_list_devices). |
No output schema declared.
No examples provided.
prtg_get_probe ~75
Get the metrics and settings of a single probe by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Probe ID (from prtg_list_probes). |
| include | string | – | Comma-separated list of additional settings sections to include, e.g. 'all_sections' or 'path'. Omit for just the most relevant fields. |
No output schema declared.
No examples provided.
prtg_get_probe_network_info ~44
Get network information (the probe host's own connectivity details) for a probe.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Probe ID (from prtg_list_probes). |
No output schema declared.
No examples provided.
prtg_get_sensor ~82
Get the metrics and settings of a single sensor by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Sensor ID (from prtg_list_sensors or prtg_list_alarms). |
| include | string | – | Comma-separated list of additional settings sections to include, e.g. 'all_sections' or 'path'. Omit for just the most relevant fields. |
No output schema declared.
No examples provided.
prtg_get_sensor_data ~157
Get channel measurement history (the actual monitoring/performance data) for a sensor.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. |
| id | string | yes | Sensor ID (from prtg_list_sensors or prtg_list_alarms). |
| limit | number | – | Number of objects to return (max 3000). Defaults to 100. |
| offset | number | – | Zero-based offset into the result set. Defaults to 0. |
| sort_by | string | – | Comma-separated list of fields to sort by. Ascending by default; prefix a field with '-' for descending. |
No output schema declared.
No examples provided.
prtg_get_sensor_status_summary ~43
Get a summary of all sensor states (counts by status - Up, Down, Warning, Paused, etc.) across the whole PRTG instance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prtg_get_version ~32
Get the PRTG core server and appserver version. Useful as a quick credential/connectivity sanity check.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prtg_list_alarms ~186
List sensors currently in a Down/Warning/Unusual/etc. alarm state that match a filter. PRTG's alerting surface - use this to find what's currently wrong.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. |
| include_all_channels | boolean | – | Include all channels per sensor. When false (default), only the primary channel and the Downtime channel are included. |
| limit | number | – | Number of objects to return (max 3000). Defaults to 100. |
| offset | number | – | Zero-based offset into the result set. Defaults to 0. |
| sort_by | string | – | Comma-separated list of fields to sort by. Ascending by default; prefix a field with '-' for descending. |
No output schema declared.
No examples provided.
prtg_list_devices ~184
List monitored devices (hostname/IP, status, parent group/probe). Each device's `id` chains into prtg_get_device, prtg_list_sensors (filter by parent), and prtg_get_object_sensor_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. |
| limit | number | – | Number of objects to return (max 3000). Defaults to 100. |
| offset | number | – | Zero-based offset into the result set. Defaults to 0. |
| sensor_status_summary | boolean | – | Include a sensor-status-summary breakdown for each device. Defaults to false. |
| sort_by | string | – | Comma-separated list of fields to sort by. Ascending by default; prefix a field with '-' for descending. |
No output schema declared.
No examples provided.
prtg_list_groups ~146
List groups (the organizational folders that contain devices). Each group's `id` chains into prtg_get_group and prtg_get_object_sensor_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. |
| limit | number | – | Number of objects to return (max 3000). Defaults to 100. |
| offset | number | – | Zero-based offset into the result set. Defaults to 0. |
| sort_by | string | – | Comma-separated list of fields to sort by. Ascending by default; prefix a field with '-' for descending. |
No output schema declared.
No examples provided.
prtg_list_probes ~167
List probes (the monitoring agents - local, remote, or mini - that run the actual sensor checks). Each probe's `id` chains into prtg_get_probe, prtg_get_probe_network_info, and prtg_get_object_sensor_summary.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. |
| limit | number | – | Number of objects to return (max 3000). Defaults to 100. |
| offset | number | – | Zero-based offset into the result set. Defaults to 0. |
| sort_by | string | – | Comma-separated list of fields to sort by. Ascending by default; prefix a field with '-' for descending. |
No output schema declared.
No examples provided.
prtg_list_sensors ~164
List sensors (the individual checks - ping, HTTP, SNMP, etc. - attached to a device), with their current status. Each sensor's `id` chains into prtg_get_sensor and prtg_get_sensor_data.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. |
| limit | number | – | Number of objects to return (max 3000). Defaults to 100. |
| offset | number | – | Zero-based offset into the result set. Defaults to 0. |
| sort_by | string | – | Comma-separated list of fields to sort by. Ascending by default; prefix a field with '-' for descending. |
No output schema declared.
No examples provided.
What is the PRTG MCP server?
PRTG is an MCP server listed in the public MCP registry as io.github.WYRE-AI/prtg-mcp. MCP server for Paessler PRTG's REST API v2 - network/infrastructure monitoring for MSPs. This page covers its container image (ghcr.io/wyre-ai/prtg-mcp:v1.0.0).
Is the PRTG MCP server safe to use?
PRTG scores 39 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 PRTG MCP server expose?
PRTG exposes 15 tools: prtg_list_devices, prtg_get_device, prtg_list_groups, prtg_get_group, prtg_list_probes, and 10 more. Their descriptions and schemas cost roughly 1,582 tokens of context every time the server is loaded.
Is the PRTG MCP server still maintained?
PRTG 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 PRTG MCP server under?
PRTG 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.