What is mcp-suite-maintenance?

A set of development instructions for maintaining a group of MCP servers, which let AI agents use connected services. It defines shared project structure, permission levels, security checks, testing, releases, and publishing.

Use it when adding or changing tools, modifying security or policy code, updating dependencies, preparing releases, or publishing the listed MCP servers.

It keeps changes consistent across related servers and helps prevent tools from exposing capabilities beyond the configured access level.

How dockndevai/mcp-kafka configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dockndevai/mcp-kafka. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dockndevai/mcp-kafka/main/.claude/skills/mcp-suite-maintenance/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/dockndevai/mcp-kafka

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dockndevai/mcp-kafka/mcp-suite-maintenance/github.svg)](https://agentmods.dev/skills/dockndevai/mcp-kafka/mcp-suite-maintenance)

Your own site

<a href="https://agentmods.dev/skills/dockndevai/mcp-kafka/mcp-suite-maintenance"><img src="https://agentmods.dev/badge/skills/dockndevai/mcp-kafka/mcp-suite-maintenance/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dockndevai/mcp-kafka/mcp-suite-maintenance"><img src="https://agentmods.dev/badge/skills/dockndevai/mcp-kafka/mcp-suite-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,650 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00112	$0.01650
Opus 5	$0.00056	$0.00825
Sonnet 5	$0.00022	$0.00330
Haiku 4.5	$0.00011	$0.00165

Measured 10d ago against content hash f5e81688a5ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mcp-suite-maintenance 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 10d 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.

Origin

This is a copy

100% identical to mcp-suite-maintenance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/mcp-suite-maintenance/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Maintaining the MCP server suite

These six TypeScript MCP servers share one architecture and one security philosophy: safe by default, least privilege, never leak secrets. This skill captures the invariants and the routine tasks so changes stay consistent and safe.

Shared architecture (every repo)

src/
  index.ts        # stdio entrypoint: load config → build server → connect
  server.ts       # registers ONLY tools whose capability ≤ access mode
  config.ts       # env → typed config (connection + security)
  security.ts     # PURE policy engine (SecurityPolicy). No I/O. Unit-tested.
  <domain>/client.ts  # thin wrapper over the real SDK/REST API
  tools/{read,write,admin}.ts  # tool defs tagged with a capability
test/             # vitest — always includes security.test.ts

Capabilities: every tool declares capability: "read" | "write" | "admin".
Access modes: read-only (0) → read-write (1) → admin (2). A tool is only registered when CAPABILITY_RANK[tool] <= MODE_RANK[mode]. Over-privileged tools are never advertised — this is the primary guarantee.
Guard at call time too: every handler calls policy.guard({ tool, capability, <resource>, destructive? }) before doing work. Defence in depth on top of registration.

Non-negotiable invariants (do NOT regress these)

Read-only means read-only. A tool tagged read must never mutate. If it can mutate, it is write or admin.
Destructive ops need a second opt-in. Deletes/drops require the mode and an explicit flag (*_ALLOW_DELETE, OCI_ALLOW_APPLY, K8S_ALLOW_EXEC, etc.). The most dangerous (k8s exec_in_pod) is not even registered without its flag.
Protected resources are read-only forever. System realms/namespaces/databases/internal topics can be read but never mutated, regardless of mode.
Secrets never reach the model. Redact before returning (see redact.ts in mcp-oci / mcp-debezium; reset_password never echoes; list_clients strips secrets; ClickHouse caps rows). Any new field that could carry a credential must be redacted.
Audit + dry-run apply to every write. guard() emits the audit line and returns { dryRun }; write handlers must honor dryRun by returning intent without calling the backend.
stdout belongs to MCP. All logs/audit/warnings go to stderr only. Never console.log to stdout.

Read the full file on GitHub · 84 lines

Changes

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.

10d ago First seen · 84 lines · 112 tokens per session scan A f5e81688a5ec

Subscribe to this mod's changes

mcp-suite-maintenance is a skill published in the GitHub repository dockndevai/mcp-kafka (1 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 1,650 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-suite-maintenance, differing in 0 lines, and is treated as a copy.

Backend and APIs LLM apache-kafka kafka mcp model-context-protocol observability

background-script-execution

What actually happens when you call snowexecutescript — the Scripted REST endpoint Serac auto-deploys on first use, the scheduled-job fallback, what scheduledjobpending means, and how to get output back when the call comes home empty.

serac-labs/serac · 54 tokens

csdm-modeling

Pick the right ServiceNow service class under the Common Service Data Model — business service, service offering, application service, business application — and point the CMDB tools at it without creating the records CSDM tells customers to migrate away from.

serac-labs/serac · 53 tokens

mcp-kafka: Skill for Claude Code