mail-index MCP Server

What the code does

We read the source, 11 h ago · rules 3dff92dd89df

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.

    const child = spawn(process.execPath, [join(here, 'selfupdate.mjs')], {

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 child = spawn(process.execPath, [join(here, 'selfupdate.mjs')], {

    el.innerHTML = el.innerHTML.split(/<br\s*\/?>/i)

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 mail-index -- npx -y mail-index

{
  "mcpServers": {
    "mail-index": {
      "args": [
        "-y",
        "mail-index"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mail-index]
command = "npx"
args = ["-y", "mail-index"]

{
  "mcpServers": {
    "mail-index": {
      "args": [
        "-y",
        "mail-index"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mail-index": {
      "args": [
        "-y",
        "mail-index"
      ],
      "command": "npx"
    }
  }
}