MCP server that provides container image vulnerability scanning and remediation capabilities through Root.io.
873
11 Tools
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
get_remediation_status | Get detailed status and results of an image remediation process. Use the remediation_id returned from 'trigger_remediation' tool. PROCESS STEPS: 'pulling' → 'scanning' → 'evaluating' → 'remediating' → 'rescanning' → 'pushing' → 'completed'. PROCESS STATUS: 'in_progress', 'completed', 'failed'. SCAN STATUS: 'scan_status_pending', 'scan_status_running', 'scan_status_completed', 'scan_status_failed'. Poll this endpoint to track progress and get final results including remediated image details. |
get_user_info | Get current user information including organization details. ESSENTIAL FIRST TOOL: Call this tool at the start of every session to get the organization_id required by most other tools. Returns user profile with organization memberships, roles, and access details. The organization_id from this response should be used in subsequent tool calls like registries_credentials_list, trigger_remediation, and get_remediation_status. |
trigger_remediation | Trigger an asynchronous image remediation process for a container image. WORKFLOW: 1) First use 'get_user_info' to get organization_id. 2) Use 'registries_credentials_list' to get available creds_id values for private registry access. 3) Then use this tool to start remediation. PROCESS: Scans image for vulnerabilities → Creates SBOM → Evaluates OS/arch support → Applies security patches → Rescans → Pushes remediated image to registry. Returns a remediation_id for status tracking with 'get_remediation_status' tool. |
Manual installation
You can install the MCP server using:
Installation for