Lift Glama Maintenance (B->A) and complete server profile (83%->100%)

[ajdelaguila]

Summary

Two Glama signals below full marks are repo-hygiene, not code:

• Maintenance: B — dragged solely by "0 of 37 issues responded to in the last 6 months." Everything else is green: 102 commits in 12 weeks, CI passing, last stable release 2026-07-08, no vulnerability alerts, no code-scanning findings.
• Profile completion: 83% — two gaps: "No related servers" and "No recent usage."

Score page: https://glama.ai/mcp/servers/knaisoma/data-olympus/score

Actions

• Issue responsiveness (Maintenance lever): triage and respond to the open issue backlog, then keep a light cadence so Glama observes maintainer responses. This is the only red input to the Maintenance grade.
• Related servers: add a relatedServers list to glama.json (currently only declares maintainers). Candidates from the Related panel: knowledge-mcp, en-quire, md-graph, obsidian-kb. Clears "No related servers" and improves discoverability.
• Seed usage: exercise the server via Glama's "Try in Browser" so "No recent usage" clears (usage tracking window is 30 days).
• Record the outcome in docs/glama.md (the score-maintenance notes doc).

Related

• Research: publish MCP server metadata for discovery and catalog ingestion #111 (publish MCP server metadata for discovery and catalog ingestion) — the relatedServers / metadata work here is a concrete Glama-scoped slice of that.

Acceptance

• Maintenance grade A and profile completion 100% on the next Glama sync.

[ajdelaguila]

Maintainer triage: active in feature/kna-141. The branch adds related server metadata and documents the maintenance profile actions. The remaining confirmation happens after merge: trigger a Glama rescan and seed usage through Try in Browser.