Blinkbox MCP Server

What the code does

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

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    const content = await fs.readFile(args.path, args.encoding || "utf8");

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 filePath = path.join(LOCAL_DIR, key);

  const result = await redis.eval(renewScript, 1, key, ownerId, ttlSeconds);

    y: AGENT_SUB_DROP + depth * 130,

        child = spawn(command, args, { cwd, env, detached: true, stdio: ['pipe', 'pipe', 'pipe'] });

export const DOCKER_SOCKET         = process.env.DOCKER_SOCKET         || "/var/run/docker.sock";

  const res = await fetch(`https://api.telegram.org/bot${botToken}/${method}${params}`, {

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

claude mcp add blinkbox --transport http https://mcp.blinkbox.net/mcp

https://mcp.blinkbox.net/mcp

[mcp_servers.blinkbox]
url = "https://mcp.blinkbox.net/mcp"

{
  "mcpServers": {
    "blinkbox": {
      "url": "https://mcp.blinkbox.net/mcp"
    }
  }
}

{
  "servers": {
    "blinkbox": {
      "type": "http",
      "url": "https://mcp.blinkbox.net/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints