kuma
Related Servers
Alternatives to kuma
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents geometric spatial awareness of web page layouts using Playwright, enabling detection of visual occlusion, layout shifts, and spatial relationships.644 npmMIT
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to run shell commands, perform sandboxed file operations, and make HTTP requests through zero-trust guards that block command injection, path traversal, and SSRF while redacting secrets from inputs and outputs. Circuit breakers, per-session rate limits, and an append-only audit ledger prevent runaway loops, excessive token spend, and provide post-hoc traceability.5MIT
- FlicenseAqualityBmaintenanceEnables AI agents to safely interact with GitHub, query Postgres read-only, check deployment status, and search/read files within an allowlisted sandbox—all with dry-run writes and SQL/path safety gates.8-

Kernora Agent Securityofficial
AlicenseNot gradedqualityFmaintenanceProvides a zero-install security baseline for AI coding agents, with tools to retrieve curated security rules and check actions against them for self-correction.1Apache 2.0- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.5 npm8MIT
- AlicenseNot gradedqualityBmaintenanceProvides sandboxed code execution for AI agents with support for Python, JavaScript, and shell commands. Includes comprehensive safety features like destructive pattern blocking, timeout protection, and restricted file access for secure production use.10 npm43 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with 25 security analysis tools including vulnerability scanning, package hallucination detection, prompt injection firewall, and CI/CD integration.1MIT
TDQS
Scored across 6 tools
The three functional groups (context, memory, safety) are reasonably distinct from each other, but each one is duplicated as an identical twin with a byte-for-byte identical description (kuma_context vs kuma_kuma_context, etc.). An agent has no basis to choose between a tool and its clone, guaranteeing arbitrary misselection in half the available surface.
Names follow a readable kuma_verb/noun snake_case pattern, but the redundant 'kuma_kuma_' prefix on three tools breaks the convention and looks like an accidental double-registration rather than a deliberate scheme. Consistent enough to parse, inconsistent enough to mislead.
Six tools would be a fine scope for this workflow, but three of them are exact duplicates, leaving only three effective tools covering context, memory, and safety. The apparent count overstates the real surface, though three genuine umbrellas is acceptable for the stated purpose.
Each umbrella tool exposes a rich action set (init/research/history/map/impact, gotcha/decision/search, guard/verify/checkpoint/rollback), covering the session lifecycle from recall through record to verification and rollback. Coverage looks solid; the main gap is that the duplicate twins add no capability, only noise.