# AlertOps (oci · ghcr.io/wyre-ai/alertops-mcp:v1.0.0)

MCP server for AlertOps' incident alerting/on-call API.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/alertops-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**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 990 tokens (~90/item across 11 items; 11 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 AlertOps MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

```json
{
  "mcpServers": {
    "wyre-ai-alertops-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/alertops-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 40)

First indexed and scored.

## MCP tools (11)

### `alertops_list_alerts` (~355 tokens)

List alerts, newest first by default. Filter by status (open/closed/assigned/all), a date range (created or closed), a specific AlertID, or by group/integration/escalation-rule IDs. Paginated (Limit, max 100 per page; Offset). AlertIDs from this response are usable directly; message-level lookups (by inbound integration's messageID or uniqueInboundID) are separate tools.

Input parameters:

- `alert_id` (number): Return only this AlertID.
- `alert_status` (number): Open=1, Closed=2, Assigned=5, All=0. Default 0 (all).
- `closed_from_date` (string): Closed-date lower bound, format 'yyyy-mm-dd'.
- `closed_to_date` (string): Closed-date upper bound, format 'yyyy-mm-dd'.
- `date_from` (string): Created-date lower bound, format 'yyyy-mm-dd'.
- `date_to` (string): Created-date upper bound, format 'yyyy-mm-dd'.
- `escalation_list` (string): Comma-separated Escalation Rule IDs to filter by, e.g. "123,456".
- `group_list` (string): Comma-separated Group IDs to filter by, e.g. "123,456". From alertops_list_groups.
- `integration_list` (string): Comma-separated Integration Rule IDs to filter by, e.g. "123,456". From alertops_list_integrations.
- `limit` (number): Page size. Default 10, max 100.
- `offset` (number): Starting point for the result set. Default 0.
- `order` (string): 'desc' (default) or 'asc', by created date.

### `alertops_get_alert_id_by_inbound_message_id` (~68 tokens)

Resolve the AlertID that a given inbound integration messageID was mapped or appended to. The messageID is the value an inbound integration call returns, not the AlertID itself.

Input parameters:

- `message_id` (number, required): The messageID returned by an inbound integration call.

### `alertops_get_alert_id_by_unique_inbound_id` (~74 tokens)

Resolve the AlertID that a given inbound integration's uniqueInboundID was mapped or appended to. The uniqueInboundID is the value an inbound integration call returns, not the AlertID itself.

Input parameters:

- `unique_inbound_id` (string, required): The uniqueInboundID returned by an inbound integration call.

### `alertops_list_users` (~48 tokens)

List all users in the AlertOps account (username, full name, user type). Usernames from this response are required by alertops_get_user_contact_methods and alertops_get_user_schedule.

### `alertops_get_user_contact_methods` (~62 tokens)

List a user's configured contact methods (email, phone/SMS, etc), including whether each is enabled. Contains contact PII. Requires a username from alertops_list_users.

Input parameters:

- `user_name` (string, required): Username, from alertops_list_users.

### `alertops_list_groups` (~53 tokens)

List all groups in the AlertOps account (group ID -> group name). Group IDs from this response are usable by alertops_list_alerts, alertops_get_oncall_now, and alertops_get_group_schedule.

### `alertops_list_topics` (~34 tokens)

List all message topics configured in the AlertOps account, used to route inbound alerts to the right escalation/priority handling.

### `alertops_list_integrations` (~54 tokens)

List configured inbound integrations in the AlertOps account (integration rule ID -> integration type, e.g. AWS, Azure Alert, AppDynamics). Integration Rule IDs from this response are usable by alertops_list_alerts.

### `alertops_get_oncall_now` (~71 tokens)

List who is on-call right now, for every group or (optionally) a single group. Returns each group and its current on-call member(s).

Input parameters:

- `group_id` (number): Optional. Limit to this Group ID, from alertops_list_groups. Omit to return every group.

### `alertops_get_user_schedule` (~85 tokens)

List a specific user's on-call schedule for a date range (max duration 3 months). Requires a username from alertops_list_users.

Input parameters:

- `end_date` (string, required): End date, format 'mm/dd/yyyy'.
- `start_date` (string, required): Start date, format 'mm/dd/yyyy'.
- `user_name` (string, required): Username, from alertops_list_users.

### `alertops_get_group_schedule` (~86 tokens)

List a group's on-call schedule for a date range (max duration 3 months). Requires a Group ID from alertops_list_groups.

Input parameters:

- `end_date` (string, required): End date, format 'mm/dd/yyyy'.
- `group_id` (number, required): Group ID, from alertops_list_groups.
- `start_date` (string, required): Start date, format 'mm/dd/yyyy'.

## Diagnostics

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

## Score history

- 2026-09-20: 40

## Common questions

### What is the AlertOps MCP server?

AlertOps is an MCP server listed in the public MCP registry as io.github.WYRE-AI/alertops-mcp. MCP server for AlertOps' incident alerting/on-call API. This page covers its container image (ghcr.io/wyre-ai/alertops-mcp:v1.0.0).

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

AlertOps scores 40 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 AlertOps MCP server expose?

AlertOps exposes 11 tools: alertops_list_alerts, alertops_get_alert_id_by_inbound_message_id, alertops_get_alert_id_by_unique_inbound_id, alertops_list_users, alertops_get_user_contact_methods, and 6 more. Their descriptions and schemas cost roughly 990 tokens of context every time the server is loaded.

### Is the AlertOps MCP server still maintained?

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

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