@pipeworx/mcp-sciencebase 0.1.2 → 0.1.3

package/README.md

@@ -2,7 +2,7 @@
 
 USGS ScienceBase catalog MCP.
 
-Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1683+ live data sources.
+Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1684+ live data sources.
 
 ## Tools
 
@@ -56,7 +56,7 @@ directly, instead of just this one's:
 }
 ```
 
-Both URLs reach the same gateway and the same 1683+ data sources. The
+Both URLs reach the same gateway and the same 1684+ data sources. The
 only difference is which pack's tools are listed **directly**; `ask_pipeworx`
 reaches all of them from either one.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pipeworx/mcp-sciencebase",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "USGS ScienceBase catalog MCP.",
   "type": "module",
   "main": "src/index.ts",
@@ -26,7 +26,7 @@
     "@cloudflare/workers-types": "^4.20260405.1"
   },
   "pipeworx": {
-    "sourceHash": "v1-533583ef0345435f5faf58f916ac958f9e363b0528c84cf8152f6827d0710aff",
-    "sourceCommit": "6fe8fb3e01138dfc4ebe7d5c246503aab9278d06"
+    "sourceHash": "v1-b2e2f72f448fb7906515f7b7bdd0567372bcd833e6a8cac5c6cb9303c906689a",
+    "sourceCommit": "fb13c3bcac104b099040ae8d7d93cb800d570afb"
   }
 }

package/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.pipeworx-io/sciencebase",
   "title": "Sciencebase",
   "description": "USGS ScienceBase catalog MCP.",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "websiteUrl": "https://pipeworx.io/packs/sciencebase",
   "repository": {
     "url": "https://github.com/pipeworx-io/mcp-sciencebase",

package/src/index.ts

@@ -859,7 +859,21 @@ async function sbGet(path: string, params: Record<string, string>): Promise<unkn
     // A 200 that is not JSON is the catalog answering with something other than
     // its API — report the shape, never let it surface as a parse error.
     return {
-      __error: `ScienceBase returned HTTP ${res.status} with a non-JSON body (${body.slice(0, 120)})`,
+      // `upstream_down:` is a CLASS TOKEN the gateway strips and classifies on
+      // (error-class.ts). Without it this booked plain `error`, which means
+      // PIPEWORX BROKE — and a catalog answering HTML where it promises JSON is
+      // the upstream's fault, not ours.
+      //
+      // It also makes the two remaining failure paths tellable apart in
+      // telemetry, which is why it is worth the token rather than just better
+      // prose. Measured 2026-09-26: `get_item` showed 2 external `error` events
+      // (09-22, 09-25) and they were read as "the not-found fix did not land".
+      // They are not misses — a miss returns `found:false` above and books
+      // `user_error`, verified live. They are THIS branch. With blob5 content
+      // redacted there was no way to see that from the class alone, and the
+      // callers are in regions where USGS may challenge differently: three
+      // probes from here returned clean JSON, so it is not reproducible locally.
+      __error: `upstream_down: ScienceBase returned HTTP ${res.status} with a non-JSON body (${body.slice(0, 120)})`,
     };
   }
 }

package/src/server.ts

@@ -9,7 +9,7 @@ import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprot
 import pack from './index.js';
 
 const server = new Server(
-  { name: '@pipeworx/mcp-sciencebase', version: '0.1.2' },
+  { name: '@pipeworx/mcp-sciencebase', version: '0.1.3' },
   { capabilities: { tools: {} } },
 );