@pipeworx/mcp-ai-briefing 0.1.1 → 0.1.3

package/README.md

@@ -2,7 +2,7 @@
 
 AI Briefing MCP — Keep AI models current on industry developments
 
-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 1786+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
 
 ## Tools
 
@@ -61,7 +61,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 1786+ 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-ai-briefing",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "AI Briefing MCP — Keep AI models current on industry developments",
   "type": "module",
   "main": "src/index.ts",
@@ -26,7 +26,7 @@
     "@cloudflare/workers-types": "^4.20260405.1"
   },
   "pipeworx": {
-    "sourceHash": "v1-c0263f801c7031df0a0e8af3598f3a990afeaa992c2b7b0ab7130e4b520c8608",
-    "sourceCommit": "60f04b68c347e970c6be94a53439d1364061fc06"
+    "sourceHash": "v1-53d142ed192e8732003a3dd64e3466c4efc3a6498d947ccc435d84475aa2bbca",
+    "sourceCommit": "25e83bad9a91f94df238b7910cd6c46a8143d26d"
   }
 }

package/server.json

@@ -3,7 +3,7 @@
   "name": "io.github.pipeworx-io/ai-briefing",
   "title": "Ai Briefing",
   "description": "AI Briefing MCP — Keep AI models current on industry developments",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "websiteUrl": "https://pipeworx.io/packs/ai-briefing",
   "repository": {
     "url": "https://github.com/pipeworx-io/mcp-ai-briefing",

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,
+      ),
+    );
   }
 }
 
@@ -678,6 +713,37 @@ async function querySupabase(path: string): Promise<unknown> {
   return res.json();
 }
 
+/**
+ * fleet #3041: 4 of 5 AI-lab blog feeds were 404/403 for an unknown period
+ * and get_ai_news kept returning a clean 200 with a plausible-looking item
+ * count — a dead source read exactly like a quiet news day. The scraper
+ * (workers/ai-briefing-scraper) now writes one row per source to
+ * `ai_scrape_health` every run; this surfaces it in the response itself so
+ * a caller never has to take "no OpenAI/Anthropic/Meta/Mistral items" on
+ * faith. Failure here (table missing, query error) returns null rather
+ * than throwing — a health-surface outage must never break the main feed.
+ */
+async function getSourceHealth(): Promise<{ partial: boolean; failed_sources: string[]; checked_at: string | null } | null> {
+  try {
+    const rows = (await querySupabase(
+      `ai_scrape_health?select=source,ok,http_status,detail,checked_at&order=checked_at.desc`,
+    )) as Array<Record<string, unknown>>;
+    if (!Array.isArray(rows) || rows.length === 0) return null;
+    const failed = rows.filter((r) => r.ok === false);
+    const newest = rows.reduce<string | null>((acc, r) => {
+      const c = r.checked_at as string | undefined;
+      return c && (!acc || c > acc) ? c : acc;
+    }, null);
+    return {
+      partial: failed.length > 0,
+      failed_sources: failed.map((r) => `${r.source}: HTTP ${r.http_status ?? 'n/a'} — ${r.detail}`),
+      checked_at: newest,
+    };
+  } catch {
+    return null;
+  }
+}
+
 const tools: McpToolExport['tools'] = [
   {
     name: 'get_briefing',
@@ -1066,15 +1132,34 @@ async function getAiNews(days: number, limit: number): Promise<unknown> {
   const newsCategories = ['model_release', 'claude_update', 'funding', 'acquisition', 'policy', 'benchmark', 'news', 'paper'];
   const catFilter = newsCategories.map((c) => `category.eq.${c}`).join(',');
 
-  const devs = await querySupabase(
-    `ai_developments?or=(${catFilter})&published_at=gte.${since}&order=published_at.desc&limit=${limit}`
-  ) as Array<Record<string, unknown>>;
+  const [devs, sources] = await Promise.all([
+    querySupabase(
+      `ai_developments?or=(${catFilter})&published_at=gte.${since}&order=published_at.desc&limit=${limit}`
+    ) as Promise<Array<Record<string, unknown>>>,
+    getSourceHealth(),
+  ]);
 
   return {
     feed: 'ai_news',
     period: `last ${days} days`,
     description: 'AI industry developments — models, funding, policy, research',
     total: devs.length,
+    // fleet #3041: a dead lab-blog feed used to read as "no news today" --
+    // this says whether the LAST scrape run actually reached every source.
+    // `sources` is omitted (not faked as healthy) when the health table
+    // could not be read, rather than claiming a status we do not have.
+    ...(sources
+      ? {
+          sources: {
+            partial: sources.partial,
+            note: sources.partial
+              ? `${sources.failed_sources.length} source(s) failed on the last scrape run -- counts above may undercount those sources, not reflect a quiet news day.`
+              : 'all tracked sources reached on the last scrape run.',
+            failed_sources: sources.failed_sources,
+            checked_at: sources.checked_at,
+          },
+        }
+      : {}),
     items: devs.map((d) => ({
       title: d.title,
       summary: d.summary,

package/src/server.ts

@@ -8,8 +8,9 @@ import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'
 import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js';
 import pack from './index.js';
 
+
 const server = new Server(
-  { name: '@pipeworx/mcp-ai-briefing', version: '0.1.1' },
+  { name: '@pipeworx/mcp-ai-briefing', version: '0.1.3' },
   { capabilities: { tools: {} } },
 );
 
@@ -24,7 +25,9 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
 server.setRequestHandler(CallToolRequestSchema, async (request) => {
   const { name, arguments: args } = request.params;
   try {
-    const result = await pack.callTool(name, (args ?? {}) as Record<string, unknown>);
+    const callArgs = { ...((args ?? {}) as Record<string, unknown>) };
+    
+    const result = await pack.callTool(name, callArgs);
     return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
   } catch (err) {
     return {