Rootly Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Rootly Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
MCP server for the Rootly incident management platform.
Built by WYRE Technology — part of the wyre-projects MCP server collection.
Uses decision-tree navigation: start with rootly_navigate to select a domain, then use that domain's tools. Call rootly_back to return.
| Tool | Description |
|---|---|
rootly_navigate | Navigate to a domain: incidents, alerts, schedules, org |
rootly_status | Check connection status and available domains |
rootly_back | Return to the navigation menu |
| Tool | Description |
|---|---|
rootly_incidents_list | List incidents with optional status/severity filters |
rootly_incidents_get | Get a single incident by ID |
rootly_incidents_create | Create a new incident |
rootly_incidents_update | Update title, summary, status, or severity |
rootly_incidents_resolve | Resolve an incident |
| Tool | Description |
|---|---|
rootly_alerts_list | List alerts with optional status filter |
rootly_alerts_acknowledge | Acknowledge an alert |
rootly_alerts_resolve | Resolve an alert |
rootly_alerts_create | Create a new alert |
rootly_alerts_update | Update alert status or summary |
| Tool | Description |
|---|---|
rootly_schedules_list | List on-call schedules |
rootly_schedules_get | Get a single on-call schedule |
| Tool | Description |
|---|---|
rootly_org_list_teams | List teams |
rootly_org_list_severities | List severity levels |
rootly_org_current_user | Get current authenticated user |
cd rootly-mcp
npm install
npm run buildexport ROOTLY_API_TOKEN=rootly_xxxxxxxxxxxxxxxxGet your token from Rootly → Profile → API Tokens.
ROOTLY_API_TOKEN=your_token node dist/index.jsROOTLY_API_TOKEN=your_token MCP_TRANSPORT=http node dist/http.js
# Listens on :8080 — /mcp for MCP, /health for health checkdocker compose up
# or
docker run -e ROOTLY_API_TOKEN=your_token ghcr.io/wyre-technology/rootly-mcp:latest{
"rootly": {
"command": "node",
"args": ["/path/to/rootly-mcp/dist/index.js"],
"env": {
"ROOTLY_API_TOKEN": "rootly_xxxxxxxxxxxxxxxx"
}
}
}Then: mcporter call rootly.rootly_navigate --domain alerts
Download the .mcpb bundle from Releases and install it in Claude Desktop.
Or manually add to claude_desktop_config.json:
{
"mcpServers": {
"rootly": {
"command": "node",
"args": ["/path/to/rootly-mcp/dist/index.js"],
"env": { "ROOTLY_API_TOKEN": "your_token" }
}
}
}Rootly enforces 3 write operations per 60 seconds. The server tracks this in-process and returns a descriptive error with retry-after time if exceeded.
https://api.rootly.com/v1Authorization: Bearer <token>application/vnd.api+jsonnpm run dev # watch mode
npm run lint # TypeScript type-check
npm run test # run testsApache-2.0 © WYRE Technology
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.