Mengram MCP Server

What the code does

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

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.

            subprocess.run(["pbcopy"], input=post.encode(), check=True)

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.

    if hostname in ("localhost", "0.0.0.0", "metadata.google.internal") or hostname.endswith(".internal") or hostname.endswith(".local"):

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.

        r = subprocess.run(f"{command} --help", shell=True, capture_output=True,

        r = subprocess.run(f"{command} --help", shell=True, capture_output=True,

          const txtFiles = fs.readdirSync(p, { recursive: true })

                        if (markup) el.innerHTML = markup;

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 15 min ago.

claude mcp add mengram --transport http https://mengram.io/mcp

{
  "mcpServers": {
    "mengram": {
      "url": "https://mengram.io/mcp"
    }
  }
}

[mcp_servers.mengram]
url = "https://mengram.io/mcp"

{
  "mcpServers": {
    "mengram": {
      "url": "https://mengram.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "mengram": {
      "url": "https://mengram.io/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