Skip to main content
Glama

Related Servers

Alternatives to cmdxray

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server that vets LLM-emitted shell commands BEFORE execution — detects rm -rf nested deep in chains, package-manager glob removal (apt remove 'nvidia'), dd/mkfs filesystem destruction, chmod 777 / chown -R privilege blast, network-exfil via curl | bash, chained shutdown/reboot, git destructive ops. 30 detection rules across 8 families. Sub-second, local, free, MCP-native.
      3
      58 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to assess the risk of shell commands before execution, providing a probability of harm and a suggested action (auto, warn, or confirm).
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      Local guardrail proxy for AI coding agents. Wraps any MCP server (stdio or HTTP/SSE) and blocks destructive tool calls before they execute, with TOFU catalog pinning against rug pulls and tool-poisoning/result-injection scanning. Single Rust binary, Apache-2.0.
      14
      11
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to score, inspect, and gate tool calls before they execute, resolving shell commands the way a shell would in order to block destructive actions and detect multi-step attack sequences. It also redacts credentials and PII in either direction, requires signed single-use approval tokens for high-impact actions, and keeps a tamper-evident audit trail.
      6
      0
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation3/5

    lint_script and check_command_safety overlap substantially because both safety-scan shell content using the same danger engine; their main differentiator is whole-script vs single-command scope, which descriptions do clarify. explain_command is clearly distinct.

    Naming Consistency5/5

    All three tools follow a consistent lowercase verb_noun snake_case pattern: lint_script, check_command_safety, explain_command. No mixed conventions or vague placeholder names exist.

    Tool Count5/5

    Three tools is small but well-scoped for a focused shell safety/explanation utility. Each tool serves a distinct role: whole-script linting, single-command guarding, and command explanation.

    Completeness5/5

    For the stated domain of shell command safety, the surface covers the necessary workflows: pre-scanning scripts, checking individual commands before execution, and explaining commands. No obvious dead ends or critical missing operations are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive