MCP Mirror Endpoint + RHOAI Version Normalization (issue 7 of 29)

[gabemontero]

Labels: ready-to-code
Dependencies: None
RHIDP Stories: RHIDP-15317, RHIDP-15321
Feature: RHDHPLAN-1510 — Epics RHIDP-15313, RHIDP-15314
Cross-feature dependency: RHIDP-15317 depends on RHIDP-15655 (Implement MCP Registry entity provider, RHDHPLAN-393). The upstream community provider must exist before the productization layer can override its endpoint configuration. RHIDP-15321 (RHOAI version normalization) has no RHDHPLAN-393 dependency and can start immediately.

Implement the MCP Registry mirror endpoint configuration with zero-internet validation (no outbound traffic to public endpoint when mirror is configured), startup health check, and non-HTTPS security warnings. Also implement RHOAI version normalization utility for MCP server entity rhdh.io/ai-asset-version annotation population. RHIDP-15321 has no cross-connector dependencies and can start immediately; RHIDP-15317 is blocked on the upstream MCP Registry entity provider (RHDHPLAN-393 RHIDP-15655).

Tasks

From openspec/changes/mcp-registry-connector/tasks.md group 1 (RHIDP-15317):

• 1.1 Add ai-catalog.providers.mcpRegistry.endpoint config schema in config.d.ts
• 1.2 Implement endpoint configuration loading from app-config
• 1.3 Add environment variable override support (MCP_REGISTRY_ENDPOINT)
• 1.4 Implement endpoint URL validation
• 1.5 Add endpoint fallback logic (app-config > env var > default public endpoint)
• 1.6 Implement startup endpoint validation health check
• 1.7 Add endpoint configuration logging at connector startup
• 1.8 Add security warning for non-HTTPS endpoints
• 1.9 Implement HTTP client configuration with mirror endpoint URL
• 1.10 Add Prometheus metrics for endpoint request count, latency, error rate
• 1.11 Add Prometheus metric for public endpoint violation detection
• 1.12–1.18 Integration tests: zero outbound traffic, mirror targeting, DNS resolution, retry backoff, invalid URL, non-HTTPS warning, override precedence
• 1.19–1.20 Documentation: mirror endpoint examples, zero-internet validation

From openspec/changes/rhoai-connector/tasks.md group 7 (RHIDP-15321):

• 7.1 Define version normalization rules
• 7.2 Implement normalizeVersion(rawVersion) utility — semver normalization, strip v prefix, handle latest/nightly
• 7.3 Populate rhdh.io/ai-asset-version annotation with normalized version
• 7.4 Handle missing version metadata: set "unknown" with DEBUG log
• 7.5 Handle invalid version strings: set "unknown" with WARNING log
• 7.6 Unit tests for version normalization
• 7.7 Integration test: emitted entities carry correct annotation

Specifications

• openspec/changes/mcp-registry-connector/specs/mirror-endpoint/spec.md
• openspec/changes/rhoai-connector/specs/mcp-catalog-source/spec.md

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:00 PM UTC · Completed 8:05 PM UTC
Commit: e03b281 · View workflow run →

[fullsend-ai-triage]

Triage Assessment

This issue bundles two work items with different dependency profiles:

RHIDP-15321 — RHOAI Version Normalization (tasks 7.1–7.7) ✅ Unblocked

This work has no cross-connector dependencies and can start immediately. It involves implementing normalizeVersion(), populating the rhdh.io/ai-asset-version annotation, and handling edge cases (missing metadata, invalid strings).

RHIDP-15317 — MCP Mirror Endpoint (tasks 1.1–1.20) 🚫 Blocked

This work is blocked on RHIDP-15655 (Implement MCP Registry entity provider, RHDHPLAN-393). The upstream community provider must exist before the productization layer can override its endpoint configuration. No tracking issue for RHIDP-15655 was found in this repo, backstage/backstage, or backstage/community-plugins.

Recommendation

A tracking issue should be created for the upstream MCP Registry entity provider (RHIDP-15655) so the dependency is visible and can be monitored. In the meantime, the RHOAI version normalization work (RHIDP-15321) can proceed independently.

Downstream impact: Issues #4051 (TLS Hardening) and #4052 (Annotation Enrichment) also depend on or reference RHDHPLAN-393, so resolving this upstream dependency unblocks multiple items in the series.

Blocked by:

• Implement upstream MCP Registry entity provider (RHIDP-15655 / RHDHPLAN-393) #4068

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 7:59 PM UTC · Completed 8:01 PM UTC
Commit: 924cefe · View workflow run →

[fullsend-ai-triage]

Triage Assessment (re-evaluated)

This issue bundles two work items with different dependency profiles. The situation is unchanged from the prior triage.

RHIDP-15321 — RHOAI Version Normalization (tasks 7.1–7.7) ✅ Unblocked

This work has no cross-connector dependencies and can start immediately. It covers implementing normalizeVersion(), populating the rhdh.io/ai-asset-version annotation, and handling edge cases (missing metadata, invalid version strings).

RHIDP-15317 — MCP Mirror Endpoint (tasks 1.1–1.20) 🚫 Blocked

This work remains blocked on the upstream MCP Registry entity provider tracked in #4068. That issue is still open with no comments or progress. The upstream community provider must exist before the productization layer can override its endpoint configuration for mirror support, zero-internet validation, and startup health checks.

Blocking dependency

• Implement upstream MCP Registry entity provider (RHIDP-15655 / RHDHPLAN-393) #4068 — Implement upstream MCP Registry entity provider (RHIDP-15655 / RHDHPLAN-393) — still open, no progress observed.

Downstream impact

Issues #4051 (TLS Hardening) and #4052 (Annotation Enrichment) also depend on or reference RHDHPLAN-393, so resolving this upstream dependency unblocks multiple items in the series.

Recommendation

The RHOAI version normalization work (RHIDP-15321, tasks 7.1–7.7) can proceed independently while #4068 is resolved. Tasks 1.1–1.20 should remain blocked until the upstream provider lands.

Blocked by:

• Implement upstream MCP Registry entity provider (RHIDP-15655 / RHDHPLAN-393) #4068