Lumino MCP Server

lumino-mcp-server PyPI v0.9.3

Published by spre-sre — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

An open source MCP server empowering SREs with intelligent observability, predictive analytics, and AI-driven automation across Kubernetes, OpenShift, and Tekton environments.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 35

Each tool and what it can reach — statically extracted from the published source.

  • adaptive_namespace_investigationno sensitive capability
  • advanced_event_analyticsno sensitive capability
  • analyze_failed_pipelineno sensitive capability
  • analyze_logsno sensitive capability
  • analyze_pod_logs_hybridno sensitive capability
  • automated_triage_rca_report_generatorno sensitive capability
  • check_cluster_certificate_healthno sensitive capability
  • check_resource_constraintsno sensitive capability
  • ci_cd_performance_baselining_toolno sensitive capability
  • conservative_namespace_overviewno sensitive capability
Show 25 more tools ↓
  • detect_anomaliesno sensitive capability
  • detect_log_anomaliesno sensitive capability
  • find_pipelineno sensitive capability
  • get_etcd_logsno sensitive capability
  • get_kubernetes_resourceno sensitive capability
  • get_machine_config_pool_statusno sensitive capability
  • get_openshift_cluster_operator_statusno sensitive capability
  • get_pipelinerun_logsno sensitive capability
  • get_tekton_pipeline_runs_statusno sensitive capability
  • investigate_tls_certificate_issuesno sensitive capability
  • list_namespacesno sensitive capability
  • list_pipelinerunsno sensitive capability
  • list_pods_in_namespaceno sensitive capability
  • list_recent_pipeline_runsno sensitive capability
  • list_taskrunsno sensitive capability
  • live_system_topology_mapperno sensitive capability
  • pipeline_tracerno sensitive capability
  • progressive_event_analysisno sensitive capability
  • prometheus_queryno sensitive capability
  • search_resources_by_labelsno sensitive capability
  • semantic_log_searchno sensitive capability
  • smart_get_namespace_eventsno sensitive capability
  • smart_summarize_pod_logsno sensitive capability
  • stream_analyze_pod_logsno sensitive capability
  • what_if_scenario_simulatorno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.9.3 latest A 99/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/lumino-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/lumino-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/lumino-mcp-server"><img src="https://mcptrustchecker.com/registry/lumino-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/lumino-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan lumino-mcp-server --online --registry pypi

Use the free API → How scoring works

More in Analytics & Monitoring