@pipeworx/mcp-ofgem 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -5,7 +5,7 @@ domestic price cap and what it is made of, wholesale gas and electricity prices,
5
5
  supplier market shares, switching, debt and customer service, returned as
6
6
  tabular rows rather than pictures.
7
7
 
8
- Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1679+ live data sources.
8
+ Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1683+ live data sources.
9
9
 
10
10
  ## Tools
11
11
 
@@ -99,7 +99,7 @@ directly, instead of just this one's:
99
99
  }
100
100
  ```
101
101
 
102
- Both URLs reach the same gateway and the same 1679+ data sources. The
102
+ Both URLs reach the same gateway and the same 1683+ data sources. The
103
103
  only difference is which pack's tools are listed **directly**; `ask_pipeworx`
104
104
  reaches all of them from either one.
105
105
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pipeworx/mcp-ofgem",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Ofgem energy data: the UK energy regulator's published statistics on the domestic price cap and what it is made of, wholesale gas and electricity prices, supplier market shares, switching, debt and customer service — as tabular rows, not pictures.",
5
5
  "type": "module",
6
6
  "main": "src/index.ts",
@@ -26,7 +26,7 @@
26
26
  "@cloudflare/workers-types": "^4.20260405.1"
27
27
  },
28
28
  "pipeworx": {
29
- "sourceHash": "v1-3592bdb363785e752b710bcb3fba567f1488291a6e8254bb6fde68deac19c800",
30
- "sourceCommit": "b0fb3c31386cf0256dcf1e2f1b3440435a87ec35"
29
+ "sourceHash": "v1-aa644e02da6333d8acf29d47a95e524cd7ecaded98b5cb975a306f81ff2c48fa",
30
+ "sourceCommit": "97740c6ee04c8acbfe7dddcacfde9e88ff2b9ca0"
31
31
  }
32
32
  }
package/server.json CHANGED
@@ -3,7 +3,7 @@
3
3
  "name": "io.github.pipeworx-io/ofgem",
4
4
  "title": "Ofgem",
5
5
  "description": "Ofgem energy data: the UK energy regulator's published statistics on the domestic price cap and…",
6
- "version": "0.1.0",
6
+ "version": "0.1.1",
7
7
  "websiteUrl": "https://pipeworx.io/packs/ofgem",
8
8
  "repository": {
9
9
  "url": "https://github.com/pipeworx-io/mcp-ofgem",
package/src/index.ts CHANGED
@@ -452,7 +452,42 @@ async function fetchWithTimeout(
452
452
  ),
453
453
  );
454
454
  }
455
- throw err;
455
+ // Fleet #2382. Everything that isn't a timeout/abort here is a genuine
456
+ // NETWORK-LEVEL failure — DNS resolution, connection refused, TLS handshake,
457
+ // Cloudflare's own "Network connection lost." — meaning `fetch()` itself
458
+ // threw and no HTTP response of any kind was ever received. Until this fix
459
+ // that raw exception was rethrown VERBATIM: a bare `TypeError: fetch failed`
460
+ // (or the Workers-runtime equivalent) names no upstream, carries no class
461
+ // token, and reads exactly like a defect in OUR code — because it says
462
+ // nothing about the call at all. It landed in `error`, the tier that means
463
+ // "Pipeworx has a defect", for every one of the (at the time of writing)
464
+ // ~470 packs that call this helper directly with no wrapper of their own.
465
+ //
466
+ // `dexscreener` hit this independently (fleet #1579) and fixed it with a
467
+ // bespoke per-pack try/catch around `fetchWithTimeout`. That fix is correct
468
+ // but only covers one pack; every other caller of this shared helper still
469
+ // leaked the raw exception. Moving the same fix HERE — the one place that
470
+ // already carries the timeout case — covers every pack that uses
471
+ // `fetchWithTimeout` without a wrapper, for free, and without widening
472
+ // `classifyToolError`'s regex list: the fix is giving the message a proper
473
+ // `upstream_down:` token at the point the two facts (no response was ever
474
+ // received, and which host we were trying to reach) are actually in hand,
475
+ // not teaching the classifier to guess from prose after the fact.
476
+ //
477
+ // Safe on the same grounds as the timeout branch above: no argument a
478
+ // caller passes can make `fetch()` itself throw a connection-level error,
479
+ // so this is always an availability failure, never a caller mistake. Same
480
+ // `markInternalOrigin` treatment — an origin we run that never answered is
481
+ // still ours, not a third party's outage.
482
+ const raw = err instanceof Error ? err.message : String(err);
483
+ throw new Error(
484
+ markInternalOrigin(
485
+ `upstream_down: could not reach ${name} at all (${raw.slice(0, 160)}). ` +
486
+ `No request reached ${name}, so this says NOTHING about whether the arguments you passed ` +
487
+ 'are valid — do not re-check them on the strength of this error. Retry shortly.',
488
+ url,
489
+ ),
490
+ );
456
491
  }
457
492
  }
458
493
 
package/src/server.ts CHANGED
@@ -9,7 +9,7 @@ import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprot
9
9
  import pack from './index.js';
10
10
 
11
11
  const server = new Server(
12
- { name: '@pipeworx/mcp-ofgem', version: '0.1.0' },
12
+ { name: '@pipeworx/mcp-ofgem', version: '0.1.1' },
13
13
  { capabilities: { tools: {} } },
14
14
  );
15
15