remedify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_remediation_planA | Turn vulnerability scan results into a deterministic, actionable remediation plan: per-distro fix commands (apt/yum/dnf/apk/zypper), vendor-backport explanations, reboot/service-restart hints, language-package (Java/npm/Go/...) rebuild instructions, and a 'no fix available' section. Accepts Trivy JSON, Grype JSON, Sysdig scan-result JSON, or Sysdig report CSV (auto-detected). |
| fetch_sysdig_planA | Fetch recent runtime scan results from the Sysdig Vulnerability Management API and generate remediation plans, with a fleet summary ('one fix -> N workloads') when multiple workloads are requested. Requires the SYSDIG_API_TOKEN environment variable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one generates a plan from various scan result formats, while the other fetches results from a specific API and then generates a plan. They do not overlap.
Both tool names use a consistent verb_noun pattern with snake_case: 'generate_remediation_plan' and 'fetch_sysdig_plan'. The naming is predictable and uniform.
With only 2 tools, the server feels minimal. While the core functionality of generating remediation plans is covered, the count is low for a typical MCP server, though not extreme.
The server covers generation and fetching of plans, but lacks tools for exporting, applying, or managing remediation plans. There are notable gaps in the lifecycle.