Model Context Protocol (MCP) server for Kubernetes and OpenShift
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 74%
Response Time: 2d
First Timer Success: 63%
containers/kubernetes-mcp-server has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in containers/kubernetes-mcp-server respond to incoming external pull requests in approximately 46.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.2 places containers/kubernetes-mcp-server in the A tier.
The external contributor pull request merge rate for containers/kubernetes-mcp-server is 74.1%, based on public PR activity from non-core contributors.
containers/kubernetes-mcp-server currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in containers/kubernetes-mcp-server.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/containers/kubernetes-mcp-server?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~30 hours (93% approval). Large PRs (>500 lines) take ~221 hours (33% approval). Keep your diff compact for rapid review.
As per title, our Build on macos-15-intel job is flaky. We should look into what is causing the failure(s) and make our tests handle those more gracefully
In #1179 we are trying to add evals for a project without any toolset yet. Currently this flow will pass argocd as a toolset when starting the server, which will fail since that toolset does not exist. The matrix approach should somehow allow for us to indicate whether or not a toolset needs to be enabled, or we just need to match a set of eval tasks to run In general, we want to be able to run evals without any toolset being enabled, as for many projects the core toolset will support their needs and we just want to show compatibility
Summary The nodes_log tool has two defects that make file-based node log queries fail against the kubelet's node-log endpoint (/api/v1/nodes/{name}/proxy/logs). Both exist on main today. They were surfaced while reviewing #419 (closing separately) and are independent of that PR. 1. The documented /var/log/... example double-prefixes the path The nodes_log tool description tells callers to query files like "/var/log/kubelet.log". The kubelet resolves a file query with SecureJoin(nodeLogDir, query), where nodeLogDir = "/var/log/". So /var/log/kubelet.log resolves to /var/log/var/log/kubelet.log and returns a 404. The correct form is a path relative to /var/log (and, because the kubelet classifies a query as a file only when it contains a slash, with a leading slash), e.g. /kubelet.log. 2. tailLines on a file query is rejected by the kubelet The kubelet's validate() rejects options on a file query: case len(n.Files) == 1 && n.options != (options{}): "cannot specify file with options", and
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to containers/kubernetes-mcp-server, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of containers/kubernetes-mcp-server acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.1% were successfully merged into the primary branch.
containers/kubernetes-mcp-server has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.2 places containers/kubernetes-mcp-server in the Welcoming tier.
The external pull request merge rate is 74.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, containers/kubernetes-mcp-server currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for containers/kubernetes-mcp-server are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.