Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/geored/lumino-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/geored/lumino-mcp-server/lumino)<a href="https://agentmods.dev/mcp/geored/lumino-mcp-server/lumino"><img src="https://agentmods.dev/badge/mcp/geored/lumino-mcp-server/lumino/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/geored/lumino-mcp-server/lumino"><img src="https://agentmods.dev/badge/mcp/geored/lumino-mcp-server/lumino.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
lumino scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
"KUBECONFIG": "~/.kube/config" This is a copy
100% identical to lumino — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"lumino": {
"command": "uvx",
"args": [
"lumino-mcp-server"
],
"env": {
"KUBECONFIG": "~/.kube/config"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 11 lines scan C 2eff2e6cd8b9
lumino is an MCP server published in the GitHub repository geored/lumino-mcp-server (0 stars, last pushed 7mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it C with 1 finding (reaches for credential files). It is 100% identical to lumino, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
AWSPrice
MCP server "AWSPrice" as configured in spacehendrix/clauder. Runs locally from the awslabs.aws-pricing-mcp-server@latest Python package. Needs 3 environment variables to run.
terraform
MCP server "terraform" as configured in aws-samples/sample-agentic-chatbot-accelerator. Runs in Docker (hashicorp/terraform-mcp-server:0.5.2).
CloudflareLogpush
MCP server "CloudflareLogpush", hosted remotely at logs.mcp.cloudflare.com, as configured in spacehendrix/clauder.