AlertOps
OCI · GHCR.IO/WYRE-AI/ALERTOPS-MCP
MCP server for AlertOps' incident alerting/on-call API.
Available components
Last scanned (15 hours ago)
Scores higher than 56% of OCI servers
Category Monitoring and Observability
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 990 tokens (~90/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
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.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 +34
- Provenance: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 6
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 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/alertops-mcp@v1.0.1
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 →
alertops_get_alert_id_by_inbound_message_id ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | number | yes | The messageID returned by an inbound integration call. |
No output schema declared.
No examples provided.
alertops_get_alert_id_by_unique_inbound_id ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| unique_inbound_id | string | yes | The uniqueInboundID returned by an inbound integration call. |
No output schema declared.
No examples provided.
alertops_get_group_schedule ~86
List a group's on-call schedule for a date range (max duration 3 months). Requires a Group ID from alertops_list_groups.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | End date, format 'mm/dd/yyyy'. |
| group_id | number | yes | Group ID, from alertops_list_groups. |
| start_date | string | yes | Start date, format 'mm/dd/yyyy'. |
No output schema declared.
No examples provided.
alertops_get_oncall_now ~71
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).
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | number | – | Optional. Limit to this Group ID, from alertops_list_groups. Omit to return every group. |
No output schema declared.
No examples provided.
alertops_get_user_contact_methods ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| user_name | string | yes | Username, from alertops_list_users. |
No output schema declared.
No examples provided.
alertops_get_user_schedule ~85
List a specific user's on-call schedule for a date range (max duration 3 months). Requires a username from alertops_list_users.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | End date, format 'mm/dd/yyyy'. |
| start_date | string | yes | Start date, format 'mm/dd/yyyy'. |
| user_name | string | yes | Username, from alertops_list_users. |
No output schema declared.
No examples provided.
alertops_list_alerts ~355
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
alertops_list_groups ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
alertops_list_integrations ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
alertops_list_topics ~34
List all message topics configured in the AlertOps account, used to route inbound alerts to the right escalation/priority handling.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
alertops_list_users ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the AlertOps MCP server?
AlertOps runs locally as a container image, launched with docker run --rm -i -e ALERTOPS_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/alertops-mcp:v1.0.1. 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/alertops-mcp
claude mcp add wyre-ai-alertops-mcp -- docker run --rm -i -e ALERTOPS_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/alertops-mcp:v1.0.1
This image reads ALERTOPS_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
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).
Is the AlertOps MCP server safe to use?
AlertOps scores 41 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 18 October 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.