satellite-anomaly-mcp
Related Servers
Alternatives to satellite-anomaly-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that coordinates autonomous infrastructure health monitoring agents, enabling natural-language telemetry queries and automated diagnosis, remediation, and verification.-
- AlicenseAqualityDmaintenanceMCP server for autonomous MLOps incident response, enabling drift detection, deployment history analysis, and human-approved rollback execution via gated tools.719 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP-powered AI platform for satellite mission control, enabling space weather analysis, orbital collision detection, satellite health monitoring, and secure command validation through natural language.-
- AlicenseNot gradedqualityAmaintenanceA lightweight, air-gapped desktop cockpit connecting local LLMs (Llama 3.2) to standard MCP tools with deterministic hardware safety, acting as an edge-native MCP control plane and autonomous tool dispatcher.2MIT

@vorionsys/mcp-serverofficial
AlicenseAqualityDmaintenanceMCP server for AI-agent governance using trust scoring, behavioral signals, and pre-flight action checks.1010 npm1Apache 2.0- AlicenseAqualityCmaintenanceMCP server for a production-shaped service-business agent, enabling grounded knowledge search, intake collection, and human escalation with deterministic safety boundaries.3MIT
TDQS
Scored across 7 tools
Each tool targets a distinct phase of anomaly handling: evaluation, novelty detection, simulation, diagnosis, and response actions. Even the two detection-oriented tools are clearly differentiated by method and scope, so there is no ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (e.g., evaluate_telemetry, trigger_safe_mode), making the tool set predictable and easy to navigate.
Seven tools is well-scoped for a satellite anomaly management domain, covering detection, diagnosis, simulation, and response without unnecessary redundancy.
The toolset covers the full anomaly response workflow from detection to safe mode, but lacks explicit recovery or restore operations (e.g., reactivating a component after isolation), which is a minor gap.