Kafka Sentinel

io.github.sanjay-amu/kafka-sentinel-mcpv0.1.2Other

Read-only Kafka observability MCP server: cluster health, consumer lag, and replay-readiness.

The current version, v0.1.2, was published to the official MCP registry on 2026-07-23. It is distributed as kafka-sentinel-mcp on PyPI, filed under Other by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Kafka Sentinel in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

REVIEWstatus: PARTIALfresh until 2026-09-11 00:12 UTC

screened 2026-07-23tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions found”via static_description

Limits of this verdict

- Semantic screen only - the deterministic conformance probe has not run on this server
- Confidence is reported but not yet calibrated (v1)
- Screen reads the tool description, not the live behavior
- advisory
- registry description only no input schema
- screen model 8b
- Still current: the description we screened is unchanged, re-checked against the registry
- The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-04).

Contracts can change after screening, with no version bump. The gate pins Kafka Sentinel’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown

[Independent trust record for Kafka Sentinel](https://mcpindex.ai/server/io-github-sanjay-amu-kafka-sentinel-mcp) - screening verdict, registry provenance, and contract drift monitoring.

HTML

<a href="https://mcpindex.ai/server/io-github-sanjay-amu-kafka-sentinel-mcp">Independent trust record for Kafka Sentinel</a> - screening verdict, registry provenance, and contract drift monitoring.

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown

[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-sanjay-amu-kafka-sentinel-mcp)](https://mcpindex.ai/server/io-github-sanjay-amu-kafka-sentinel-mcp)

HTML

<a href="https://mcpindex.ai/server/io-github-sanjay-amu-kafka-sentinel-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-sanjay-amu-kafka-sentinel-mcp" alt="mcpindex verdict" height="20" /></a>

Environment variables

KAFKA_BOOTSTRAP

required

Kafka bootstrap servers, e.g. broker1:9092,broker2:9092

KAFKA_SECURITY_PROTOCOL

librdkafka security.protocol, e.g. SASL_SSL

KAFKA_SASL_MECHANISM

librdkafka sasl.mechanism, e.g. PLAIN or SCRAM-SHA-512

KAFKA_SASL_USERNAME

SASL username

KAFKA_SASL_PASSWORD

secret

SASL password

KAFKA_SSL_CA_LOCATION

Path to CA certificate for SSL

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Other

AgentRoam

ai.agentroam/agentroam

Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.

Authoryze

ai.authoryze/authoryze

Give your AI agent a spending limit: approval controls and single-use virtual cards.

io.github.sanjaysgk/can-immune

Query CAN-IMMUNE: cancer neoantigen mutations, peptides, cell lines, MHC-I binding. Read-only.

Install this server

Claude Desktop (uvx)

{
  "mcpServers": {
    "kafka-sentinel-mcp": {
      "command": "uvx",
      "args": [
        "--",
        "kafka-sentinel-mcp"
      ],
      "env": {
        "KAFKA_BOOTSTRAP": "<kafka_bootstrap>",
        "KAFKA_SECURITY_PROTOCOL": "<kafka_security_protocol>",
        "KAFKA_SASL_MECHANISM": "<kafka_sasl_mechanism>",
        "KAFKA_SASL_USERNAME": "<kafka_sasl_username>",
        "KAFKA_SASL_PASSWORD": "<your-kafka_sasl_password>",
        "KAFKA_SSL_CA_LOCATION": "<kafka_ssl_ca_location>"
      }
    }
  }
}

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/io-github-sanjay-amu-kafka-sentinel-mcp

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v0.1.2
category: Other
verdict expires: 2026-09-11
quality: 84 / 100
operator: sanjay-amu

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 965,260). Verify it yourself.

Links

Repository →