@pipeworx/mcp-earthscope-fdsn 0.1.0

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/src/index.ts ADDED
@@ -0,0 +1,1035 @@
1
+ interface McpToolDefinition {
2
+ name: string;
3
+ description: string;
4
+ /** Human-facing one-liner (fleet #1967). Optional; consumers fall back to
5
+ * description. Kept in step with shared/src/types.ts — scripts/lib/
6
+ * check-inlined-types.mjs reports drift at publish time. */
7
+ summary?: string;
8
+ inputSchema: {
9
+ type: 'object';
10
+ properties: Record<string, unknown>;
11
+ required?: string[];
12
+ anyOf?: Array<{ required: string[] }>;
13
+ oneOf?: Array<{ required: string[] }>;
14
+ allOf?: Array<{ required: string[] }>;
15
+ };
16
+ outputSchema?: Record<string, unknown>;
17
+ }
18
+
19
+ interface McpToolExport {
20
+ tools: McpToolDefinition[];
21
+ callTool: (name: string, args: Record<string, unknown>) => Promise<unknown>;
22
+ meter?: { credits: number };
23
+ cost?: Record<string, unknown>;
24
+ provider?: string;
25
+ }
26
+
27
+ /**
28
+ * Was this failure OUR OWN web service? — the other half of `internal-db-class.ts`.
29
+ *
30
+ * fleet #1089 pulled failures from our own Postgres out of `upstream_down` by
31
+ * keying on the SQLSTATE inside PostgREST's four-key error envelope. That
32
+ * covered the majority and structurally could not cover the rest: the rest
33
+ * never reach Postgres, so they carry no SQLSTATE. What was left, measured over
34
+ * the 24h to 2026-09-02T15:00Z (fleet #1096):
35
+ *
36
+ * 5 pipeworx-catalog get_pack_tools Pipeworx catalog error: 522 — error code: 522
37
+ * 3 fleet fleet_list_open … upstream_down: Fleet task queue did not respond within 25s
38
+ *
39
+ * 521/522/523/526 are Cloudflare saying its edge could not reach an ORIGIN, and
40
+ * in both of those rows the origin is ours — `gateway.pipeworx.io` for the
41
+ * catalog pack (it self-fetches when the gateway hasn't injected a manifest),
42
+ * our own Supabase for fleet. There is no third party anywhere in either call.
43
+ * Same defect as #1089: our own outage filed under `upstream_down`, the one
44
+ * class that means "the source is unreachable and there is nothing for us to
45
+ * fix", which is why the problem-tools triage skips it.
46
+ *
47
+ * WHY NOT A WORDING RULE. The obvious fix is to match `fleet db error:` and
48
+ * `Pipeworx catalog error:` in classifyToolError. Each is emitted from exactly
49
+ * one site today, so it would work today. It would also rot the first time
50
+ * somebody rewords a label — silently, and in the direction of hiding our own
51
+ * outage, which is worse than the bug being fixed. Every prose rule in
52
+ * error-class.ts has needed widening as packs invented new wording (#409/#450/
53
+ * #584); that history is most of that file's comment budget.
54
+ *
55
+ * WHAT THIS KEYS ON INSTEAD: **the host the call actually reached.** A URL's
56
+ * hostname is a fact about the call, not a guess about its prose. Two
57
+ * consequences that a pack-level flag could not give us, and the reason the
58
+ * flag was rejected:
59
+ *
60
+ * - It describes the CALL, not the pack. `govcon-intel` fans out to our own
61
+ * Supabase AND to genuine third parties; `court-listener` holds our cache
62
+ * in Supabase and fetches courtlistener.com. An `internallyHosted: true` on
63
+ * either pack would relabel a real third-party outage as ours — inventing
64
+ * work, which is the same class of error in the opposite direction.
65
+ * - It covers every future internal pack for free, instead of one declared
66
+ * slug at a time.
67
+ *
68
+ * WHY IT SURVIVES A REWORD. The marker below is not matched as a literal by two
69
+ * separate files. `markInternalOrigin()` writes it and `internalHostMetricsClass()`
70
+ * reads it, both from the single exported `INTERNAL_ORIGIN_MARKER` constant in
71
+ * this module — so changing the wording changes both sides in the same edit and
72
+ * cannot desynchronise them. The pack's own label (`fleet db error:`,
73
+ * `Pipeworx catalog error:`) is not read at all: reword it freely, the class is
74
+ * unaffected. That is the property `stripClassPrefix` lacked when it drifted
75
+ * from its own classifier three times and needed a CI gate to hold them
76
+ * together.
77
+ *
78
+ * WHERE THE 5xx TEST LIVES. `markInternalOrigin` is called from the places that
79
+ * hold the real `Response` — `httpError`/`httpErrorMessage` and the timeout
80
+ * branch of `fetchWithTimeout` in `shared/src/http.ts` — so "is this an
81
+ * availability failure" is decided from the actual status code, never re-derived
82
+ * by scraping a number out of a sentence. A 404 from our own registry for a slug
83
+ * that does not exist is a caller's bad argument and is deliberately NOT marked.
84
+ */
85
+
86
+ /**
87
+ * OUR OWN web service was unreachable — not an upstream, and never `upstream_down`.
88
+ *
89
+ * ONE value, not three, unlike `internal_db_*`. That split existed because a
90
+ * slow query, an exhausted pool and an unknown SQLSTATE have different owners
91
+ * and different fixes. Here there is only one story to tell — an origin we run
92
+ * did not answer the edge — and one owner. A bucket with no distinct owner per
93
+ * value is decoration; #724 is what happens when a class holds several
94
+ * situations, and inventing sub-values ahead of a reason to act on them
95
+ * differently is the same mistake with the sign flipped.
96
+ *
97
+ * METRICS ONLY, exactly like PLATFORM_KEY_ERROR_CLASS and the internal_db
98
+ * values. `classifyToolError` still answers `upstream_down` for the retry and
99
+ * hint paths, which only care whether retrying or a sibling tool might work —
100
+ * and it might. Nothing a caller sees or is charged changes here.
101
+ *
102
+ * READ SIDE: this value is in BROKEN_TOOL_CLASSES, FAULT_CLASSES and
103
+ * ALL_ERROR_CLASSES in `workers/registry-api/src/index.ts`. All three, or it
104
+ * lands on no dashboard — fleet #721 is the warning, where the #719 split
105
+ * worked on the write side and was invisible for weeks.
106
+ */
107
+ const INTERNAL_SERVICE_UNREACHABLE_CLASS = 'internal_service_unreachable';
108
+
109
+ /**
110
+ * The token that carries "this origin is ours" from the call site to the
111
+ * classifier.
112
+ *
113
+ * Appended to the error message rather than attached to the Error object,
114
+ * because the object does not survive the trip: 275 packs return `{ error:
115
+ * string }` instead of throwing, the gateway reads `observedError` as a string,
116
+ * and the fleet pack rebuilds its error from a captured status + body across a
117
+ * retry loop. A property on an Error would be dropped by every one of those
118
+ * paths and the class would work in tests and vanish in production.
119
+ *
120
+ * WORDING IS LOAD-BEARING, same rule as labelAge's note in authority.ts. This
121
+ * string is appended to a pack's thrown Error message (shared/src/http.ts),
122
+ * and a thrown Error's message is exactly what the gateway hands back to the
123
+ * caller as `content[0].text` when nothing rewrites it (workers/gateway/src
124
+ * catches the throw and sets `rawResult.message = stripClassPrefix(error)`,
125
+ * which does not touch this suffix) — so the original wording,
126
+ * " [pipeworx-hosted origin — our own service, not a third party]", was not a
127
+ * theoretical leak: it shipped live on pipeworx-catalog's 522s, 7 times in 6
128
+ * hours on 2026-09-02 (see tests/golden-internal-service.test.ts), verbatim
129
+ * naming Pipeworx as the host. check:hosting-claims never caught it because it
130
+ * did not scan shared/ at all (task #2009). Reworded to describe the
131
+ * OBSERVATION (the origin did not answer) without a claim about who runs it —
132
+ * the identical fix labelAge got: drop the possessive, keep the fact.
133
+ */
134
+ const INTERNAL_ORIGIN_MARKER = ' [origin did not respond — retry before concluding the named source is down]';
135
+
136
+ /**
137
+ * Supabase's data plane for a project is `<ref>.supabase.co`, where the ref is
138
+ * exactly twenty lowercase letters (ours is `pqauisounztsgdgfkhke`).
139
+ *
140
+ * Matching the shape rather than listing the ref keeps this correct when we add
141
+ * a project — `supabaseEnv` on a pack entry already points some packs at a
142
+ * second one — while still excluding `status.supabase.co`, which is Supabase's
143
+ * own status page and emphatically not our database. Verified 2026-09-02 by
144
+ * `grep -rhoE '[a-z0-9-]+\.supabase\.(co|in)' mcps shared workers scripts`: the
145
+ * only real project ref anywhere in the tree is ours, the rest are doc
146
+ * placeholders (`abc`, `xyz`, `example`) which this pattern also excludes. Same
147
+ * finding internal-db-class.ts relies on for the PostgREST envelope being ours
148
+ * by construction.
149
+ */
150
+ const SUPABASE_PROJECT_HOST = /^[a-z]{20}\.supabase\.(co|in)$/;
151
+
152
+ /**
153
+ * Is this a host WE run?
154
+ *
155
+ * Deliberately NOT including `*.workers.dev`: plenty of third-party APIs are
156
+ * hosted on workers.dev, so the suffix says where something runs and not who
157
+ * owns it. Every internal call we actually make goes to a `pipeworx.io`
158
+ * hostname or to our Supabase project, both of which are ownership facts.
159
+ *
160
+ * `workers/gateway/src/provenance.ts`'s `OUR_HOSTS` answers the same
161
+ * question and DOES include `workers.dev` — a documented divergence
162
+ * (task #2051), not a bug to converge. That list decides what a response may
163
+ * cite as a data SOURCE, where a false negative (citing our own worker as an
164
+ * external source) is the hosting-disclosure leak this whole file exists to
165
+ * prevent, so it errs broad. This one decides who gets BLAMED for a 5xx in
166
+ * outage metrics read by on-call, where a false positive (crediting our own
167
+ * infra with a third party's outage) hides the real failure, so it errs
168
+ * narrow. Same suffix, opposite direction, because they are never called for
169
+ * the same reason.
170
+ *
171
+ * Returns false on anything unparseable rather than throwing — this runs inside
172
+ * an error path, and an error path that can itself throw turns a diagnosable
173
+ * failure into a mystery.
174
+ */
175
+ function isPipeworxOrigin(url: string | URL | undefined | null): boolean {
176
+ if (!url) return false;
177
+ let host: string;
178
+ try {
179
+ host = new URL(url instanceof URL ? url.href : url).hostname.toLowerCase();
180
+ } catch {
181
+ return false;
182
+ }
183
+ if (host === 'pipeworx.io' || host.endsWith('.pipeworx.io')) return true;
184
+ return SUPABASE_PROJECT_HOST.test(host);
185
+ }
186
+
187
+ /**
188
+ * Append the marker when this failure was OUR origin failing to answer.
189
+ *
190
+ * `status` is the HTTP status when there is one, and omitted for a timeout —
191
+ * where there is no response at all, and "the origin did not answer" is the
192
+ * whole observation. Statuses below 500 are left alone: a 404 from our own
193
+ * registry for a slug that does not exist is the caller's argument, not our
194
+ * outage, and marking it would put ordinary 404s on the incident dashboard.
195
+ *
196
+ * Idempotent, so a message that is wrapped and re-marked on the way up (the
197
+ * fleet pack's retry loop re-throws through two layers) carries the marker once.
198
+ */
199
+ function markInternalOrigin(
200
+ message: string,
201
+ url: string | URL | undefined | null,
202
+ status?: number,
203
+ ): string {
204
+ if (status !== undefined && status < 500) return message;
205
+ if (!isPipeworxOrigin(url)) return message;
206
+ if (message.includes(INTERNAL_ORIGIN_MARKER)) return message;
207
+ return message + INTERNAL_ORIGIN_MARKER;
208
+ }
209
+
210
+ /**
211
+ * Which blob4 value a failure from our own web services books as, or undefined
212
+ * if this is not one.
213
+ *
214
+ * Ordered AFTER `internalDbMetricsClass` at the call site: a PostgREST envelope
215
+ * from our own Supabase is a strictly more specific statement about the same
216
+ * row (which of our services, and why), and the two cannot disagree about
217
+ * whether the failure is ours.
218
+ */
219
+ function internalHostMetricsClass(error: string): string | undefined {
220
+ return error.includes(INTERNAL_ORIGIN_MARKER) ? INTERNAL_SERVICE_UNREACHABLE_CLASS : undefined;
221
+ }
222
+
223
+
224
+ /**
225
+ * One place to turn a failed `fetch` into an error a caller can act on.
226
+ *
227
+ * Nearly every pack was written the same way:
228
+ *
229
+ * if (!res.ok) throw new Error(`Unsplash: ${res.status}`);
230
+ *
231
+ * which discards the response body — and the body is usually where the upstream
232
+ * says what was actually wrong ("**symbol** not found: GBP", "parameter `year`
233
+ * out of range", "unknown taxonomy id"). The caller gets a number, cannot
234
+ * self-correct, and retries the same broken call. A 2026-07-31 sweep found this
235
+ * shape in 481 of 1,400 packs, 47 of them PLATFORM-keyed.
236
+ *
237
+ * It also hides bugs one level down. Two of the first three packs audited had a
238
+ * second defect that only existed because of this line: unsplash's rate-limit
239
+ * branch sat BELOW a catch-all and was unreachable, and bea-gov parsed
240
+ * `BEAAPI.Error.APIErrorDescription` below a `!res.ok` throw that made the
241
+ * parsing dead code for every non-200.
242
+ *
243
+ * DELIBERATELY NOT A CLASSIFIER. It does not add `user_error:` /
244
+ * `upstream_down:` prefixes. Those decide which tier a failure lands in, and the
245
+ * `error` tier is what the daily problem-tools list is built from — it means
246
+ * "Pipeworx has a defect". A 400 is genuinely ambiguous: often a caller's bad
247
+ * argument, but sometimes a query WE built wrong (ted-eu comma-joined its CPV
248
+ * values into something TED rejected, and that bug was found only because it sat
249
+ * in `error`). Blanket-classifying 400s as caller mistakes would have hidden it.
250
+ * A pack that KNOWS which it is should keep saying so explicitly; this helper is
251
+ * for the 481 that say nothing at all.
252
+ */
253
+
254
+ /** Longest upstream explanation we'll pass through. Enough for a real message,
255
+ * short enough that an HTML page or a stack trace can't swamp the error. */
256
+
257
+ const MAX_DETAIL = 300;
258
+
259
+ /**
260
+ * Default bound for `fetchWithTimeout` when a pack doesn't state its own.
261
+ *
262
+ * 25s mirrors the number `epo-ops` landed on after measuring the real failure:
263
+ * a degraded upstream that doesn't error, it just never answers, and a Worker
264
+ * sits in `await fetch()` until ITS OWN execution budget kills the request —
265
+ * which can take minutes, not seconds (epo_ops_search_patents measured 4-8
266
+ * MINUTE hangs before this existed). 25s is short enough that a caller gets a
267
+ * fast, actionable error instead of holding the connection, and long enough
268
+ * that it doesn't false-trip on a merely-slow-but-alive upstream.
269
+ */
270
+ const DEFAULT_FETCH_TIMEOUT_MS = 25_000;
271
+
272
+ /**
273
+ * Read the body of a failed response and fold it into a throwable Error.
274
+ *
275
+ * Usage — note the `await`, which is the one thing that makes this a mechanical
276
+ * change rather than a drop-in:
277
+ *
278
+ * if (!res.ok) throw await httpError(res, 'Unsplash');
279
+ *
280
+ * Safe to call on any non-ok response: a body that is missing, empty, unreadable
281
+ * or HTML degrades to exactly the old `Name: 404` string rather than throwing
282
+ * something new from inside the error path.
283
+ */
284
+ async function httpError(res: Response, name: string): Promise<Error> {
285
+ return new Error(await httpErrorMessage(res, name));
286
+ }
287
+
288
+ /** The message text without constructing an Error — for packs that need to wrap
289
+ * it in their own envelope or add an explicit classification prefix. */
290
+ async function httpErrorMessage(res: Response, name: string): Promise<string> {
291
+ // The one place a 5xx from a host WE run gets stamped as ours. `res.url` is
292
+ // the URL the fetch actually resolved to (after redirects), so this is a fact
293
+ // about the call rather than a guess from the `name` the pack passed in —
294
+ // reword that label freely, the class does not move. See
295
+ // internal-host-class.ts; no-op for every third-party upstream, which is why
296
+ // this touches 481 packs' error text and changes none of it.
297
+ return markInternalOrigin(
298
+ `${name}: ${res.status}${detailSuffix(await readDetail(res))}`,
299
+ res.url,
300
+ res.status,
301
+ );
302
+ }
303
+
304
+ /**
305
+ * Just the upstream's own explanation — no name, no status.
306
+ *
307
+ * For a pack that has already said both in its own sentence. epo-ops reads
308
+ * `EPO rejected this search as too large (HTTP 413) — ${httpErrorMessage(…)}`,
309
+ * which rendered as `… (HTTP 413) — EPO: 413.` once the XML detail was being
310
+ * dropped: the upstream named twice, the status twice, and the one thing EPO
311
+ * actually said ("Not enough characters before truncation character") nowhere
312
+ * (fleet #712). Returns '' when the body carries nothing readable, so a caller
313
+ * can fall back to its own wording.
314
+ */
315
+ async function upstreamDetail(res: Response): Promise<string> {
316
+ return readDetail(res);
317
+ }
318
+
319
+ /**
320
+ * Read a SUCCESSFUL response as JSON, failing loudly when it isn't JSON.
321
+ *
322
+ * `httpError` above only ever runs on `!res.ok`, which leaves the nastier half
323
+ * of the problem unhandled: an upstream that answers **HTTP 200 with an HTML
324
+ * page**. A bot wall, a login redirect, a maintenance interstitial and a CDN
325
+ * error page are all 200s, so `res.ok` is true, and `res.json()` then throws
326
+ * `Unexpected token '<', "<!DOCTYPE "... is not valid JSON`.
327
+ *
328
+ * That string is the problem. It names no upstream, carries no status, and
329
+ * reads like a parser bug in Pipeworx — so it lands in the `error` tier, which
330
+ * means "we have a defect", and the caller is told nothing they can act on.
331
+ * data.govt.nz sat dead behind an Imperva challenge this way and every
332
+ * status-code health check we own reported it green (7889a845). A zero-length
333
+ * body has the same shape: `Unexpected end of JSON input`, seen this week on
334
+ * uk-gazette (83% of external calls) and census.
335
+ *
336
+ * UNLIKE `httpError`, this one DOES classify, and the asymmetry is deliberate.
337
+ * A 400 is genuinely ambiguous — often the caller's bad argument, sometimes a
338
+ * query we built wrong — so blanket-classifying it would hide our own bugs.
339
+ * There is no such ambiguity here: **no argument a caller can pass makes a JSON
340
+ * API return an HTML page.** It is always the upstream, so `upstream_down:` is
341
+ * a statement of fact rather than a guess, and it keeps these out of the
342
+ * problem-tools list where they crowd out real defects.
343
+ *
344
+ * const data = await parseJson<Feed>(res, 'UK Gazette');
345
+ *
346
+ * Call it only after the `!res.ok` check — on a failed response you want
347
+ * `httpError`, which mines the body for the upstream's own explanation.
348
+ */
349
+ async function parseJson<T>(res: Response, name: string): Promise<T> {
350
+ let raw: string;
351
+ try {
352
+ raw = await res.text();
353
+ } catch {
354
+ throw new Error(
355
+ `upstream_down: ${name} returned a body that could not be read (HTTP ${res.status}). ` +
356
+ 'The connection most likely dropped mid-response; retrying is reasonable.',
357
+ );
358
+ }
359
+
360
+ const type = res.headers.get('content-type') ?? 'no content-type';
361
+
362
+ if (!raw.trim()) {
363
+ throw new Error(
364
+ `upstream_down: ${name} answered HTTP ${res.status} with an EMPTY body where JSON was expected (${type}). ` +
365
+ 'Nothing about the request can cause this — it is an upstream fault, and the same call may well work on retry.',
366
+ );
367
+ }
368
+
369
+ // Checked before parsing rather than in the catch, because knowing it is
370
+ // markup is what turns "we failed to parse something" into "they served a
371
+ // web page" — the second is diagnosable, the first is not.
372
+ const head = raw.slice(0, 200).trimStart().toLowerCase();
373
+ if (head.startsWith('<!doctype') || head.startsWith('<html') || head.startsWith('<?xml')) {
374
+ const kind = head.startsWith('<?xml') ? 'an XML document' : 'an HTML page';
375
+ // The summary, not the source. Pasting the first 120 characters of a web
376
+ // page handed the agent `<!DOCTYPE html><html lang="en"…` — the same leak
377
+ // this branch exists to describe (fleet #712).
378
+ throw new Error(
379
+ `upstream_down: ${name} answered HTTP ${res.status} with ${kind} instead of JSON (${type}). ` +
380
+ 'That is typically a bot wall, a login redirect or a maintenance page — it is returned as a SUCCESS, ' +
381
+ `so status-code health checks read it as fine. No argument change will get past it. ` +
382
+ `The page says: ${summarizeErrorBody(raw) || 'nothing readable'}`,
383
+ );
384
+ }
385
+
386
+ try {
387
+ return JSON.parse(raw) as T;
388
+ } catch {
389
+ throw new Error(
390
+ `upstream_down: ${name} answered HTTP ${res.status} with a body that is not valid JSON (${type}). ` +
391
+ `It begins: ${stripMarkup(raw).slice(0, 120) || '(unreadable)'}`,
392
+ );
393
+ }
394
+ }
395
+
396
+ /**
397
+ * `fetch`, but bounded — the fix for a systemic gap found 2026-08-30: a grep
398
+ * audit of every pack's `mcps/*\/src/index.ts` found 1,339 of ~1,500 call
399
+ * `fetch()` with NO timeout guard anywhere in the file. Two of those
400
+ * (epo-ops, statcan) were confirmed live-hanging for 4-8 minutes before this
401
+ * existed — every unguarded call carries the same risk, just unconfirmed.
402
+ *
403
+ * Mirrors the `epoFetch` wrapper `mcps/epo-ops/src/index.ts` shipped first:
404
+ * bound the request with `AbortSignal.timeout`, and on a timeout/abort throw
405
+ * an `upstream_down:` error that names the upstream and the bound rather than
406
+ * letting the raw `TimeoutError`/`AbortError` (which names neither) propagate.
407
+ * `upstream_down:` is deliberate, same reasoning as `parseJson` above — no
408
+ * argument a caller passes can make an upstream hang, so it is always the
409
+ * upstream's fault, and marking it that way keeps a slow API off the
410
+ * problem-tools list where it would crowd out our own defects.
411
+ *
412
+ * Usage — a mechanical swap for a bare `fetch(url, init)`:
413
+ *
414
+ * const res = await fetchWithTimeout(url, init, 'Some API');
415
+ *
416
+ * Pass `timeoutMs` as a fourth argument to override the default for a pack
417
+ * with a known-slower upstream; the label should be the same short name you'd
418
+ * pass to `httpError`/`httpErrorMessage` for that call.
419
+ */
420
+ async function fetchWithTimeout(
421
+ url: string | URL,
422
+ init: RequestInit = {},
423
+ name: string,
424
+ timeoutMs: number = DEFAULT_FETCH_TIMEOUT_MS,
425
+ ): Promise<Response> {
426
+ try {
427
+ return await fetch(url, { ...init, signal: AbortSignal.timeout(timeoutMs) });
428
+ } catch (err) {
429
+ if (err instanceof Error && (err.name === 'TimeoutError' || err.name === 'AbortError')) {
430
+ // States the OBSERVATION (no response in N seconds), not a diagnosis.
431
+ // "appears to be degraded" is an inference about the vendor that we have
432
+ // not checked, and it is wrong in a way that misdirects whoever reads it:
433
+ // a timeout from a Worker can equally mean OUR egress is blocked.
434
+ //
435
+ // Measured today (2026-09-01, fleet #1047): every call to
436
+ // mainnet.base.org failed from the x402 facilitator while the identical
437
+ // request from a laptop returned 200. Base was entirely healthy; the
438
+ // public RPC refuses Cloudflare Worker egress. Had this message fired
439
+ // there it would have blamed Base by name, and the next person would have
440
+ // waited for a vendor outage to clear that did not exist.
441
+ // A timeout has no status to test — there is no response at all — so
442
+ // `markInternalOrigin` is called without one: an origin we run that never
443
+ // answered is an availability failure by definition. This is the half of
444
+ // fleet #1096 with neither a SQLSTATE nor a status code to key on.
445
+ throw new Error(
446
+ markInternalOrigin(
447
+ `upstream_down: ${name} did not respond within ${timeoutMs / 1000}s. ` +
448
+ `That can be ${name} being slow or down, or this environment being unable to reach it ` +
449
+ `(some hosts refuse datacenter/Worker egress) — retry shortly, and check reachability ` +
450
+ `from elsewhere before concluding ${name} is down.`,
451
+ url,
452
+ ),
453
+ );
454
+ }
455
+ throw err;
456
+ }
457
+ }
458
+
459
+ function detailSuffix(detail: string): string {
460
+ return detail ? ` — ${detail}` : '';
461
+ }
462
+
463
+ async function readDetail(res: Response): Promise<string> {
464
+ let raw: string;
465
+ try {
466
+ raw = await res.text();
467
+ } catch {
468
+ // Body already consumed, or the connection died mid-read. The status alone
469
+ // is still worth throwing — never let the error path throw its own error.
470
+ return '';
471
+ }
472
+ return summarizeErrorBody(raw);
473
+ }
474
+
475
+ /**
476
+ * Turn ANY error body — JSON, HTML, XML or plain text — into one short phrase
477
+ * that never contains markup.
478
+ *
479
+ * This used to just drop an HTML or XML body on the floor, on the reasoning
480
+ * that markup crowds out the status. That was half right. Dropping it loses the
481
+ * one sentence a caller could have acted on: an `Access Denied` title, an SDMX
482
+ * `<message:Error>` text, an OPS fault string. A 2026-08-30 support sweep
483
+ * measured 13 of 291 caller-facing error rows carrying a raw page or document
484
+ * verbatim, across 11 packs, and in every one of them the useful content —
485
+ * "Access Denied", "Invalid country code", "SCRAPE_TIMEOUT" — was in there,
486
+ * buried in markup the agent had to parse out of a string (fleet #712).
487
+ *
488
+ * So: extract the meaning, discard the markup. The output is passed through
489
+ * `stripMarkup` unconditionally, which is what lets `check:error-body-leak`
490
+ * assert mechanically that no caller-facing message can contain `<?xml`,
491
+ * `<!DOCTYPE` or `<html`.
492
+ */
493
+ function summarizeErrorBody(raw: string): string {
494
+ if (!raw || !raw.trim()) return '';
495
+
496
+ const head = raw.slice(0, 400).trimStart().toLowerCase();
497
+
498
+ // An HTML error page (Cloudflare interstitial, nginx default, a login
499
+ // redirect) says what it is in its <title>, and almost nowhere else.
500
+ if (head.startsWith('<!doctype') || head.startsWith('<html')) {
501
+ const title = htmlTitle(raw);
502
+ return title
503
+ ? `${title} (upstream returned an HTML error page, not an API response)`
504
+ : 'upstream returned an HTML error page, not an API response';
505
+ }
506
+
507
+ // XML fault documents — EPO OPS, SDMX (`<message:Error>`), SOAP faults. The
508
+ // human sentence sits in a child element whose tag name says what it is.
509
+ if (head.startsWith('<?xml') || head.startsWith('<')) {
510
+ const fault = xmlFaultText(raw);
511
+ return fault
512
+ ? `${stripMarkup(fault).slice(0, MAX_DETAIL)} (from the upstream's XML error document)`
513
+ : 'upstream returned an XML error document with no readable message';
514
+ }
515
+
516
+ // Most JSON error bodies bury one human sentence among ids and echoed request
517
+ // params. Prefer that sentence; fall back to the whole body when the shape is
518
+ // unfamiliar, since an unfamiliar shape is exactly when we can least afford to
519
+ // guess wrong and show nothing.
520
+ const fromJson = messageFromJson(raw);
521
+ return stripMarkup(fromJson ?? raw).slice(0, MAX_DETAIL);
522
+ }
523
+
524
+ /** The `<title>` of an HTML error page, or its first `<h1>` — the two places a
525
+ * bot wall, a 502 and an "Access Denied" all state what happened. */
526
+ function htmlTitle(raw: string): string | null {
527
+ const head = raw.slice(0, 4000);
528
+ for (const re of [/<title[^>]*>([\s\S]*?)<\/title>/i, /<h1[^>]*>([\s\S]*?)<\/h1>/i]) {
529
+ const m = re.exec(head);
530
+ const text = m ? stripMarkup(m[1]) : '';
531
+ if (text) return text.slice(0, 160);
532
+ }
533
+ return null;
534
+ }
535
+
536
+ /** Tag names that carry the explanation in an XML fault document, namespace
537
+ * prefix optional (`<message:Error>`, `<com:Text>`, `<faultstring>`). */
538
+ const XML_FAULT_TAG_RE =
539
+ /<(?:[A-Za-z0-9_.-]+:)?(?:text|message|description|faultstring|reason|detail|title|errormessage|error)\b[^>]*>([^<]{2,400})</i;
540
+
541
+ function xmlFaultText(raw: string): string | null {
542
+ const head = raw.slice(0, 8000);
543
+ const tagged = XML_FAULT_TAG_RE.exec(head);
544
+ if (tagged && tagged[1].trim()) return tagged[1];
545
+
546
+ // Nothing conventionally named — take the longest text node instead. A fault
547
+ // document with one sentence in an oddly named element is still readable;
548
+ // returning nothing at all is not.
549
+ let best = '';
550
+ for (const m of head.matchAll(/>([^<>]{8,400})</g)) {
551
+ const text = m[1].trim();
552
+ if (text.length > best.length) best = text;
553
+ }
554
+ return best || null;
555
+ }
556
+
557
+ /**
558
+ * Remove every tag and stray angle bracket, then collapse whitespace.
559
+ *
560
+ * Applied to everything on the way out, including the JSON and plain-text
561
+ * paths, because an upstream is free to embed markup in a JSON string field —
562
+ * and a leak is a leak regardless of which branch produced it.
563
+ */
564
+ function stripMarkup(s: string): string {
565
+ return collapse(decodeEntities(s.replace(/<[^>]*>/g, ' ')).replace(/[<>]/g, ' '));
566
+ }
567
+
568
+ /** The handful of entities that show up in error-page titles. Decoded AFTER
569
+ * tags are stripped and BEFORE the angle-bracket sweep, so `&lt;script&gt;`
570
+ * in a title cannot decode into markup that survives — EMBL-EBI's ChEMBL 500
571
+ * page renders as `500 Internal Server Error &lt; EMBL-EBI` otherwise. */
572
+ function decodeEntities(s: string): string {
573
+ return s
574
+ .replace(/&(?:amp|#0*38);/gi, '&')
575
+ .replace(/&(?:lt|#0*60);/gi, '<')
576
+ .replace(/&(?:gt|#0*62);/gi, '>')
577
+ .replace(/&(?:quot|#0*34);/gi, '"')
578
+ .replace(/&(?:#0*39|apos|#x0*27);/gi, "'")
579
+ .replace(/&nbsp;/gi, ' ');
580
+ }
581
+
582
+ /** The conventional "what went wrong" field, under any of the names upstreams
583
+ * actually use. Checked in order; first non-empty string wins. */
584
+ const MESSAGE_KEYS = [
585
+ 'message', 'error_message', 'errorMessage', 'detail', 'details',
586
+ 'description', 'error_description', 'reason', 'title', 'fault',
587
+ ];
588
+
589
+ function messageFromJson(raw: string): string | null {
590
+ let parsed: unknown;
591
+ try {
592
+ parsed = JSON.parse(raw);
593
+ } catch {
594
+ return null;
595
+ }
596
+ return pickMessage(parsed, 0);
597
+ }
598
+
599
+ function pickMessage(node: unknown, depth: number): string | null {
600
+ // Two levels covers `{error: {message}}` and `{errors: [{detail}]}`, the two
601
+ // shapes that account for nearly all of them, without walking a large payload.
602
+ if (depth > 2 || node == null) return null;
603
+
604
+ if (typeof node === 'string') return node.trim() || null;
605
+
606
+ if (Array.isArray(node)) {
607
+ for (const item of node) {
608
+ const found = pickMessage(item, depth + 1);
609
+ if (found) return found;
610
+ }
611
+ return null;
612
+ }
613
+
614
+ if (typeof node !== 'object') return null;
615
+ const obj = node as Record<string, unknown>;
616
+
617
+ for (const key of MESSAGE_KEYS) {
618
+ const v = obj[key];
619
+ if (typeof v === 'string' && v.trim()) return v.trim();
620
+ }
621
+ // `{error: …}` where error is itself an object or a string — the single most
622
+ // common wrapper, so it is worth descending into by name rather than scanning
623
+ // every key and risking picking up an echoed request parameter.
624
+ for (const key of ['error', 'errors', 'fault', 'Error', 'data']) {
625
+ if (key in obj) {
626
+ const found = pickMessage(obj[key], depth + 1);
627
+ if (found) return found;
628
+ }
629
+ }
630
+ return null;
631
+ }
632
+
633
+ /** Errors are read in a single line of log output; newlines and runs of
634
+ * whitespace make a multi-line body unreadable there. */
635
+ function collapse(s: string): string {
636
+ return s.replace(/\s+/g, ' ').trim();
637
+ }
638
+ /**
639
+ * FDSN seismic web services MCP — seismometer metadata, data holdings and
640
+ * regional earthquake catalogues, over the international FDSN standard.
641
+ *
642
+ * This is the INSTRUMENT side of seismology, not the earthquake catalogue:
643
+ * which seismic stations exist, where they are, what channels they record, who
644
+ * operates them, and which data centre holds the waveforms for a given time
645
+ * window. `usgs-earthquakes` and `emsc` already cover "what earthquakes
646
+ * happened"; `fdsn_events` here adds the REGIONAL agency catalogues (GFZ, INGV,
647
+ * RESIF, KOERI), which record local magnitude-1-to-3 seismicity that the global
648
+ * catalogues never list.
649
+ *
650
+ * APIs (all keyless):
651
+ * - https://service.earthscope.org/fdsnws/station/1/query station metadata
652
+ * - https://service.earthscope.org/irisws/fedcatalog/1/query federated holdings
653
+ * - https://geofon.gfz.de/fdsnws/event/1/query (+ other FDSN nodes) events
654
+ *
655
+ * TRAPS, all verified 2026-09-17:
656
+ * - service.iris.edu 301-redirects to service.earthscope.org. Call the new host
657
+ * directly; the old one still resolves and costs a redirect on every call.
658
+ * - EarthScope serves only `station` and `dataselect` under /fdsnws/. Their
659
+ * `event` and `availability` services answer 404 (availability sits behind an
660
+ * EarthScope login — it redirects to a trailing-slash path served by uvicorn
661
+ * with `vary: Cookie`). `fdsn_availability` here therefore answers from
662
+ * fedcatalog, which is keyless and reports the same holdings question across
663
+ * every federated data centre rather than one.
664
+ * - `nodata=404` makes "no rows" indistinguishable from "endpoint retired":
665
+ * both are a bare 404 with an empty body. These tools send nodata=204 so an
666
+ * empty result is a 204 and a 404 genuinely means the route is gone.
667
+ */
668
+
669
+
670
+ const UA = 'pipeworx-mcp-earthscope-fdsn/1.0 (+https://pipeworx.io)';
671
+ const EARTHSCOPE = 'https://service.earthscope.org';
672
+
673
+ async function pwFetch(url: string, upstream: string): Promise<Response> {
674
+ return fetchWithTimeout(url, { headers: { 'User-Agent': UA } }, upstream);
675
+ }
676
+
677
+ /**
678
+ * FDSN event nodes that serve an open, keyless event/1/query. Each publishes
679
+ * its OWN agency catalogue, which is the point: GFZ is global rapid moment
680
+ * tensors, INGV is Italian local seismicity down to M1, RESIF is metropolitan
681
+ * France, KOERI is Turkey and the eastern Mediterranean.
682
+ */
683
+ const EVENT_NODES: Record<string, { url: string; name: string; scope: string }> = {
684
+ gfz: { url: 'https://geofon.gfz.de/fdsnws/event/1/query', name: 'GFZ GEOFON (Germany)', scope: 'Global rapid solutions, M4.5+ worldwide' },
685
+ ingv: { url: 'https://webservices.ingv.it/fdsnws/event/1/query', name: 'INGV (Italy)', scope: 'Italy and surroundings, down to ~M0.5' },
686
+ resif: { url: 'https://api.franceseisme.fr/fdsnws/event/1/query', name: 'RESIF / FranceSeisme', scope: 'Metropolitan France and overseas territories' },
687
+ koeri: { url: 'http://www.koeri.boun.edu.tr/services/fdsnws/event/1/query', name: 'KOERI (Turkey)', scope: 'Turkey and the eastern Mediterranean' },
688
+ };
689
+
690
+ const tools: McpToolExport['tools'] = [
691
+ {
692
+ name: 'fdsn_stations',
693
+ description:
694
+ '"Which seismometers are near Yellowstone?" / "what channels does station IU ANMO record?" — seismic station metadata from EarthScope, the largest FDSN data centre. AUTHORITATIVE for where seismic instruments physically are: returns network and station codes, site name, latitude/longitude/elevation, the operating date range, and (at channel level) every recorded channel with its sample rate, sensor description, azimuth and dip. Search by network/station code, by a geographic box, or by radius around a point. PREFER OVER WEB SEARCH for seismic instrumentation questions.',
695
+ inputSchema: {
696
+ type: 'object' as const,
697
+ properties: {
698
+ network: { type: 'string', description: 'FDSN network code, e.g. "IU" (Global Seismographic Network), "US", "CI" (Southern California). Wildcards * and ? allowed; comma-separate several.' },
699
+ station: { type: 'string', description: 'Station code, e.g. "ANMO". Wildcards allowed, e.g. "ANM*".' },
700
+ channel: { type: 'string', description: 'Channel code, e.g. "BHZ" (broadband high-gain vertical), "LH*". Only meaningful at level "channel".' },
701
+ level: { type: 'string', description: '"network", "station" (default), or "channel" — how much metadata to return. "channel" is much larger.' },
702
+ latitude: { type: 'number', description: 'Centre latitude for a radial search (use with longitude and max_radius_km).' },
703
+ longitude: { type: 'number', description: 'Centre longitude for a radial search.' },
704
+ max_radius_km: { type: 'number', description: 'Radius in km around latitude/longitude.' },
705
+ min_latitude: { type: 'number', description: 'Bounding-box south edge.' },
706
+ max_latitude: { type: 'number', description: 'Bounding-box north edge.' },
707
+ min_longitude: { type: 'number', description: 'Bounding-box west edge.' },
708
+ max_longitude: { type: 'number', description: 'Bounding-box east edge.' },
709
+ starttime: { type: 'string', description: 'Only stations operating on or after this date, YYYY-MM-DD.' },
710
+ endtime: { type: 'string', description: 'Only stations operating on or before this date, YYYY-MM-DD.' },
711
+ limit: { type: 'number', description: 'Max rows to return (default 100, max 1000).' },
712
+ },
713
+ required: [],
714
+ },
715
+ },
716
+ {
717
+ name: 'fdsn_events',
718
+ description:
719
+ '"What small earthquakes happened near Etna this week?" — earthquake catalogues published by REGIONAL seismological agencies over the FDSN standard: GFZ GEOFON (global rapid solutions), INGV (Italy, down to about M0.5), RESIF (France), KOERI (Turkey and the eastern Mediterranean). Complements the global catalogues — these agencies list the local magnitude-1-to-3 events that USGS and EMSC never publish. Returns event id, origin time, latitude/longitude/depth, magnitude and magnitude type, region name and event type.',
720
+ inputSchema: {
721
+ type: 'object' as const,
722
+ properties: {
723
+ datacenter: { type: 'string', description: 'Which agency catalogue: "gfz" (default, global), "ingv" (Italy), "resif" (France), "koeri" (Turkey).' },
724
+ starttime: { type: 'string', description: 'Earliest origin time, YYYY-MM-DD (default: 30 days ago).' },
725
+ endtime: { type: 'string', description: 'Latest origin time, YYYY-MM-DD.' },
726
+ min_magnitude: { type: 'number', description: 'Minimum magnitude.' },
727
+ max_magnitude: { type: 'number', description: 'Maximum magnitude.' },
728
+ min_depth_km: { type: 'number', description: 'Minimum hypocentre depth in km.' },
729
+ max_depth_km: { type: 'number', description: 'Maximum hypocentre depth in km.' },
730
+ latitude: { type: 'number', description: 'Centre latitude for a radial search.' },
731
+ longitude: { type: 'number', description: 'Centre longitude for a radial search.' },
732
+ max_radius_km: { type: 'number', description: 'Radius in km around latitude/longitude.' },
733
+ min_latitude: { type: 'number', description: 'Bounding-box south edge.' },
734
+ max_latitude: { type: 'number', description: 'Bounding-box north edge.' },
735
+ min_longitude: { type: 'number', description: 'Bounding-box west edge.' },
736
+ max_longitude: { type: 'number', description: 'Bounding-box east edge.' },
737
+ limit: { type: 'number', description: 'Max events to return (default 50, max 500).' },
738
+ },
739
+ required: [],
740
+ },
741
+ },
742
+ {
743
+ name: 'fdsn_availability',
744
+ description:
745
+ '"Where can I download waveform data for station IU ANMO in September 2026?" — which FDSN data centres actually hold seismic waveform data for a given network/station/channel and time window, from the EarthScope federated catalogue. Returns each data centre that holds matching data, its dataselect and station service URLs, and the exact network/station/location/channel/time rows it can serve. This is the "is the data there, and from whom" question — the waveform bytes themselves are fetched from the returned dataselect URL, not from here.',
746
+ inputSchema: {
747
+ type: 'object' as const,
748
+ properties: {
749
+ network: { type: 'string', description: 'FDSN network code, e.g. "IU". Wildcards allowed.' },
750
+ station: { type: 'string', description: 'Station code, e.g. "ANMO". Wildcards allowed.' },
751
+ channel: { type: 'string', description: 'Channel code, e.g. "BHZ" or "BH*" (default "*").' },
752
+ location: { type: 'string', description: 'Location code, e.g. "00". Default any.' },
753
+ starttime: { type: 'string', description: 'Window start, YYYY-MM-DD or ISO 8601 (default: 7 days ago).' },
754
+ endtime: { type: 'string', description: 'Window end, YYYY-MM-DD or ISO 8601 (default: today).' },
755
+ limit: { type: 'number', description: 'Max channel rows to return per data centre (default 50, max 500).' },
756
+ },
757
+ required: [],
758
+ },
759
+ },
760
+ ];
761
+
762
+ function clampLimit(raw: unknown, def: number, max: number): number {
763
+ const n = Math.round(Number(raw ?? def));
764
+ return Number.isFinite(n) ? Math.min(max, Math.max(1, n)) : def;
765
+ }
766
+
767
+ function isoDate(raw: unknown): string | undefined {
768
+ if (raw == null || raw === '') return undefined;
769
+ const s = String(raw).trim();
770
+ if (!/^\d{4}-\d{2}-\d{2}([T ]\d{2}:\d{2}(:\d{2}(\.\d+)?)?Z?)?$/.test(s)) {
771
+ throw new Error(`user_error: times must be YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS, got "${raw}".`);
772
+ }
773
+ return s.replace(' ', 'T');
774
+ }
775
+
776
+ function daysAgo(n: number): string {
777
+ return new Date(Date.now() - n * 86400_000).toISOString().slice(0, 10);
778
+ }
779
+
780
+ function setIf(p: URLSearchParams, key: string, value: unknown) {
781
+ if (value != null && value !== '') p.set(key, String(value));
782
+ }
783
+
784
+ /** km -> degrees of great-circle arc, which is what FDSN maxradius takes. */
785
+ function kmToDeg(km: number): number {
786
+ return km / 111.195;
787
+ }
788
+
789
+ /**
790
+ * Parse an FDSN `format=text` body: a `#`-prefixed header row then pipe-
791
+ * delimited data rows. Field names differ by service, so the header is used
792
+ * rather than fixed positions.
793
+ */
794
+ function parseFdsnText(body: string): Array<Record<string, string>> {
795
+ const lines = body.split(/\r?\n/).filter((l) => l.trim().length > 0);
796
+ const headerLine = lines.find((l) => l.startsWith('#'));
797
+ if (!headerLine) return [];
798
+ const header = headerLine.replace(/^#/, '').split('|').map((h) => h.trim());
799
+ return lines
800
+ .filter((l) => !l.startsWith('#'))
801
+ .map((line) => {
802
+ const cells = line.split('|');
803
+ const row: Record<string, string> = {};
804
+ header.forEach((h, i) => { row[h] = (cells[i] ?? '').trim(); });
805
+ return row;
806
+ });
807
+ }
808
+
809
+ function num(v: string | undefined): number | null {
810
+ if (v == null || v === '') return null;
811
+ const n = Number(v);
812
+ return Number.isFinite(n) ? n : null;
813
+ }
814
+
815
+ async function fdsnText(url: string, upstream: string): Promise<string> {
816
+ const res = await pwFetch(url, upstream);
817
+ if (res.status === 204) return '';
818
+ const body = await res.text();
819
+ if (!res.ok) {
820
+ throw new Error(
821
+ `upstream_error: ${upstream} returned HTTP ${res.status} — ${body.slice(0, 300) || '(empty body)'}`,
822
+ );
823
+ }
824
+ return body;
825
+ }
826
+
827
+ /** Field names differ between `level=station` and `level=channel` responses. */
828
+ function pick(row: Record<string, string>, ...names: string[]): string | undefined {
829
+ for (const n of names) if (row[n] != null && row[n] !== '') return row[n];
830
+ return undefined;
831
+ }
832
+
833
+ async function stations(args: Record<string, unknown>) {
834
+ const level = String(args.level ?? 'station').trim().toLowerCase();
835
+ if (!['network', 'station', 'channel'].includes(level)) {
836
+ throw new Error(`user_error: level must be "network", "station" or "channel", got "${args.level}".`);
837
+ }
838
+ const limit = clampLimit(args.limit, 100, 1000);
839
+
840
+ const p = new URLSearchParams({ level, format: 'text', nodata: '204' });
841
+ setIf(p, 'net', args.network);
842
+ setIf(p, 'sta', args.station);
843
+ setIf(p, 'cha', args.channel);
844
+ setIf(p, 'starttime', isoDate(args.starttime));
845
+ setIf(p, 'endtime', isoDate(args.endtime));
846
+ setIf(p, 'minlatitude', args.min_latitude);
847
+ setIf(p, 'maxlatitude', args.max_latitude);
848
+ setIf(p, 'minlongitude', args.min_longitude);
849
+ setIf(p, 'maxlongitude', args.max_longitude);
850
+ if (args.latitude != null && args.longitude != null) {
851
+ setIf(p, 'latitude', args.latitude);
852
+ setIf(p, 'longitude', args.longitude);
853
+ const km = Number(args.max_radius_km ?? 100);
854
+ p.set('maxradius', kmToDeg(km).toFixed(4));
855
+ }
856
+ if (![...p.keys()].some((k) => ['net', 'sta', 'cha', 'minlatitude', 'latitude'].includes(k))) {
857
+ // An unfiltered channel-level query is the whole federation: tens of MB.
858
+ if (level === 'channel') {
859
+ throw new Error('user_error: level="channel" needs at least a network, station or geographic filter — an unfiltered channel query returns the entire archive.');
860
+ }
861
+ p.set('net', '*');
862
+ }
863
+
864
+ const url = `${EARTHSCOPE}/fdsnws/station/1/query?${p}`;
865
+ const rows = parseFdsnText(await fdsnText(url, 'EarthScope FDSN station service'));
866
+
867
+ return {
868
+ source: 'EarthScope (IRIS DMC) FDSN station service',
869
+ level,
870
+ total_rows: rows.length,
871
+ count: Math.min(rows.length, limit),
872
+ truncated: rows.length > limit,
873
+ stations: rows.slice(0, limit).map((r) => ({
874
+ network: pick(r, 'Network'),
875
+ station: pick(r, 'Station') ?? null,
876
+ location: pick(r, 'Location') ?? null,
877
+ channel: pick(r, 'Channel') ?? null,
878
+ site_name: pick(r, 'SiteName', 'Description') ?? null,
879
+ latitude: num(pick(r, 'Latitude')),
880
+ longitude: num(pick(r, 'Longitude')),
881
+ elevation_m: num(pick(r, 'Elevation')),
882
+ depth_m: num(pick(r, 'Depth')),
883
+ azimuth_deg: num(pick(r, 'Azimuth')),
884
+ dip_deg: num(pick(r, 'Dip')),
885
+ sensor: pick(r, 'SensorDescription') ?? null,
886
+ sample_rate_hz: num(pick(r, 'SampleRate')),
887
+ start_time: pick(r, 'StartTime') ?? null,
888
+ end_time: pick(r, 'EndTime') || null,
889
+ total_stations: num(pick(r, 'TotalStations')),
890
+ })),
891
+ };
892
+ }
893
+
894
+ async function events(args: Record<string, unknown>) {
895
+ const key = String(args.datacenter ?? 'gfz').trim().toLowerCase();
896
+ const node = EVENT_NODES[key];
897
+ if (!node) {
898
+ throw new Error(
899
+ `user_error: unknown datacenter "${args.datacenter}". FDSN event nodes wired here: ${Object.keys(EVENT_NODES).join(', ')}.`,
900
+ );
901
+ }
902
+ const limit = clampLimit(args.limit, 50, 500);
903
+
904
+ const p = new URLSearchParams({ format: 'text', nodata: '204' });
905
+ p.set('starttime', isoDate(args.starttime) ?? daysAgo(30));
906
+ setIf(p, 'endtime', isoDate(args.endtime));
907
+ setIf(p, 'minmagnitude', args.min_magnitude);
908
+ setIf(p, 'maxmagnitude', args.max_magnitude);
909
+ setIf(p, 'mindepth', args.min_depth_km);
910
+ setIf(p, 'maxdepth', args.max_depth_km);
911
+ setIf(p, 'minlatitude', args.min_latitude);
912
+ setIf(p, 'maxlatitude', args.max_latitude);
913
+ setIf(p, 'minlongitude', args.min_longitude);
914
+ setIf(p, 'maxlongitude', args.max_longitude);
915
+ if (args.latitude != null && args.longitude != null) {
916
+ setIf(p, 'latitude', args.latitude);
917
+ setIf(p, 'longitude', args.longitude);
918
+ p.set('maxradius', kmToDeg(Number(args.max_radius_km ?? 100)).toFixed(4));
919
+ }
920
+ p.set('limit', String(Math.min(500, limit * 2)));
921
+
922
+ const rows = parseFdsnText(await fdsnText(`${node.url}?${p}`, node.name));
923
+
924
+ return {
925
+ datacenter: key,
926
+ datacenter_name: node.name,
927
+ catalog_scope: node.scope,
928
+ total_rows: rows.length,
929
+ count: Math.min(rows.length, limit),
930
+ truncated: rows.length > limit,
931
+ events: rows.slice(0, limit).map((r) => ({
932
+ event_id: pick(r, 'EventID') ?? null,
933
+ time: pick(r, 'Time') ?? null,
934
+ latitude: num(pick(r, 'Latitude')),
935
+ longitude: num(pick(r, 'Longitude')),
936
+ depth_km: num(pick(r, 'Depth/km', 'Depth/Km', 'Depth')),
937
+ magnitude: num(pick(r, 'Magnitude')),
938
+ magnitude_type: pick(r, 'MagType') ?? null,
939
+ magnitude_author: pick(r, 'MagAuthor') || null,
940
+ region: pick(r, 'EventLocationName') ?? null,
941
+ event_type: pick(r, 'EventType') || null,
942
+ author: pick(r, 'Author') || null,
943
+ catalog: pick(r, 'Catalog') || null,
944
+ })),
945
+ };
946
+ }
947
+
948
+ /**
949
+ * fedcatalog answers in its own `format=request` dialect, not FDSN text: blank-
950
+ * line-separated blocks, each opening with KEY=value service lines and then
951
+ * bare `NET STA LOC CHA START END` rows.
952
+ */
953
+ async function availability(args: Record<string, unknown>) {
954
+ const limit = clampLimit(args.limit, 50, 500);
955
+ const p = new URLSearchParams({ format: 'request' });
956
+ p.set('net', String(args.network ?? '*'));
957
+ p.set('sta', String(args.station ?? '*'));
958
+ p.set('cha', String(args.channel ?? '*'));
959
+ setIf(p, 'loc', args.location);
960
+ p.set('starttime', `${isoDate(args.starttime) ?? daysAgo(7)}`);
961
+ p.set('endtime', `${isoDate(args.endtime) ?? new Date().toISOString().slice(0, 10)}`);
962
+
963
+ if (p.get('net') === '*' && p.get('sta') === '*') {
964
+ throw new Error('user_error: give at least a network or a station — an unfiltered federated holdings query returns the whole archive.');
965
+ }
966
+
967
+ const body = await fdsnText(`${EARTHSCOPE}/irisws/fedcatalog/1/query?${p}`, 'EarthScope FDSN federated catalogue');
968
+
969
+ const centers: Array<Record<string, unknown>> = [];
970
+ let current: { datacenter: string | null; website: string | null; dataselect: string | null; station: string | null; availability: string | null; channels: Array<Record<string, unknown>> } | null = null;
971
+
972
+ for (const raw of body.split(/\r?\n/)) {
973
+ const line = raw.trim();
974
+ if (!line) continue;
975
+ if (line.startsWith('DATACENTER=')) {
976
+ if (current) centers.push(finishCenter(current, limit));
977
+ const [id, site] = line.slice('DATACENTER='.length).split(',');
978
+ current = { datacenter: id?.trim() ?? null, website: site?.trim() ?? null, dataselect: null, station: null, availability: null, channels: [] };
979
+ continue;
980
+ }
981
+ if (!current) continue;
982
+ if (line.startsWith('DATASELECTSERVICE=')) { current.dataselect = line.split('=')[1].trim(); continue; }
983
+ if (line.startsWith('STATIONSERVICE=')) { current.station = line.split('=')[1].trim(); continue; }
984
+ if (line.startsWith('AVAILABILITYSERVICE=')) { current.availability = line.split('=')[1].trim(); continue; }
985
+ if (line.includes('=')) continue; // any other service line
986
+ const f = line.split(/\s+/);
987
+ if (f.length >= 6) {
988
+ current.channels.push({
989
+ network: f[0], station: f[1], location: f[2], channel: f[3],
990
+ start_time: f[4], end_time: f[5],
991
+ });
992
+ }
993
+ }
994
+ if (current) centers.push(finishCenter(current, limit));
995
+
996
+ const totalChannels = centers.reduce((n, c) => n + (c.total_channels as number), 0);
997
+ return {
998
+ source: 'EarthScope FDSN federated catalogue (irisws/fedcatalog)',
999
+ query: {
1000
+ network: p.get('net'), station: p.get('sta'), channel: p.get('cha'),
1001
+ starttime: p.get('starttime'), endtime: p.get('endtime'),
1002
+ },
1003
+ datacenters_holding_data: centers.length,
1004
+ total_channels: totalChannels,
1005
+ datacenters: centers,
1006
+ };
1007
+ }
1008
+
1009
+ function finishCenter(c: { datacenter: string | null; website: string | null; dataselect: string | null; station: string | null; availability: string | null; channels: Array<Record<string, unknown>> }, limit: number) {
1010
+ return {
1011
+ datacenter: c.datacenter,
1012
+ website: c.website,
1013
+ dataselect_url: c.dataselect,
1014
+ station_url: c.station,
1015
+ availability_url: c.availability,
1016
+ total_channels: c.channels.length,
1017
+ truncated: c.channels.length > limit,
1018
+ channels: c.channels.slice(0, limit),
1019
+ };
1020
+ }
1021
+
1022
+ async function callTool(name: string, args: Record<string, unknown>): Promise<unknown> {
1023
+ switch (name) {
1024
+ case 'fdsn_stations':
1025
+ return stations(args);
1026
+ case 'fdsn_events':
1027
+ return events(args);
1028
+ case 'fdsn_availability':
1029
+ return availability(args);
1030
+ default:
1031
+ throw new Error(`Unknown tool: ${name}`);
1032
+ }
1033
+ }
1034
+
1035
+ export default { tools, callTool, meter: { credits: 1 } } satisfies McpToolExport;