Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/rootly

PYPI · MCPARMORY-ROOTLY · 2 COMPONENTS · SCANNED SEP 20

Manage incident alerts, events, and workflows with custom automations

0 this week 37 Trust /100
Trust breakdown (7 categories)

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 Security87
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Install-script risk not yet assessed.Unverified
  • 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
  • Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change.Unverified
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full, and the trim removes the very descriptions this category reads.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the com.mcparmory/rootly MCP server?

com.mcparmory/rootly runs locally as a PyPI package, launched with uvx mcparmory-rootly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-rootly

# add to Claude Code
claude mcp add com-mcparmory-rootly -- uvx mcparmory-rootly
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-rootly": {
      "command": "uvx",
      "args": [
        "mcparmory-rootly"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-rootly": {
      "command": "uvx",
      "args": [
        "mcparmory-rootly"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-rootly -- uvx mcparmory-rootly
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-rootly": {
      "type": "local",
      "command": [
        "uvx",
        "mcparmory-rootly"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mcparmory-rootly --command uvx --arg mcparmory-rootly
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-rootly:
    command: "uvx"
    args: ["mcparmory-rootly"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-rootly": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcparmory-rootly"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-mcparmory-rootly -t stdio -c uvx -a mcparmory-rootly
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-rootly": {
      "command": "uvx",
      "args": [
        "mcparmory-rootly"
      ]
    }
  }
}
Changelog

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.

  • 16 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 31 Aug 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
  • 26 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Aug 26 0
    • Malware scan: unverified → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Aug 26 0
    • Malware scan: pass → unverified security
    • Stability: Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change. security
    • MCP protocol: unverified → pass functional
    • Tool coverage: Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy. functional
    • Schema quality: Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy. functional
  • 4 Aug 26 0
    • Malware scan: unverified → pass security
Diagnostics

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 20 Sept 2026 · Analysed pypi/mcparmory-rootly@1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Dependencies 41 packages
Packages resolved 41
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 348 exposed · ~54,819 tokens partial

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 →

Tool Tokens
create_postmortem_template ~188

No description provided.

NameTypeReqDescription
contentstringyes
defaultboolean
formatstring
namestringyes
typestringyes

No output schema declared.

No examples provided.

create_pulse ~324

No description provided.

NameTypeReqDescription
dataobject
ended_atstring
environment_idsarray
external_urlstring
service_idsarray
sourcestring
summarystringyes
typestringyes

No output schema declared.

No examples provided.

create_retrospective_process ~203

No description provided.

NameTypeReqDescription
copy_fromstringyes
descriptionstring
namestringyes
retrospective_process_matching_criteria
typestringyes

No output schema declared.

No examples provided.

create_retrospective_step ~198

No description provided.

NameTypeReqDescription
descriptionstring
due_after_daysinteger
positioninteger
retrospective_process_idstringyes
skippableboolean
titlestringyes
typestringyes

No output schema declared.

No examples provided.

create_schedule ~202

No description provided.

NameTypeReqDescription
all_time_coverageboolean
descriptionstring
namestringyes
owner_group_idsarray
owner_user_idinteger
typestringyes

No output schema declared.

No examples provided.

create_schedule_rotation ~323

No description provided.

NameTypeReqDescription
active_daysarray
active_time_attributesarray
namestringyes
positioninteger
schedule_idstringyes
schedule_rotationable_attributesobjectyes
schedule_rotationable_typestringyes
time_zonestring
typestringyes

No output schema declared.

No examples provided.

create_service ~582

No description provided.

NameTypeReqDescription
alert_urgency_idstring
alerts_email_enabledboolean
backstage_idstring
colorstring
cortex_idstring
descriptionstring
environment_idsarray
external_idstring
github_repository_branchstring
github_repository_namestring
gitlab_repository_branchstring
gitlab_repository_namestring
namestringyes
notify_emailsarray
opsgenie_team_idstring
owner_group_idsarray
owner_user_idsarray
positioninteger
public_descriptionstring
service_idsarray
service_now_ci_sys_idstring
show_uptimeboolean
show_uptime_last_daysinteger
slack_aliasesarray
slack_channelsarray
typestringyes

No output schema declared.

No examples provided.

create_severity ~283

No description provided.

NameTypeReqDescription
colorstring
descriptionstring
namestringyes
notify_emailsarray
positioninteger
severitystring
slack_aliasesarray
slack_channelsarray
typestringyes

No output schema declared.

No examples provided.

create_status_page ~542

No description provided.

NameTypeReqDescription
allow_search_engine_indexboolean
authentication_enabledboolean
authentication_passwordstring
descriptionstring
enabledboolean
failure_messagestring
footer_colorstring
functionality_idsarray
ga_tracking_idstring
header_colorstring
publicboolean
public_descriptionstring
public_titlestring
service_idsarray
show_uptimeboolean
show_uptime_last_daysinteger
success_messagestring
time_zonestring
titlestringyes
typestringyes
website_privacy_urlstring
website_support_urlstring
website_urlstring

No output schema declared.

No examples provided.

create_team ~575

No description provided.

NameTypeReqDescription
admin_idsarray
alert_urgency_idstring
alerts_email_enabledboolean
backstage_idstring
colorstring
cortex_idstring
descriptionstring
external_idstring
namestringyes
notify_emailsarray
opsgenie_team_idstring
pagerduty_service_idstring
pagertree_idstring
positioninteger
service_now_ci_sys_idstring
slack_aliasesarray
slack_channelsarray
typestringyes
user_idsarray
victor_ops_idstring

No output schema declared.

No examples provided.

create_workflow_run ~109

No description provided.

NameTypeReqDescription
attributesyes
typestringyes
workflow_idstringyes

No output schema declared.

No examples provided.

create_workflow_task ~198

No description provided.

NameTypeReqDescription
enabledboolean
positioninteger
skip_on_failureboolean
task_paramsyes
typestringyes
workflow_idstringyes

No output schema declared.

No examples provided.

delete_alert_event ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_alert_group ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_alert_source ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_alert_urgency ~49

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_authorization ~41

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_catalog ~40

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_catalog_entity ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_catalog_entity_property ~50

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_catalog_field ~42

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_cause ~40

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_custom_form ~42

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_dashboard ~39

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_dashboard_panel ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_email_address ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_environment ~40

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_escalation_level ~44

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_escalation_path ~45

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_escalation_policy ~52

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_form_field ~42

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_form_field_option ~49

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_form_field_placement_condition ~59

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_form_set ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_form_set_condition ~49

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_functionality ~40

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_heartbeat ~41

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident ~41

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_action_item ~52

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_event ~44

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_event_functionality ~48

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_event_service ~47

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_role ~43

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_role_task ~47

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_incident_type ~52

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_live_call_router ~45

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_notification_rule ~49

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_on_call_shadow ~52

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_override_shift ~61

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

delete_playbook ~42

No description provided.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/rootly MCP server?

com.mcparmory/rootly is an MCP server listed in the public MCP registry as com.mcparmory/rootly. Manage incident alerts, events, and workflows with custom automations. This page covers its PyPI package (mcparmory-rootly).

Is the com.mcparmory/rootly MCP server safe to use?

com.mcparmory/rootly scores 37 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.

Is the com.mcparmory/rootly MCP server still maintained?

com.mcparmory/rootly 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.