Lumino

Created By
Georgy Georgievski4 months ago
AI/ML-powered diagnostic engine for SRE Observability on Konflux and OpenShift. It uses the Model Context Protocol (MCP) and 40+ tools to analyze logs, metrics, and traces, enabling automated RCA and predictive analysis.
Overview

What is Lumino?

Lumino is an AI/ML-powered diagnostic engine designed for Site Reliability Engineers (SREs) to enhance observability on Kubernetes and OpenShift environments. It utilizes the Model Context Protocol (MCP) and integrates over 40 tools to analyze logs, metrics, and traces, facilitating automated root cause analysis (RCA) and predictive analysis.

How to use Lumino?

To use Lumino, you can either provision it through Claude Code CLI by following a simple prompt or manually set it up by cloning the repository and installing dependencies. Once set up, you can interact with Lumino using natural language queries to analyze your Kubernetes clusters.

Key features of Lumino?

  • Real-time monitoring of cluster health and resources.
  • Automated root cause analysis for failed pipelines.
  • Predictive analytics to forecast resource bottlenecks.
  • Advanced log analysis with anomaly detection.
  • Simulation of configuration changes to assess impact before deployment.

Use cases of Lumino?

  1. Diagnosing complex failures in CI/CD pipelines.
  2. Predicting potential resource issues before they impact services.
  3. Analyzing logs for security compliance and certificate management.
  4. Monitoring and optimizing Kubernetes and OpenShift operations.

FAQ from Lumino?

  • Can Lumino be used with any Kubernetes cluster?
    Yes, Lumino is designed to work with any Kubernetes or OpenShift cluster that has the appropriate access permissions.

  • Is Lumino open-source?
    Yes, Lumino is open-source and available on GitHub under the Apache License 2.0.

  • What are the prerequisites for using Lumino?
    You need Python 3.10 or higher and a valid kubeconfig with read permissions for your Kubernetes cluster.

Server Config

{
  "mcpServers": {
    "lumino": {
      "type": "stdio",
      "command": "<ABSOLUTE_PATH_TO_LUMINO>/.venv/bin/python",
      "args": [
        "<ABSOLUTE_PATH_TO_LUMINO>/main.py"
      ],
      "env": {
        "PYTHONUNBUFFERED": "1"
      }
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
Georgy Georgievski
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 minutes ago