crawlforge-mcp-server 5.5.7 → 5.5.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "crawlforge-mcp-server",
-  "version": "5.5.7",
+  "version": "5.5.8",
   "mcpName": "io.github.mysleekdesigns/crawlforge-mcp-server",
   "description": "CrawlForge MCP Server - Professional Model Context Protocol server with 29 web scraping, crawling, deep-research, and autonomous-extraction tools. Returns clean Markdown and structured JSON for Claude, Cursor, and any MCP client. Defaults to local Ollama for LLM extraction (no API key needed); OpenAI/Anthropic available as opt-in. Includes a unified multi-format scrape tool, an autonomous agent, pre-built site templates, and Camoufox stealth browsing.",
   "main": "server.js",

package/server.js

@@ -105,7 +105,7 @@ const taskStore = createTaskStore({ logger });
 // Create the server
 const server = new McpServer({
   name: "crawlforge",
-  version: "5.5.7",
+  version: "5.5.8",
   description: "Production-ready MCP server with 29 web scraping, crawling, and content processing tools. Features MCP Resources (crawlforge://), Prompts, Sampling fallback, Elicitation, stealth browsing, deep research, structured extraction, embedded JavaScript state extraction, real Google SERP rank tracking, Reddit search via community archives, change tracking, local-LLM extraction via Ollama, unified multi-format scrape, and autonomous agent tool.",
   homepage: "https://www.crawlforge.dev",
   icon: "https://www.crawlforge.dev/icon.png",

package/src/tools/tracking/trackChanges/notifier.js

@@ -10,6 +10,18 @@ import { identityHeaders } from '../../../utils/fetchIdentity.js';
 // these two senders were the only ones left calling bare fetch.
 import { safeFetch } from '../../../utils/ssrfGuard.js';
 
+/**
+ * How long to wait on a notification endpoint before giving up.
+ *
+ * fetch/undici has no `timeout` RequestInit option, so without an explicit
+ * signal a webhook target that accepts the connection and then never answers
+ * holds the request open forever. These sends are awaited together in
+ * `sendNotifications`, so one unresponsive endpoint stalls every notification
+ * for that change, not just its own. `WebhookDispatcher` hit exactly this and
+ * documents it; 30s matches the default it settled on.
+ */
+const NOTIFY_TIMEOUT_MS = Number(process.env.TRACK_CHANGES_NOTIFY_TIMEOUT_MS) || 30000;
+
 /**
  * Send all enabled notifications for a detected change.
  * @param {string} url
@@ -52,7 +64,8 @@ export async function sendWebhookNotification(url, changeResult, webhookConfig,
         ...identityHeaders({ role: 'webhook' }),
         ...webhookConfig.headers
       },
-      body: JSON.stringify(payload)
+      body: JSON.stringify(payload),
+      signal: AbortSignal.timeout(NOTIFY_TIMEOUT_MS)
     });
 
     if (!response.ok) {
@@ -97,7 +110,8 @@ export async function sendSlackNotification(url, changeResult, slackConfig, emit
     const response = await safeFetch(slackConfig.webhookUrl, {
       method: 'POST',
       headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify(payload)
+      body: JSON.stringify(payload),
+      signal: AbortSignal.timeout(NOTIFY_TIMEOUT_MS)
     });
 
     if (!response.ok) {