io.github.geored/lumino
Lumino MCP Server
Is the Lumino MCP server down? Yes. It has given no valid answer since 2026-10-17: install failed.
AI-powered SRE observability for Kubernetes/OpenShift with 40+ Tekton debugging tools
install failed down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
error: Failed to install entrypoints for `lumino-mcp-server`
- Run it
- uvx lumino-mcp-server@0.9.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/spre-sre/lumino-mcp-server
- Website
- https://github.com/spre-sre/lumino-mcp-server
- Registry
- active, updated 2026-01-24 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- MCPSentinel io.github.gentaArnezzi/mcpsentinel · crashed on start
- citable io.github.genzagents/citable · alive
- rentready io.github.genzagents/rentready · alive
- GeoLens io.github.geolens-io/geolens · alive
- MCP Modal Server io.github.george-bobby/mcp-modal · alive
- bhoonidhi-mcp io.github.geovicco-dev/bhoonidhi-mcp · alive
- io.github.gersonfreire/simpliq-server · crashed on start
- Ghidra BizHawk MCP io.github.getanirao/ghidra-bizhawk-mcp · crashed on start
Servers that mention lumino or observability or kubernetes.
- MaxiBestOf io.github.luminous8/maxibestof · needs auth
- AnomalyArmor ai.anomalyarmor/armor-mcp · needs auth
- ai.diezx/diezx · no DNS
- ai.getvda/llm-observability-orchestration · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain-community · newer protocol
- ai.getvda/llm-orchestration-observability-agent · newer protocol
- ai.noveum/noveum · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.