@pipeworx/mcp-data360 0.1.1 → 0.1.3

package/README.md

@@ -2,7 +2,7 @@
 
 World Bank Data360 MCP — the World Bank's modern unified data platform.
 
-Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1679+ 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 1679+ 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-data360",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "World Bank Data360 MCP — the World Bank's modern unified data platform.",
   "type": "module",
   "main": "src/index.ts",
@@ -26,7 +26,7 @@
     "@cloudflare/workers-types": "^4.20260405.1"
   },
   "pipeworx": {
-    "sourceHash": "v1-9111b17a396691d0fd844ff83b3d1af903aebd79e12dbba249568b6663c4f4a8",
-    "sourceCommit": "839ab210d969ef7f822cd747ea516f6bb49e9231"
+    "sourceHash": "v1-65667b630bb15d46ce130f4a24495fed088134e0b2301b8e8f7e71ea0734d4c1",
+    "sourceCommit": "904686a205e7659f86731df3f45eb88b9333c5a0"
   }
 }

package/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.pipeworx-io/data360",
   "title": "Data360",
   "description": "World Bank Data360 MCP — the World Bank's modern unified data platform.",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "websiteUrl": "https://pipeworx.io/packs/data360",
   "repository": {
     "url": "https://github.com/pipeworx-io/mcp-data360",

package/src/index.ts

@@ -452,7 +452,42 @@ async function fetchWithTimeout(
         ),
       );
     }
-    throw err;
+    // Fleet #2382. Everything that isn't a timeout/abort here is a genuine
+    // NETWORK-LEVEL failure — DNS resolution, connection refused, TLS handshake,
+    // Cloudflare's own "Network connection lost." — meaning `fetch()` itself
+    // threw and no HTTP response of any kind was ever received. Until this fix
+    // that raw exception was rethrown VERBATIM: a bare `TypeError: fetch failed`
+    // (or the Workers-runtime equivalent) names no upstream, carries no class
+    // token, and reads exactly like a defect in OUR code — because it says
+    // nothing about the call at all. It landed in `error`, the tier that means
+    // "Pipeworx has a defect", for every one of the (at the time of writing)
+    // ~470 packs that call this helper directly with no wrapper of their own.
+    //
+    // `dexscreener` hit this independently (fleet #1579) and fixed it with a
+    // bespoke per-pack try/catch around `fetchWithTimeout`. That fix is correct
+    // but only covers one pack; every other caller of this shared helper still
+    // leaked the raw exception. Moving the same fix HERE — the one place that
+    // already carries the timeout case — covers every pack that uses
+    // `fetchWithTimeout` without a wrapper, for free, and without widening
+    // `classifyToolError`'s regex list: the fix is giving the message a proper
+    // `upstream_down:` token at the point the two facts (no response was ever
+    // received, and which host we were trying to reach) are actually in hand,
+    // not teaching the classifier to guess from prose after the fact.
+    //
+    // Safe on the same grounds as the timeout branch above: no argument a
+    // caller passes can make `fetch()` itself throw a connection-level error,
+    // so this is always an availability failure, never a caller mistake. Same
+    // `markInternalOrigin` treatment — an origin we run that never answered is
+    // still ours, not a third party's outage.
+    const raw = err instanceof Error ? err.message : String(err);
+    throw new Error(
+      markInternalOrigin(
+        `upstream_down: could not reach ${name} at all (${raw.slice(0, 160)}). ` +
+          `No request reached ${name}, so this says NOTHING about whether the arguments you passed ` +
+          'are valid — do not re-check them on the strength of this error. Retry shortly.',
+        url,
+      ),
+    );
   }
 }
 
@@ -761,7 +796,39 @@ async function callTool(name: string, args: Record<string, unknown>): Promise<un
       if (period) params.set('TIME_PERIOD', period);
       params.set('skip', String(numArg(args.skip, 0)));
       params.set('top', String(numArg(args.top, 100)));
-      return get(`/data?${params.toString()}`);
+      const res = await pwFetch(`${BASE}/data?${params.toString()}`, {
+        headers: { Accept: 'application/json', 'User-Agent': UA },
+      });
+      if (!res.ok) {
+        const text = await res.text();
+        // Data360 answers an unknown DATABASE_ID with 417 EA500001 "Data
+        // retrieval failed" -- the same body it sends on a real outage, so the
+        // body cannot tell them apart. Check the id against the database list
+        // and only call it not_found when it is genuinely absent (fleet #2497).
+        const dbId = params.get('DATABASE_ID')!;
+        const known = await databaseIds().catch(() => null);
+        if (known && !known.includes(dbId)) {
+          const near = known.find((k) => k.toLowerCase() === dbId.toLowerCase());
+          return {
+            error: 'not_found',
+            message: near
+              ? `Data360 has no database "${dbId}" -- ids are case-sensitive; did you mean "${near}"?`
+              : `Data360 has no database "${dbId}". Call data360_list_databases for valid DATABASE_IDs (e.g. "WB_WDI").`,
+            DATABASE_ID: dbId,
+          };
+        }
+        throw new Error(`Data360: ${res.status} ${text.slice(0, 200)}`);
+      }
+      const data = (await res.json()) as { count?: number; value?: unknown[] };
+      if ((data.count ?? data.value?.length ?? 0) === 0) {
+        // An unknown INDICATOR / REF_AREA pair is a 200 with zero rows, not an error.
+        return {
+          ...data,
+          empty_reason: 'no_match',
+          note: `No observations for INDICATOR "${params.get('INDICATOR')}" in ${params.get('DATABASE_ID')} for REF_AREA "${params.get('REF_AREA')}"${period ? ` in ${period}` : ''}. Check the code with data360_search_indicators (database_id: "${params.get('DATABASE_ID')}"), or drop TIME_PERIOD.`,
+        };
+      }
+      return data;
     }
 
     default:
@@ -779,10 +846,16 @@ async function searchPost(body: unknown): Promise<unknown> {
   return res.json();
 }
 
-async function get(path: string): Promise<unknown> {
-  const res = await pwFetch(`${BASE}${path}`, { headers: { Accept: 'application/json', 'User-Agent': UA } });
-  if (!res.ok) throw new Error(`Data360: ${res.status} ${await res.text().then((t) => t.slice(0, 200))}`);
-  return res.json();
+async function databaseIds(): Promise<string[]> {
+  const res = (await searchPost({
+    count: true,
+    search: '*',
+    top: 0,
+    facets: ['series_description/database_id,count:1000'],
+  })) as any;
+  const ids: Array<{ value: string }> = res?.['@search.facets']?.['series_description/database_id'] ?? [];
+  if (ids.length === 0) throw new Error('Data360 database list came back empty');
+  return ids.map((d) => d.value);
 }
 
 function reqStr(args: Record<string, unknown>, key: string, example: string): string {

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-data360', version: '0.1.1' },
+  { name: '@pipeworx/mcp-data360', version: '0.1.3' },
   { capabilities: { tools: {} } },
 );