MetaGO Agent Harness MCP Server

What the code does

We read the source, 6 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

      'eval(', 'exec(', 'system(', 'rm -rf', 'del /f', 'format ', 'shutdown',

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const out = execSync(`${cmd} --help`, { encoding: 'utf8', timeout: 8000, stdio: 'pipe' });

      const filePath = path.join(this.enginePath, file.path);

        r = subprocess.run([exe, str(script)], capture_output=True, text=True,

        var fn = (new Function('return (' + s + ')'))();

      tbody.innerHTML = tools.map(t => {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add metago -- npx -y @metago-ai/mcp-server

{
  "mcpServers": {
    "metago": {
      "command": "npx",
      "args": [
        "-y",
        "@metago-ai/mcp-server"
      ]
    }
  }
}

[mcp_servers.metago]
command = "npx"
args = ["-y", "@metago-ai/mcp-server"]

{
  "mcpServers": {
    "metago": {
      "command": "npx",
      "args": [
        "-y",
        "@metago-ai/mcp-server"
      ]
    }
  }
}

{
  "servers": {
    "metago": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@metago-ai/mcp-server"
      ]
    }
  }
}