Skip to main content
Glama

Related Servers

Alternatives to kuma

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables 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.
    5
    MIT
  • F
    license
    A
    quality
    B
    maintenance
    Enables 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
    -
  • A
    license
    Not graded
    quality
    F
    maintenance
    Provides a zero-install security baseline for AI coding agents, with tools to retrieve curated security rules and check actions against them for self-correction.
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides 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 npm
    43 PyPI
    MIT

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation2/5

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.

Naming Consistency3/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessResponsive