Nibgate MCP Server

What the code does

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

            (bool ok, bytes memory reason) = implementation.delegatecall(initData);

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.

    execSync(`"${prismaCli}" generate --schema=${schemaPath} 2>&1`, { stdio: 'pipe', timeout: 30000, cwd: repoRoot });

          const webpPath = path.join(UPLOAD_DIR, webpName);

  app.innerHTML = items.map(function(item) {

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

claude mcp add nibgate --transport http https://api.nibgate.xyz/mcp

{
  "mcpServers": {
    "nibgate": {
      "url": "https://api.nibgate.xyz/mcp"
    }
  }
}

[mcp_servers.nibgate]
url = "https://api.nibgate.xyz/mcp"

{
  "mcpServers": {
    "nibgate": {
      "url": "https://api.nibgate.xyz/mcp"
    }
  }
}

{
  "mcpServers": {
    "nibgate": {
      "url": "https://api.nibgate.xyz/mcp"
    }
  }
}

Available tools 5

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

Endpoints