Is io.github.wyre-technology/saas-alerts-mcp safe to use?

io.github.wyre-technology/saas-alerts-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.wyre-technology/saas-alerts-mcp?

io.github.wyre-technology/saas-alerts-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.wyre-technology/saas-alerts-mcp?

io.github.wyre-technology/saas-alerts-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.wyre-technology/saas-alerts-mcp actively maintained?

io.github.wyre-technology/saas-alerts-mcp is actively maintained — last commit was 17 days ago.

io.github.wyre-technology/saas-alerts-mcp

npm

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

14.4M/wk GitHub npm

No known CVEs

No license

Actively maintained

Last commit 17d ago

Works with most clients

Transport: stdio

0 tools

Grade F

MCPpedia last refreshed this data 16h ago

Edit this pageView history

Cloud Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-wyre-technology-saas-alerts-mcp-wyre-technology": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wyre-technology-saas-alerts-mcp-wyre-technology)](https://mcppedia.org/s/io-github-wyre-technology-saas-alerts-mcp-wyre-technology)

Read me

What io.github.wyre-technology/saas-alerts-mcp does

Model Context Protocol server for Kaseya SaaS Alerts — a SaaS security monitoring platform for M365 and Google Workspace events.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

20/100across 5 weighted dimensions

How we score →

0255075100

−80

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked npm against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wyre-technology/saas-alerts-mcp safe to use?: io.github.wyre-technology/saas-alerts-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.wyre-technology/saas-alerts-mcp?: io.github.wyre-technology/saas-alerts-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.wyre-technology/saas-alerts-mcp?: io.github.wyre-technology/saas-alerts-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.wyre-technology/saas-alerts-mcp actively maintained?: io.github.wyre-technology/saas-alerts-mcp is actively maintained — last commit was 17 days ago.

Similar servers

Others in cloud / developer-tools

View all →

Context797

Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

59.5k 2

XcodeBuildMCP97

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

6.1k 2

Supabase MCP Server97

Manage Supabase projects — databases, auth, storage, and edge functions

2.8k 4

Cli96

The official TanStack CLI - Project Scaffolding, MCP Server, Agent Skills Installation, etc

1.3k 3

MCP Security Weekly

Get CVE alerts and security updates for io.github.wyre-technology/saas-alerts-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Cloud Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-wyre-technology-saas-alerts-mcp-wyre-technology": {
      "args": [
        "-y",
        "npm"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wyre-technology-saas-alerts-mcp-wyre-technology)](https://mcppedia.org/s/io-github-wyre-technology-saas-alerts-mcp-wyre-technology)

Read me

What io.github.wyre-technology/saas-alerts-mcp does

Model Context Protocol server for Kaseya SaaS Alerts — a SaaS security monitoring platform for M365 and Google Workspace events.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

saas-alerts-mcp

Model Context Protocol server for Kaseya SaaS Alerts — a SaaS security monitoring platform for M365 and Google Workspace events.

Part of the WYRE Technology MCP fleet.

Features

Exposes the full SaaS Alerts External Partner API (v0.20.0) through 30 MCP tools organized by domain:

Domain	Tools
events	Query/count security events by severity, customer, user, event type; advanced Elasticsearch queries; scroll pagination; recommended actions
customers	List, get, create, update, delete customers; set IP/country and account whitelists
users	MSP user info, partner users, customer users
devices	Unify mapped/unmapped/ignored devices, device organizations
billing	Billing details by date, billing date history
reports	List/get/create/delete scheduled reports
partner	Partner profile, branding settings

Write/destructive tools require user confirmation via MCP elicitation (fail-open: proceeds if client doesn't support elicitation).

Authentication

SaaS Alerts uses an API key sent as the api_key HTTP header.

Generate your API key in the SaaS Alerts UI under Settings → API Keys.

Local / stdio mode

export SAAS_ALERTS_API_KEY=your-api-key
node dist/index.js

HTTP mode

export SAAS_ALERTS_API_KEY=your-api-key
export MCP_TRANSPORT=http
export MCP_HTTP_PORT=8080
node dist/http.js

WYRE Gateway mode

When running behind the WYRE MCP Gateway, set AUTH_MODE=gateway. The gateway injects the API key per-request via the X-SaaS-Alerts-API-Key header — no env var needed.

Running with Docker

docker compose up

Or pull from GHCR:

docker run -e SAAS_ALERTS_API_KEY=your-key \
  -e MCP_TRANSPORT=http \
  -p 8080:8080 \
  ghcr.io/wyre-technology/saas-alerts-mcp:latest

Development

npm install
npm run build
npm test
npm run lint
node scripts/lint-destructive-warnings.mjs src

Destructive tool confirmation

Tools that permanently delete data (customer delete, scheduled report delete) carry:

⚠ DESTRUCTIVE — IRREVERSIBLE description prefix
annotations.destructiveHint: true
Elicitation confirmation guard (additive — proceeds if client doesn't support elicitation)

Always confirm with the user before invoking these tools.

License

Apache-2.0 — see LICENSE.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

20/100across 5 weighted dimensions

How we score →

0255075100

−80

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked npm against OSV.dev.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wyre-technology/saas-alerts-mcp safe to use?: io.github.wyre-technology/saas-alerts-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.wyre-technology/saas-alerts-mcp?: io.github.wyre-technology/saas-alerts-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.wyre-technology/saas-alerts-mcp?: io.github.wyre-technology/saas-alerts-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.wyre-technology/saas-alerts-mcp actively maintained?: io.github.wyre-technology/saas-alerts-mcp is actively maintained — last commit was 17 days ago.