Skip to content

fix(rh-sre): use get_mcp_version in mcp-lightspeed-validator #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dmartinol merged 1 commit into from
Jun 22, 2026
Merged

fix(rh-sre): use get_mcp_version in mcp-lightspeed-validator #125

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions rh-sre/skills/cve-impact/docs/references/lightspeed-mcp-tool-failures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,13 @@ When Lightspeed MCP tools fail with cryptic backend errors (e.g. KeyError, missi

**Cause**: Some MCP clients incorrectly serialize the `limit` parameter as `limit_`. The Lightspeed MCP server expects `limit` (no underscore).

**Workaround**: For connectivity tests, call with **no parameters**—the tool uses default `limit=10`:
**Workaround**: Call with **no parameters**—the tool uses default `limit=10`:
```
vulnerability__get_cves()
```
Or pass only parameters that don't trigger the bug (e.g. `impact`, `sort`, `advisory_available`). Avoid passing `limit` when the client may serialize it as `limit_`.

**Skills affected**: mcp-lightspeed-validator (connectivity test), cve-impact (account-level CVE queries).
**Skills affected**: cve-impact (account-level CVE queries). For MCP connectivity validation, use `/mcp-lightspeed-validator` which calls `get_mcp_version` instead.

### vulnerability__explain_cves — `'dnf_modules'` (or similar KeyError)

Expand Down
8 changes: 4 additions & 4 deletions rh-sre/skills/mcp-lightspeed-validator/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,20 +5,20 @@ description: |
model: haiku
color: yellow
license: Apache-2.0
allowed-tools: vulnerability__get_cves
allowed-tools: get_mcp_version
---

# MCP Lightspeed Validator

Validates connectivity to the Red Hat Lightspeed MCP server by running a lightweight tool call.
Validates connectivity to the Red Hat Lightspeed MCP server by calling `get_mcp_version`.

## When to Use This Skill

Use when validating Lightspeed MCP before CVE operations, troubleshooting connection issues, or when other skills (e.g. remediation) need to verify availability. Do NOT use for actual CVE queries—use cve-impact or cve-validation.

## Workflow

1. **Test connectivity**: Call `vulnerability__get_cves` with **no parameters** (uses default limit=10). Do NOT pass `limit`—some MCP clients incorrectly serialize it as `limit_`, causing validation errors.
1. **Test connectivity**: Call `get_mcp_version` with **no parameters**.
2. **If it fails**: Provide a comprehensive message with possible root causes (see below).
3. **Report**: Output a table with validated servers and outcome (emojis).

Expand Down Expand Up @@ -60,7 +60,7 @@ Use ✅ for success, ❌ for failure, ⚠️ for partial (e.g. connected but err
- `lightspeed-mcp` - Red Hat Lightspeed vulnerability and inventory data

### Required MCP Tools
- `vulnerability__get_cves` or `get_cves` (from lightspeed-mcp) - Connectivity test
- `get_mcp_version` (from lightspeed-mcp gateway) - Connectivity test

### Related Skills
- `/remediation` - Requires Lightspeed MCP validation before CVE operations
Expand Down
Loading