# PRTG (oci · ghcr.io/wyre-ai/prtg-mcp:v1.0.0) MCP server for Paessler PRTG's REST API v2 - network/infrastructure monitoring for MSPs. - Trust score: 39/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - oci · `ghcr.io/wyre-ai/prtg-mcp:v1.0.0`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-prtg-mcp/ghcr-io-wyre-ai-prtg-mcp-v1-0-0.md), [page](https://verifymcp.io/servers/wyre-ai-prtg-mcp/ghcr-io-wyre-ai-prtg-mcp-v1-0-0) ## Channel facts - Registry: `oci` - Package: `ghcr.io/wyre-ai/prtg-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**: 82/100 - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 1582 tokens (~105/item across 15 items; 15 tools + 0 resources), lean. - 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 15 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 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. ### Claude ```bash claude mcp add wyre-ai-prtg-mcp -- docker run --rm -i ghcr.io/wyre-ai/prtg-mcp:v1.0.0 ``` ### Cursor ```json { "mcpServers": { "wyre-ai-prtg-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/prtg-mcp:v1.0.0" ] } } } ``` ### VS Code ```json { "servers": { "wyre-ai-prtg-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/prtg-mcp:v1.0.0" ] } } } ``` ### Codex ```bash codex mcp add wyre-ai-prtg-mcp -- docker run --rm -i ghcr.io/wyre-ai/prtg-mcp:v1.0.0 ``` ### opencode ```json { "$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 } } } ``` ### Hermes ```yaml mcp_servers: wyre-ai-prtg-mcp: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/prtg-mcp:v1.0.0"] ``` ### Netclaw ```json { "McpServers": { "wyre-ai-prtg-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/prtg-mcp:v1.0.0" ] } } } ``` ### Other ```json { "mcpServers": { "wyre-ai-prtg-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/prtg-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 39) First indexed and scored. ## MCP tools (15) ### `prtg_list_devices` (~184 tokens) 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. Input parameters: - `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. ### `prtg_get_device` (~74 tokens) Get the metrics and settings of a single device by ID. Input parameters: - `id` (string, required): 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. ### `prtg_list_groups` (~146 tokens) List groups (the organizational folders that contain devices). Each group's `id` chains into prtg_get_group and prtg_get_object_sensor_summary. Input parameters: - `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. ### `prtg_get_group` (~74 tokens) Get the metrics and settings of a single group by ID. Input parameters: - `id` (string, required): 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. ### `prtg_list_probes` (~167 tokens) 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. Input parameters: - `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. ### `prtg_get_probe` (~75 tokens) Get the metrics and settings of a single probe by ID. Input parameters: - `id` (string, required): 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. ### `prtg_get_probe_network_info` (~44 tokens) Get network information (the probe host's own connectivity details) for a probe. Input parameters: - `id` (string, required): Probe ID (from prtg_list_probes). ### `prtg_list_sensors` (~164 tokens) 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. Input parameters: - `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. ### `prtg_get_sensor` (~82 tokens) Get the metrics and settings of a single sensor by ID. Input parameters: - `id` (string, required): 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. ### `prtg_get_sensor_data` (~157 tokens) Get channel measurement history (the actual monitoring/performance data) for a sensor. Input parameters: - `filter` (string): PRTG filter expression to narrow results, e.g. "status == 'Down'". See PRTG API v2 Overview: Filters. - `id` (string, required): 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. ### `prtg_list_alarms` (~186 tokens) 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. Input parameters: - `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. ### `prtg_get_sensor_status_summary` (~43 tokens) Get a summary of all sensor states (counts by status - Up, Down, Warning, Paused, etc.) across the whole PRTG instance. ### `prtg_get_object_sensor_summary` (~59 tokens) Get a sensor-state summary scoped to one probe, group, or device. Input parameters: - `id` (string, required): Probe, group, or device ID (from prtg_list_probes, prtg_list_groups, or prtg_list_devices). ### `prtg_get_channel` (~95 tokens) 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. Input parameters: - `id` (string, required): 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. ### `prtg_get_version` (~32 tokens) Get the PRTG core server and appserver version. Useful as a quick credential/connectivity sanity check. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-prtg-mcp/ghcr-io-wyre-ai-prtg-mcp-v1-0-0#diagnostics ## Score history - 2026-09-20: 39 ## Common questions ### 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. ## Links - Repository: https://github.com/WYRE-AI/prtg-mcp - Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-prtg-mcp/ghcr-io-wyre-ai-prtg-mcp-v1-0-0.xml - Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-prtg-mcp/ghcr-io-wyre-ai-prtg-mcp-v1-0-0.json - HTML version of this page: https://verifymcp.io/servers/wyre-ai-prtg-mcp/ghcr-io-wyre-ai-prtg-mcp-v1-0-0