ShipASO MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · 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.

        subprocess.run(

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.

        subprocess.run(

  const endpoint = `https://api.telegram.org/bot${botToken}/sendMessage`;

        env = env or dict(os.environ)

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

claude mcp add shipaso --transport http https://api.shipaso.com/mcp

https://api.shipaso.com/mcp

[mcp_servers.shipaso]
url = "https://api.shipaso.com/mcp"

{
  "mcpServers": {
    "shipaso": {
      "url": "https://api.shipaso.com/mcp"
    }
  }
}

{
  "servers": {
    "shipaso": {
      "type": "http",
      "url": "https://api.shipaso.com/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints