DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring
mcp-name: io.github.Aguantar/kafka-dataops-mcp A DataOps-focused Kafka MCP server with consumer lag diagnosis and broker health monitoring. Diagnosis logic is based on actual CDC pipeline operational experience. — Consumer group lag with incident-pattern diagnosis — Topic details with ISR/replication health checks — Cluster health: brokers, controller, under-replicated partitions — Topic catalog…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
mcp-name: io.github.Aguantar/kafka-dataops-mcp A DataOps-focused Kafka MCP server with consumer lag diagnosis and broker health monitoring. Diagnosis logic is based on actual CDC pipeline operational experience. ** — Consumer group lag with incident-pattern diagnosis — Topic details with ISR/replication health checks — Cluster health: brokers, controller, under-replicated partitions — Topic catalog with built-in descriptions The diagnosis logic is not generic — it's based on actual operational…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.