@leadbay/mcp 0.35.0 → 0.35.2

package/CHANGELOG.md

@@ -1,5 +1,47 @@
 # Changelog — @leadbay/mcp
 
+## 0.35.2 — 2026-09-08
+
+A backend `bad_request` 400 is now `BAD_INPUT` (product#4085).
+
+**What happened.** On 8 Sep an unattended routine on the hosted server called
+`leadbay_research_lead_by_id` twenty times in 39 seconds with the first block
+of each lead UUID (`/lenses/48110/leads/5585c198`, …). The backend rejected
+every call in ~30 ms with `400 {"error":{"code":"bad_request","message":"bad
+'leadId' parameter"}}`. `client.ts` `mapErrorResponse` filed that under the
+`API_ERROR` catch-all, whose hint reads "Try again or check the Leadbay API
+status". The agent did what it was told. The same pattern ran on 31 Aug.
+
+**Change.** A 400 whose body carries the backend's `bad_request` code (a path
+or query parameter that failed to parse, a body that failed to deserialize) is
+`BAD_INPUT`, with the backend message verbatim and a hint that the call fails
+identically on retry and that ids are the full values Leadbay returned. Other
+400 codes (`duplicate`, `unpaid_invoice`, `not_allowed`, …) are domain answers
+and stay `API_ERROR`. `leadbay_research_lead_by_id`'s `leadId` schema
+description now says the id is the full 36-character UUID from
+`leadbay_pull_leads` `items[].id`, never shortened. No template change.
+
+## 0.35.1 — 2026-09-08
+
+Release-pipeline only. No source change, no behaviour change: `packages/core`
+and `packages/mcp` are byte-identical to 0.35.0. This version exists because
+the MCP Registry can only be reached by a tag push, and the two `release.yml`
+bugs fixed in #208 had to ship before a tag could carry it.
+
+**What was broken.** 0.35.0 published to npm and then the workflow died
+before creating the GitHub Release: the release-notes pipeline ended in
+`head -60` under `set -euo pipefail`, the 0.35.0 changelog section is 115
+lines, so `head` closed the pipe, GNU sed failed its final flush and the step
+exited 4. No Release meant no `.dxt`/`.mcpb`, and `Publish to MCP Registry`
+was skipped for `needs:`-ing the job that failed. Separately, on 0.34.1 the
+registry job did run and the registry refused it — it re-checks npm itself and
+got a 404 for a version published seconds earlier. Between the two, the
+directory listing sat at 0.34.0 and the desktop bundle at 0.34.x while npm and
+the hosted server were on 0.35.0.
+
+0.35.0's Release and its four assets were created by hand once #208 landed;
+this release is what carries the fix through the pipeline itself.
+
 ## 0.35.0 — 2026-09-02
 
 The MCP no longer keeps any record of the jobs it starts (product#4005,

package/dist/bin.js

@@ -661,6 +661,9 @@ var init_client = __esm({
         if (status === 404) {
           return this.makeError("NOT_FOUND", parsed?.message || parsed?.error?.message || "Resource not found", "Verify the ID is correct", endpoint, null, status);
         }
+        if (status === 400 && parsed?.error?.code === "bad_request") {
+          return this.makeError("BAD_INPUT", parsed?.error?.message || parsed?.message || "Leadbay rejected the request as malformed", "Leadbay's input validation rejected this call, so the same call will fail the same way \u2014 do not retry it unchanged. Fix the parameter named in the message first; if it is an id, pass it exactly as Leadbay returned it, never shortened or reconstructed.", endpoint, null, status);
+        }
         return this.makeError("API_ERROR", parsed?.message || parsed?.error?.message || `API error (${status})`, "Try again or check the Leadbay API status", endpoint, null, status);
       }
       // /me cache (60s TTL). Separate from resolveOrgId() which still works for
@@ -14817,7 +14820,10 @@ var init_research_lead_by_id = __esm({
       inputSchema: {
         type: "object",
         properties: {
-          leadId: { type: "string", description: "Lead UUID (required)" },
+          leadId: {
+            type: "string",
+            description: "Full 36-character lead UUID exactly as returned in leadbay_pull_leads items[].id (never shortened)"
+          },
           lensId: {
             type: "number",
             description: "Lens id (escape hatch \u2014 normally omit; auto-resolves to the active lens)"
@@ -28045,7 +28051,7 @@ var OAUTH_BASE_URLS = {
     fr: "https://staging.api.leadbay.app"
   }
 };
-var VERSION = "0.35.0";
+var VERSION = "0.35.2";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
 

package/dist/http-server.js

@@ -3649,6 +3649,9 @@ var LeadbayClient = class _LeadbayClient {
     if (status === 404) {
       return this.makeError("NOT_FOUND", parsed?.message || parsed?.error?.message || "Resource not found", "Verify the ID is correct", endpoint, null, status);
     }
+    if (status === 400 && parsed?.error?.code === "bad_request") {
+      return this.makeError("BAD_INPUT", parsed?.error?.message || parsed?.message || "Leadbay rejected the request as malformed", "Leadbay's input validation rejected this call, so the same call will fail the same way \u2014 do not retry it unchanged. Fix the parameter named in the message first; if it is an id, pass it exactly as Leadbay returned it, never shortened or reconstructed.", endpoint, null, status);
+    }
     return this.makeError("API_ERROR", parsed?.message || parsed?.error?.message || `API error (${status})`, "Try again or check the Leadbay API status", endpoint, null, status);
   }
   // /me cache (60s TTL). Separate from resolveOrgId() which still works for
@@ -16962,7 +16965,10 @@ var researchLeadById = {
   inputSchema: {
     type: "object",
     properties: {
-      leadId: { type: "string", description: "Lead UUID (required)" },
+      leadId: {
+        type: "string",
+        description: "Full 36-character lead UUID exactly as returned in leadbay_pull_leads items[].id (never shortened)"
+      },
       lensId: {
         type: "number",
         description: "Lens id (escape hatch \u2014 normally omit; auto-resolves to the active lens)"
@@ -25410,7 +25416,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.35.0" : "0.0.0-dev";
+var VERSION = true ? "0.35.2" : "0.0.0-dev";
 var PORT = Number(process.env.PORT ?? 8080);
 var HOST = process.env.HOST ?? "0.0.0.0";
 var logger = {

package/dist/installer-electron.js

@@ -1805,7 +1805,7 @@ var init_installer_gui = __esm({
     init_install_dxt();
     init_install_shared();
     init_oauth();
-    VERSION = true ? "0.35.0" : "0.0.0-dev";
+    VERSION = true ? "0.35.2" : "0.0.0-dev";
     MESSAGES = {
       en: {
         installer: {

package/dist/installer-gui.js

@@ -1068,7 +1068,7 @@ async function oauthLogin(opts) {
 }
 
 // installer/installer-gui.ts
-var VERSION = true ? "0.35.0" : "0.0.0-dev";
+var VERSION = true ? "0.35.2" : "0.0.0-dev";
 var MESSAGES = {
   en: {
     installer: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leadbay/mcp",
-  "version": "0.35.0",
+  "version": "0.35.2",
   "mcpName": "io.github.leadbay/leadbay-mcp",
   "description": "Model Context Protocol (MCP) server for Leadbay — AI lead discovery, qualification, and enrichment for Claude Desktop, Cursor, and Claude Code.",
   "type": "module",