prescryb
Related Servers
Alternatives to prescryb
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that provides deterministic remediation plans from vulnerability scan data (Trivy, Grype, Sysdig) via tools to generate plans from scan content or fetch live from Sysdig API, enabling AI agents to produce concrete, distro-aware fix commands.22Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that provides SSH tools (read-only probes and arbitrary exec) to a fleet of hosts outside Kubernetes, with an inventory-based allowlist and key-based authentication.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes SOC2 and HIPAA compliance remediation logic as structured tools for AI agents to call, enabling an LLM-driven workflow to discover, assess, remediate, and report on compliance controls.MIT
- FlicenseNot gradedqualityBmaintenanceEnables deterministic triage of OpenShift alerts by executing YAML-defined runbooks against an upstream OCP MCP server, collecting auditable evidence bundles for LLM interpretation.-
- AlicenseBqualityAmaintenanceA lightweight, self-hosted MCP server that connects LLM-based agents to Red Hat Lightspeed services, enabling natural language querying of read-only (and optionally write) operations across Advisor, Image Builder, Inventory, Planning, Remediations, and Vulnerability services.4224Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for querying CVE and package vulnerability data from NVD and OSV.dev, allowing CVE lookups and dependency scanning.41MIT
TDQS
Scored across 7 tools
Each tool has a unique, well-defined purpose: checking CVEs, fetching advisories, generating playbooks, inventorying hosts, listing CCE targets, looking up CCE entries, and mapping compliance topics. No functional overlap exists.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_cves, fetch_advisory, generate_playbook). The naming style is uniform and predictable.
With 7 tools, the set is well-scoped for its security compliance domain. Each tool covers a necessary step in the workflow (inventory, CVE scanning, advisory lookup, compliance mapping, playbook generation) without extraneous additions.
The tool surface covers the full lifecycle: inventory → CVE matching → advisory retrieval → compliance mapping (CCE and CIS/DISA) → playbook generation. No critical gaps are apparent for the stated purpose of automated compliance remediation.