Model Context Protocol server for RocketCyber Managed SOC platform integration
RocketCyber MCP has 10 well-named tools with consistent verb_noun patterns (list_, get_, test_). All tools have descriptions and input schemas with typed parameters. However, parameter descriptions are sparse (many lack detail on format/constraints), output schemas are not documented, and error handling guidance is absent. The rocketcyber_list_incidents tool has an exceptionally detailed description (explaining truncation behavior and pagination), but this is the exception. Most tools lack enum constraints for filter parameters (e.g., 'connectivity', 'status', 'severity' accept free-form strings). No tool annotations (readOnlyHint, destructiveHint) are present. Parameter descriptions average ~40 chars, below the 72-char baseline for A+ tools.
Get RocketCyber account information
Get Windows Defender status from RocketCyber
Get event summary/statistics from RocketCyber
Get Office 365 status from RocketCyber
List monitored agents/endpoints in RocketCyber
List managed apps in RocketCyber
Output schemas not documented. Tool descriptions do not specify what fields are returned, forcing LLMs to infer structure and risking incorrect downstream tool chaining.
Filter parameters accept free-form strings instead of enums. 'connectivity', 'status', 'severity', 'platform' lack enum constraints, inviting hallucinated invalid values from LLMs.
Parameter descriptions lack format/constraint details. 'dates' parameter described as 'Date range filter' without specifying format (ISO 8601? Natural language? Relative?). 'sort' field lacks documentation of valid sort keys.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
List security events in RocketCyber. Requires appId - unlike every other list_* tool here, the underlying RocketCyber API rejects this specific endpoint outright (400 "appId is required") if it's omitted, regardless of any other filter supplied. Each RocketCyber "app" is a distinct monitored integration/module (Defender Manager, Office 365 Risk Detection, Datto Ransomware Detection, etc.) - events are always scoped to exactly one. Call rocketcyber_list_apps to see every app this account has and its ID, or rocketcyber_get_event_summary first (no appId needed) to see actual per-app event counts for this account and pick the one with data rather than guessing.
List firewall devices in RocketCyber
List security incidents in RocketCyber. By default, long free-text fields (description, remediation) are truncated to ~300 characters, and the total response is capped at ~40,000 characters (a size cap) — if a page does not fit, only the first incidents are returned and the message says how many; use a smaller pageSize with page to paginate through the rest. Pass verbose: true for full untruncated text.
Test the connection to RocketCyber API
No error handling guidance. Tool descriptions do not explain what errors can occur, when to retry, or how to recover (e.g., 'appId is required' for rocketcyber_list_events is documented in description but no recovery path offered).
No tool annotations. Tools lack readOnlyHint, destructiveHint, or idempotentHint metadata, preventing agents from reasoning about safety and retry semantics.