# SaaS Alerts (oci · ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4)

MCP server for Kaseya SaaS Alerts — SaaS security monitoring for M365 & Google Workspace.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-saas-alerts-mcp/ghcr-io-wyre-technology-saas-alerts-mcp-v1-2-4.md), [page](https://verifymcp.io/servers/wyre-technology-saas-alerts-mcp/ghcr-io-wyre-technology-saas-alerts-mcp-v1-2-4)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4`
- 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-08-22.

- **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**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1857 tokens (~61/item across 30 items; 30 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.
- **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 SaaS Alerts MCP server?

SaaS Alerts runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4. 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-technology-saas-alerts-mcp -- docker run --rm -i ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-technology-saas-alerts-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-technology-saas-alerts-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-technology-saas-alerts-mcp -- docker run --rm -i ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  wyre-technology-saas-alerts-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-technology-saas-alerts-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-technology-saas-alerts-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4"
      ]
    }
  }
}
```

## 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-08-21 (score 39)

First indexed and scored.

## MCP tools (30)

### `saas_alerts_navigate` (~67 tokens)

Browse a domain to see its available tools and descriptions. All tools are callable at any time — navigation is optional discovery, not a gate.

Input parameters:

- `domain` (string, required): Domain to inspect. One of: events, customers, users, devices, billing, reports, partner

### `saas_alerts_status` (~34 tokens)

Check connectivity to SaaS Alerts by fetching the authenticated MSP user. Returns the list of available domains and connection status.

### `saas_alerts_events_query` (~264 tokens)

Query security events from SaaS Alerts with optional filters. Returns a paginated list of events matching the specified criteria. Events are compacted to triage-relevant fields by default; pass verbose: true for full raw records. Compact responses are capped at ~40,000 characters — over-cap result sets are truncated to the first events that fit, so prefer a modest size with from/size pagination or a narrower date range.

Input parameters:

- `alert_status` (string): Filter by alert severity
- `customer_id` (string): Filter by SaaS Alerts customer ID
- `end_date` (string): End of range — ISO-8601 timestamp or epoch ms (inclusive)
- `event_type` (array): Filter by one or more event types
- `from` (number): Offset for pagination
- `size` (number): Maximum results to return (default 50)
- `start_date` (string): Start of range — ISO-8601 timestamp or epoch ms (inclusive)
- `time_sort` (string): Sort direction on event timestamp
- `user_email` (string): Filter by user email (UPN)
- `verbose` (boolean): Return full raw event records (large). Default false: events are compacted to triage-relevant fields.

### `saas_alerts_events_count` (~104 tokens)

Count security events matching the given filters without fetching full records.

Input parameters:

- `alert_status` (string): Filter by alert severity
- `customer_id` (string): Filter by customer ID
- `end_date` (string): End of range — ISO-8601 timestamp or epoch ms (inclusive)
- `event_type` (array): Filter by event types
- `start_date` (string): Start of range — ISO-8601 timestamp or epoch ms (inclusive)

### `saas_alerts_events_query_advanced` (~168 tokens)

Execute an advanced Elasticsearch query against the SaaS Alerts events index. Accepts a raw Elasticsearch query body for maximum flexibility. Event hits are compacted to triage-relevant fields by default; pass verbose: true for full raw records. Compact responses are capped at ~40,000 characters — over-cap hit lists are truncated to the first hits that fit (hits.total still reports the true match count), so prefer a modest size with from/size in the query body.

Input parameters:

- `query` (object, required): Elasticsearch query body (e.g. { "query": { "term": { "alertStatus": "critical" } } })
- `verbose` (boolean): Return full raw event records (large). Default false: events are compacted to triage-relevant fields.

### `saas_alerts_events_count_advanced` (~37 tokens)

Count events using a raw Elasticsearch query body without fetching full records.

Input parameters:

- `query` (object, required): Elasticsearch query body

### `saas_alerts_events_scroll` (~163 tokens)

Continue paginating through a previous event query result set using a scroll ID. Call after saas_alerts_events_query_advanced returns a scroll ID. Event hits are compacted to triage-relevant fields by default; pass verbose: true for full raw records. Compact responses are capped at ~40,000 characters — if a scroll page exceeds the cap it is truncated, and the trimmed events canNOT be recovered by continuing the scroll (the server cursor has already advanced past them); re-run the originating query with a smaller size instead.

Input parameters:

- `scroll_id` (string, required): Scroll ID returned by a previous query
- `verbose` (boolean): Return full raw event records (large). Default false: events are compacted to triage-relevant fields.

### `saas_alerts_recommended_actions` (~38 tokens)

Get the list of recommended remediation actions for SaaS Alerts event types. Use this to map detected event types to actionable guidance.

### `saas_alerts_customers_list` (~24 tokens)

List all SaaS Alerts customers for the authenticated partner.

### `saas_alerts_customers_get` (~33 tokens)

Get a single SaaS Alerts customer by ID.

Input parameters:

- `customer_id` (string, required): Customer ID

### `saas_alerts_customers_create` (~42 tokens)

Create a new SaaS Alerts customer for the authenticated partner.

Input parameters:

- `body` (object, required): Customer creation payload (see SaaS Alerts API docs)

### `saas_alerts_customers_update` (~45 tokens)

Update an existing SaaS Alerts customer by ID.

Input parameters:

- `body` (object, required): Fields to update
- `customer_id` (string, required): Customer ID to update

### `saas_alerts_customers_delete` (~62 tokens)

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a SaaS Alerts customer and all associated data. This action cannot be undone. Confirm with the user before invoking.

Input parameters:

- `customer_id` (string, required): Customer ID to delete

### `saas_alerts_customers_set_whitelists` (~73 tokens)

⚠ HIGH-IMPACT. Replace the IP/country whitelist for a customer. This overwrites the existing whitelist. Confirm with the user before invoking.

Input parameters:

- `body` (object, required): Whitelist payload (IPs and/or country codes)
- `customer_id` (string, required): Customer ID

### `saas_alerts_customers_set_account_whitelists` (~68 tokens)

⚠ HIGH-IMPACT. Replace the account-level whitelist for a customer. This overwrites the existing account whitelist. Confirm with the user before invoking.

Input parameters:

- `body` (object, required): Account whitelist payload
- `customer_id` (string, required): Customer ID

### `saas_alerts_users_get_msp` (~35 tokens)

Get the MSP user profile associated with the authenticated API key. Also used as a connectivity / credential check.

### `saas_alerts_users_list_partner` (~23 tokens)

List all users associated with the authenticated partner account.

### `saas_alerts_users_list_by_customer` (~40 tokens)

List all users belonging to a specific SaaS Alerts customer.

Input parameters:

- `customer_id` (string, required): Customer ID to list users for

### `saas_alerts_devices_list_mapped` (~44 tokens)

List devices that have been mapped (unified) to SaaS Alerts customer organizations.

Input parameters:

- `organization_ids` (array, required): Organization IDs to filter by

### `saas_alerts_devices_list_unmapped` (~98 tokens)

List devices that have NOT yet been mapped to a SaaS Alerts organization. Optionally filter by confidence score or whether mapping suggestions are available.

Input parameters:

- `confidence` (number): Minimum confidence threshold (0–1) for mapping suggestions
- `only_with_suggestions` (boolean): If true, return only devices that have at least one mapping suggestion
- `organization_ids` (array, required): Organization IDs to include in the search

### `saas_alerts_devices_list_ignored` (~37 tokens)

List devices that have been explicitly marked as ignored.

Input parameters:

- `organization_ids` (array, required): Organization IDs to filter by

### `saas_alerts_devices_list_orgs` (~24 tokens)

List all device organizations visible to the authenticated partner.

### `saas_alerts_billing_get_details` (~53 tokens)

Retrieve billing details for a specific billing date. Use saas_alerts_billing_list_dates first to discover available dates.

Input parameters:

- `billing_date` (string, required): Billing date in YYYY-MM-DD format

### `saas_alerts_billing_list_dates` (~40 tokens)

List all available billing dates for the authenticated partner. Use the returned dates as input to saas_alerts_billing_get_details.

### `saas_alerts_reports_list_scheduled` (~24 tokens)

List all scheduled reports configured for the authenticated partner.

### `saas_alerts_reports_get_scheduled` (~34 tokens)

Get a specific scheduled report by its ID.

Input parameters:

- `report_id` (string, required): Scheduled report ID

### `saas_alerts_reports_create_scheduled` (~38 tokens)

Create a new scheduled report.

Input parameters:

- `body` (object, required): Scheduled report configuration payload (see SaaS Alerts API docs)

### `saas_alerts_reports_delete_scheduled` (~58 tokens)

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently delete a scheduled report. This action cannot be undone. Confirm with the user before invoking.

Input parameters:

- `report_id` (string, required): Scheduled report ID to delete

### `saas_alerts_partner_get_profile` (~24 tokens)

Get the partner profile associated with the authenticated API key.

### `saas_alerts_partner_update_branding` (~63 tokens)

⚠ HIGH-IMPACT. Update the partner branding settings (logo, colours, etc.). This overwrites existing branding. Confirm with the user before invoking.

Input parameters:

- `body` (object, required): Branding payload (logoUrl, primaryColor, etc.)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-technology-saas-alerts-mcp/ghcr-io-wyre-technology-saas-alerts-mcp-v1-2-4#diagnostics

## Score history

- 2026-08-22: 39
- 2026-08-21: 39

## Common questions

### What is the SaaS Alerts MCP server?

SaaS Alerts is an MCP server listed in the public MCP registry as io.github.wyre-technology/saas-alerts-mcp. MCP server for Kaseya SaaS Alerts, SaaS security monitoring for M365 & Google Workspace. This page covers its container image (ghcr.io/wyre-technology/saas-alerts-mcp:v1.2.4).

### Is the SaaS Alerts MCP server safe to use?

SaaS Alerts 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 SaaS Alerts MCP server expose?

SaaS Alerts exposes 30 tools: saas_alerts_navigate, saas_alerts_status, saas_alerts_events_query, saas_alerts_events_count, saas_alerts_events_query_advanced, and 25 more. Their descriptions and schemas cost roughly 1,857 tokens of context every time the server is loaded.

### Is the SaaS Alerts MCP server still maintained?

SaaS Alerts is still listed as active in the MCP registry. We last reached this channel on 22 August 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 SaaS Alerts MCP server under?

SaaS Alerts 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-technology/saas-alerts-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-saas-alerts-mcp/ghcr-io-wyre-technology-saas-alerts-mcp-v1-2-4.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-saas-alerts-mcp/ghcr-io-wyre-technology-saas-alerts-mcp-v1-2-4.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-saas-alerts-mcp/ghcr-io-wyre-technology-saas-alerts-mcp-v1-2-4