Skip to main content
Glama
YYDW-1211

safe-agent-mcp

by YYDW-1211
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to safe-agent-mcp

No user-submitted related servers found.

    Related Servers

    • dsh-harness-mcp-server

      chushixixin
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes DeepSeek Harness agent capabilities as an MCP server, letting any MCP client drive Harness to execute real coding tasks with structured results, context isolation, and parallel execution.
      92 npm
      12
      MIT

    • hermes-dsh-bridge

      Emilia-awa
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables external MCP clients to drive DeepSeek Harness agents for real coding tasks, providing tools for task execution and queueing, session management, sandboxed file access, preset switching, and usage statistics.
      464 npm
      4
      GPL 3.0
    • terminal-toolkit-mcp by camel-ai

      terminal-toolkit-mcpofficial

      camel-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients to execute shell commands safely through the MCP protocol, with features like session management, safe mode, and process control.
      1
      Apache 2.0

    • opencode-mcp-bridge

      nmt3325
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes opencode's coding agent and shell as MCP tools, enabling MCP-only AI clients to execute shell commands, manage files, and run agent sessions with async job handling.
      23 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The name 'run_command' clearly describes its function, eliminating any ambiguity.

    Naming Consistency5/5

    The single tool follows a consistent verb_noun pattern ('run_command'). There are no other tools to create inconsistency, so the naming is perfectly consistent.

    Tool Count3/5

    The server has only one tool, which feels thin for a typical tool set. While it may cover the core purpose of safe command execution, the surface is minimal and could benefit from additional related tools.

    Completeness5/5

    The server's stated purpose is to execute shell commands in a sandbox, and 'run_command' fully covers this operation by returning stdout, stderr, and exit code. No obvious gaps exist for the intended scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources