MCP Scorecard

Mission StatementGitHub
← All posts

Kubeshark: An 11,800-Star Kubernetes Tool Joins the Registry at 84

A battle-tested Kubernetes network traffic analyzer with 11,800 stars, 519 forks, and years of active development adds MCP support. Score 84 — the only new High Trust entry this batch, and the third established project to claim a top-tier position in two weeks.
io.github.kubeshark

Last week Scrapling entered at 92 — a 19,000-star scraping framework that became the registry's most trusted server. This week, the pattern repeats. io.github.kubeshark/mcp arrives with 11,810 stars, 519 forks, and a trust score of 84 — the only new High Trust entry in a batch of 232 servers.

What Kubeshark Is

Kubeshark is a real-time Kubernetes network traffic analyzer. Think Wireshark for Kubernetes. It captures and dissects all API traffic flowing through a cluster — HTTP/1.1, HTTP/2, gRPC, Redis, Kafka, AMQP, and DNS — without requiring sidecars, proxies, or instrumentation. It hooks into the Linux kernel via eBPF and taps traffic directly, then presents it through a web dashboard or CLI.

The project has been under active development since 2021. It serves a specific, painful use case: debugging microservice communication in production Kubernetes clusters where you can't reproduce the issue locally and log-based observability isn't cutting it. It shows you exactly what went over the wire — request and response bodies, headers, timing, TLS handshake details — in real time.

The MCP Integration

The MCP server wraps Kubeshark's analysis capabilities. An AI agent connected to a running Kubeshark instance can query live cluster traffic, filter by protocol or service, inspect specific API calls, and analyze communication patterns. The distribution format is notable: platform-specific MCPB binaries — precompiled bundles for macOS (ARM + x86), Linux (ARM + x86), and Windows. Five separate package entries, all stdio transport.

Version 53.1.0. Published March 6, 2026.

The Score Breakdown

CategoryScore
Provenance80/100
Maintenance79/100
Popularity91/100
Permissions90/100
Overall84

No flags. No secrets required. No credentials. Stdio only. Apache-2.0 license. Code of conduct present. 32 active commit weeks in the past year. 7 contributors. 15 releases in the past year. This is what a mature, well-maintained open source project looks like when it decides to support MCP.

The Pattern

Kubeshark is the third established project in two weeks to register an MCP server and immediately land in the top tier:

  • Scrapling (19.4k stars) — score 92
  • Kubeshark (11.8k stars) — score 84
  • edgartools (1.8k stars) — score 71

These are not MCP-native projects. They are proven tools with existing user bases that added MCP as an interface. Every time an established project makes this choice, it signals to other maintainers watching from the sidelines that the protocol is worth the integration effort. Two data points is anecdotal. Three is a trend.

Score: 84. No flags. Apache-2.0.

Sources: Kubeshark — GitHub · Scorecard: io.github.kubeshark (score 84)

← Ten MCP Servers for Ham Radio: The Most Niche Suite in the RegistryRegistry Pulse: Past 3,100 Servers, Streamable-HTTP Takes Hold →