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/samarthpatel24/claude-log-analyzerWrote 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/samarthpatel24/claude-log-analyzer/k8s-analyzer)<a href="https://agentmods.dev/mcp/samarthpatel24/claude-log-analyzer/k8s-analyzer"><img src="https://agentmods.dev/badge/mcp/samarthpatel24/claude-log-analyzer/k8s-analyzer/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/samarthpatel24/claude-log-analyzer/k8s-analyzer"><img src="https://agentmods.dev/badge/mcp/samarthpatel24/claude-log-analyzer/k8s-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
k8s-analyzer scanned grade A with 0 findings 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"k8s-analyzer": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"claude-log-analyzer"
]
}
}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.
- 9d ago First seen · 11 lines scan A f7ffa05e41de
k8s-analyzer is an MCP server published in the GitHub repository samarthpatel24/claude-log-analyzer (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-kubernetes
Kubernetes monitoring & ops for AI agents — safe-by-default access modes and guards. Runs locally from the @dockndevai/mcp-kubernetes npm package. Needs 2 environment variables to run.
rancher-mcp-server
MCP server for Rancher API integration. Runs locally from the rancher-mcp-server Python package.
st-k8s
MCP server "st-k8s" as configured in bhf/st-k8s. Runs locally from the st-k8s npm package.
k8s-observability-mcp
MCP server "k8s-observability-mcp" as configured in martinimarcello00/k8s-observability-mcp. Runs locally from the k8s-observability-mcp Python package.
stockbit-mcp
Indonesian exchange (IDX) via your own Stockbit account: quotes, bandarmology, charts. Unofficial. Runs locally from the stockbit-mcp npm package. Needs 4 environment variables to run.
localkeep
Local memory banks you keep — a localhost Hub UI + MCP connector for Claude. You curate titled, dated memory banks on your machine; Claude recalls them via MCP. Runs locally from the localkeep Python package. Needs 2 environment variables to run.