# io.github.WYRE-AI/rocketcyber-mcp

MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.5.7
- **Author:** io.github.WYRE-AI
- **License:** Unknown
- **Source:** https://github.com/WYRE-AI/rocketcyber-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T01:27:16.862Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `rocketcyber_test_connection` — Test the connection to RocketCyber API
- `rocketcyber_get_account` — Get RocketCyber account information
- `rocketcyber_list_agents` — List monitored agents/endpoints in RocketCyber
- `rocketcyber_list_incidents` — List security incidents in RocketCyber. By default, long free-text fields (description, remediation) are truncated to ~300 characters, and the total response is
- `rocketcyber_list_events` — List security events in RocketCyber. Requires appId - unlike every other list_* tool here,
- `rocketcyber_get_event_summary` — Get event summary/statistics from RocketCyber
- `rocketcyber_list_firewalls` — List firewall devices in RocketCyber
- `rocketcyber_list_apps` — List managed apps in RocketCyber
- `rocketcyber_get_defender` — Get Windows Defender status from RocketCyber
- `rocketcyber_get_office` — Get Office 365 status from RocketCyber

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no package coordinates and no declared endpoint — Forge cannot tell where this would run or whose authority it would borrow. Known so far: holds an api key; read-only tool surface.
- Floor 13, ceiling 25 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Frocketcyber-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Frocketcyber-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.WYRE-AI%2Frocketcyber-mcp
- HTML page: https://forgeregistry.com/registry/io.github.WYRE-AI%2Frocketcyber-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.