@aborruso/ckan-mcp-server 0.4.132 → 0.4.133

package/LOG.md

@@ -1,10 +1,29 @@
 # LOG
 
+## 2026-10-28
+
+### v0.4.133
+
+Ships #568. For callers: `ckan_find_portals` works again on the hosted Worker (it failed on every call since at least 2026-09-05); `ckan_status_show` on a site that is not a CKAN API now says so and points at `ckan_find_portals`, instead of telling the caller to call `ckan_status_show`; `open.toronto.ca` works as a server URL in every tool (routed to its CKAN host). Tests 616 passed. Smoke 16/17: same MQA outage as v0.4.132 (per-dataset `/api/mqa/cache/*/{id}` still not answering, `/global` 0.2 s), tagged with `SKIP_RELEASE_GATE=1` on the user's decision.
+
+### Telemetry errors: find_portals fixed on Workers, error messages logged, non-CKAN hints
+
+From the error analysis of `worker_events_flat.jsonl` (app errors are logged only since 2026-09-05: 754 of 3,752 calls, 537 of them invalid input from scanners).
+
+- `ckan_find_portals` failed on every Worker call (96/96 since 2026-09-05): it was the only tool calling axios directly, and axios's fetch adapter breaks on Workers ("The 'cache' field on 'RequestInitializerDict' is not implemented"). Now uses `safeFetch`, like MQA; SSRF checks on redirects come with it. Checked with `wrangler dev`: 945 portals, about 5 s (the datashades.info list is 22 MB).
+- The worker log line of a failed call now has `error_message` (first 200 chars, one line) and `error_kind` (`validation`, `not_allowed`, `timeout`, `upstream_http`, `unreachable`, `other`, `src/utils/error-telemetry.ts`); the archiver carries both into the flat file. The find_portals failure stayed hidden for weeks because the log only said `error`.
+- `ckan_status_show` on a site that is not the CKAN API (47% failure on real URLs: open.toronto.ca, open.ottawa.ca, data.europa.eu/data, ...) told the caller to call `ckan_status_show`. It now says the site may not run CKAN or keep the API on another host, and points at `ckan_find_portals`. `open.toronto.ca` is routed to its CKAN host `ckan0.cf.opendata.inter.prod-toronto.ca` via `portals.json`.
+- Tests 615 passed (+14, each new test fails without its fix), Python tests 5.
+
 ## 2026-10-27
 
+### Archiver: empty result lists for zero-result searches
+
+Manual archiver run on a scratchpad copy (7 live events): search fields reach `worker_events_flat.jsonl`, but a zero-result search came in with `result_ids`/`result_names` null, since the Observability API drops empty arrays from `source`. `flatten()` now restores `[]` whenever `result_count` is present, so "0 results" stays distinct from "not a search". Rechecked on a fresh copy: `zzqxkwvnonesiste` → `result_count` 0, lists `[]`. Tests in `tests/python/test_worker_telemetry_archiver.py` (stdlib `unittest`: zero count with omitted lists, non-empty lists, non-search event, field set); the zero-count case fails on the previous `flatten()`. They run in `update-telemetry.yml` before each archiver run (Greptile review).
+
 ### v0.4.132
 
-Ships #565: worker telemetry logs returned search results. Tests 601 passed. Smoke 16/17: the MQA case times out because data.europa.eu `/api/mqa/cache/datasets/{id}` (and its successor `/resources/{id}`) hang for every dataset id tried, while `/global`, `/countries`, `/catalogues/dati-gov-it` answer in 0.2 s; released anyway on the user's decision. The official spec (`openapi.yaml` 6.0.1-SNAPSHOT) marks `/datasets/{id}` deprecated, alias of `/resources/{id}`: switching is a separate change.
+Ships #565: worker telemetry logs returned search results. Tests 601 passed. Smoke 16/17: the MQA case times out because data.europa.eu `/api/mqa/cache/datasets/{id}` (and its successor `/resources/{id}`) hang for every dataset id tried, while `/global`, `/countries`, `/catalogues/dati-gov-it` answer in 0.2 s; released anyway on the user's decision. Live on npm (provenance), the MCP Registry (`isLatest`), the Worker (`/health` 0.4.132) and the GitHub release (DXT + skill attached). Observability API checked read-only: `result_ids` arrives as a list and `flatten()` maps it. The official spec (`openapi.yaml` 6.0.1-SNAPSHOT) marks `/datasets/{id}` deprecated, alias of `/resources/{id}`: switching is a separate change.
 
 ### Worker telemetry: returned search results
 

package/dist/index.js

@@ -96,6 +96,16 @@ var portals_default = {
         "http://open.canada.ca"
       ]
     },
+    {
+      id: "open-toronto",
+      name: "open.toronto.ca",
+      api_url: "https://ckan0.cf.opendata.inter.prod-toronto.ca",
+      api_url_aliases: [
+        "https://open.toronto.ca",
+        "http://open.toronto.ca"
+      ],
+      dataset_view_url: "https://open.toronto.ca/dataset/{name}/"
+    },
     {
       id: "data-gov-au",
       name: "data.gov.au",
@@ -3648,14 +3658,15 @@ Typical workflow: ckan_status_show (verify server is up) \u2192 ckan_package_sea
           structuredContent: cappedStructured(result)
         };
       } catch (error) {
-        const migrated = error instanceof CkanApiError && error.serverUrl && getPortalMigration(error.serverUrl);
-        const detail = formatCkanError(error, "ckan_status_show");
+        const migrated = (error instanceof CkanApiError || error instanceof CkanTransportError) && error.serverUrl && getPortalMigration(error.serverUrl);
+        if (migrated) {
+          return { content: [{ type: "text", text: formatCkanError(error, "ckan_status_show") }], isError: true };
+        }
+        const detail = error instanceof CkanApiError || error instanceof CkanTransportError ? `${error.message}
+\u2192 No CKAN API answered at this address. The site may be up but not run CKAN, or keep its CKAN API on another host. Use \`ckan_find_portals\` to look up the portal's CKAN API URL; retry later only if this address usually works.` : formatCkanError(error, "ckan_status_show");
         return {
-          content: [{
-            type: "text",
-            text: migrated ? detail : `Server appears to be offline or not a valid CKAN instance:
-${detail}`
-          }],
+          content: [{ type: "text", text: `Server appears to be offline or not a valid CKAN instance:
+${detail}` }],
           isError: true
         };
       }
@@ -5407,14 +5418,17 @@ ${error instanceof Error ? error.message : String(error)}`;
 
 // src/tools/portal-discovery.ts
 import { z as z11 } from "zod";
-import axios2 from "axios";
 var DATASHADES_URL = "https://datashades.info/api/portal/list";
 async function fetchPortals() {
-  const resp = await axios2.get(DATASHADES_URL, {
-    timeout: 15e3,
-    headers: { "User-Agent": "CKAN-MCP-Server/1.0" }
-  });
-  return resp.data.portals;
+  const resp = await safeFetch(DATASHADES_URL, {
+    headers: { "User-Agent": "CKAN-MCP-Server/1.0" },
+    signal: AbortSignal.timeout(15e3)
+  }, { httpsOnly: true });
+  if (!resp.ok) {
+    throw new Error(`datashades.info returned ${resp.status} ${resp.statusText}`);
+  }
+  const data = await resp.json();
+  return data.portals;
 }
 function deduplicateByHostname(portals) {
   const seen = /* @__PURE__ */ new Map();
@@ -6142,7 +6156,7 @@ var registerAllPrompts = (server) => {
 function createServer() {
   return new McpServer({
     name: "ckan-mcp-server",
-    version: "0.4.132"
+    version: "0.4.133"
   });
 }
 function registerAll(server) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aborruso/ckan-mcp-server",
-  "version": "0.4.132",
+  "version": "0.4.133",
   "mcpName": "io.github.aborruso/ckan-mcp-server",
   "description": "MCP server for interacting with CKAN open data portals",
   "repository": {