Model Context Protocol moderate risk

JS

YepCode MCP Server enables AI platforms to run code and manage YepCode resources via the Model Context Protocol, offering seamless integration and control.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readwriteexecadmin

Quickstart

Config

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/sk-c2E....RD/sse"
    }
  }
}

Exposed MCP Tools (9)

high

run_code

Executes code within the YepCode environment.

Allows arbitrary code execution, which can be exploited if not properly sandboxed or validated.

high

set_env_var

Sets an environment variable in the YepCode workspace.

Modifying environment variables can impact the behavior of running processes and potentially expose secrets.

high

remove_env_var

Removes an environment variable from the YepCode workspace.

Removing environment variables can disrupt running processes and cause unexpected behavior.

safe

list_files

Lists files in the YepCode storage.

Read-only operation that does not modify any data.

moderate

upload_file

Uploads a file to YepCode storage.

Writing to storage, potentially overwriting existing files.

safe

download_file

Downloads a file from YepCode storage.

Read-only operation; retrieves file content.

critical

delete_file

Deletes a file from YepCode storage.

Deletes files, leading to potential data loss.

moderate

<process_slug>

Executes a specific YepCode process.

The danger level depends on the actions performed by the process itself; can range from safe to critical.

safe

get_processes

Lists processes with optional filters.

Read-only operation that does not modify any data.

Safety Assessment

YepCode MCP Server offers a balance between functionality and security. It's safe when used with carefully defined process tags and restricted tool selection. Risks arise when granting broad access or allowing uncontrolled code execution.

Code execution occurs in YepCode's sandboxed environment.
API key authentication is required.
Tool selection can be controlled via environment variables.
Sensitive environment variables can be masked in logs.

Exposes code execution capability, which can be risky if not properly controlled.
Allows modification of environment variables and storage.
Process execution can trigger potentially harmful actions.
Improperly configured process tags can expose unintended processes as tools.