echelongraph-mcp 3.0.0 → 3.1.0

package/dist/index.js

@@ -67,12 +67,13 @@ import { registerCveIntel } from "./tools/cve_intel.js";
 import { registerCveRemediation } from "./tools/cve_remediation.js";
 import { fixStatusSchema } from "./fixStatus.js";
 import { registerGetCwe } from "./tools/get_cwe.js";
-import { holdRequest, isHttpEntrypoint, requestSignal, upstreamHeaders, upstreamUserAgent } from "./runtime.js";
+import { holdRequest, isHttpEntrypoint, networkFailureClass, requestSignal, upstreamFailed, upstreamHeaders, upstreamUserAgent } from "./runtime.js";
 import { registerVendorAdvisoryTools } from "./tools/vendor_advisories.js";
 import { registerPrompts } from "./prompts.js";
 import { registerResources } from "./resources.js";
+import { withSchemaRefusal } from "./schemaRefusal.js";
 import { answering, answeringNow, cutData, dataText, FIRST_TEXT_BLOCK_BESIDE_A_CUT, FULL_ARG, GET_CVE_WHOLE, NO_DATA_CUT, STRUCTURED_BUDGET, TEXT_BUDGET_DESCRIPTION, wholePage, } from "./textBudget.js";
-import { SHODAN_ATTRIBUTION, SHODAN_OWNERSHIP } from "./requiredText.js";
+import { KEV_CATALOG_FLAG, KEV_LISTED_DEPRECATED, KEV_OBSERVATION_FLAG, PATCH_AVAILABLE_WITHDRAWN, SHODAN_ATTRIBUTION, SHODAN_OWNERSHIP } from "./requiredText.js";
 // The package actually running, read from the package.json that ships beside dist/. The MCP
 // handshake (serverInfo) and the User-Agent both carry its name and version, so the API's
 // access log can count adoption per version without a code change per release.
@@ -192,6 +193,8 @@ function retryAfterSeconds(v) {
 // The request is cancelled when init.signal aborts (check_sbom's call was cancelled) or, on the
 // hosted endpoint, when the client it answers has gone (runtime.ts requestSignal, #2775): a
 // network failure saying so, which nobody reads, since the SDK sends nothing for a cancelled call.
+// Every other failure is reported (runtime.ts upstreamFailed, #2948): on the hosted endpoint, one
+// mcp_upstream_failed line; on stdio, nothing.
 export async function api(path, init) {
     const limitMs = init?.timeoutMs === undefined ? TIMEOUT_MS : Math.max(0, Math.min(TIMEOUT_MS, Math.floor(init.timeoutMs)));
     const m = init?.method && init.method.toUpperCase() !== "GET" ? { method: init.method.toUpperCase() } : {};
@@ -199,6 +202,11 @@ export async function api(path, init) {
     const cancelledFailure = () => ({ ok: false, kind: "network", path, ...m, detail: "cancelled: the call was abandoned before the API answered" });
     if (callers.some((s) => s.aborted))
         return cancelledFailure();
+    const t0 = Date.now();
+    const reported = (f, failureClass) => {
+        upstreamFailed({ failureClass, path, status: f.status ?? null, afterMs: Date.now() - t0 });
+        return f;
+    };
     const ctrl = new AbortController();
     let timedOut = false;
     let cancelled = false;
@@ -213,7 +221,7 @@ export async function api(path, init) {
     for (const s of callers)
         s.addEventListener("abort", cancel, { once: true });
     const own = limitMs === TIMEOUT_MS ? {} : { timeoutMs: limitMs };
-    const timeout = () => ({ ok: false, kind: "timeout", path, ...m, ...own, detail: `no response within ${limitMs} ms` });
+    const timeout = () => reported({ ok: false, kind: "timeout", path, ...m, ...own, detail: `no response within ${limitMs} ms` }, "timeout");
     try {
         let res;
         try {
@@ -228,18 +236,22 @@ export async function api(path, init) {
             });
         }
         catch (e) {
-            return timedOut ? timeout() : cancelled ? cancelledFailure() : { ok: false, kind: "network", path, ...m, detail: describeError(e) };
+            return timedOut ? timeout() : cancelled ? cancelledFailure() : reported({ ok: false, kind: "network", path, ...m, detail: describeError(e) }, networkFailureClass(e));
         }
         let body;
         try {
             body = await res.text();
         }
         catch (e) {
-            return timedOut ? timeout() : cancelled ? cancelledFailure() : { ok: false, kind: "network", path, ...m, detail: `reading the body failed: ${describeError(e)}` };
+            return timedOut
+                ? timeout()
+                : cancelled
+                    ? cancelledFailure()
+                    : reported({ ok: false, kind: "network", path, ...m, detail: `reading the body failed: ${describeError(e)}` }, networkFailureClass(e));
         }
         if (!res.ok) {
             const retryAfter = retryAfterSeconds(res.headers.get("retry-after"));
-            return { ok: false, kind: "http", path, ...m, status: res.status, ...(retryAfter === undefined ? {} : { retryAfter }), detail: apiMessage(body) };
+            return reported({ ok: false, kind: "http", path, ...m, status: res.status, ...(retryAfter === undefined ? {} : { retryAfter }), detail: apiMessage(body) }, "http");
         }
         let data;
         try {
@@ -247,10 +259,10 @@ export async function api(path, init) {
         }
         catch {
             const ctype = res.headers.get("content-type") ?? "no content-type";
-            return { ok: false, kind: "not_json", path, ...m, status: res.status, detail: `${ctype}; body starts: ${snippet(body)}` };
+            return reported({ ok: false, kind: "not_json", path, ...m, status: res.status, detail: `${ctype}; body starts: ${snippet(body)}` }, "not_json");
         }
         if (data === null || typeof data !== "object") {
-            return { ok: false, kind: "not_object", path, ...m, status: res.status, detail: `body was ${snippet(body)}` };
+            return reported({ ok: false, kind: "not_object", path, ...m, status: res.status, detail: `body was ${snippet(body)}` }, "not_object");
         }
         return { ok: true, status: res.status, data };
     }
@@ -331,9 +343,21 @@ const envelopeText = (structured, said, own) => {
 // describeFailure already quotes (a redacted cause, the API's own message). Every note is a
 // sentence of the message, so the text envelope carries none.
 export const failure = (state, message, error, coverage = null) => {
+    reportUnusable(error);
+    return failureResult(state, message, error, coverage);
+};
+const failureResult = (state, message, error, coverage) => {
     const structuredContent = { state, measured_at: null, method: null, coverage, freshness: null, notes: sentences(message), error };
     return { content: [text(message), envelopeText(structuredContent, message, [])], structuredContent, isError: true };
 };
+// #2948: an answer the API sent that the tool could not use (a 2xx whose fields are not what it
+// reads: a schema mismatch, exposure_radar's mcp_servers counts, cve_intel's sections) is an
+// upstream failure too, reported here once per answer; api() reported every other kind itself.
+function reportUnusable(error) {
+    const unusable = error.kind === "radars" ? (error.radars ?? []).filter((r) => r.kind === "unexpected_shape") : error.kind === "unexpected_shape" ? [error] : [];
+    for (const u of unusable)
+        upstreamFailed({ failureClass: "unexpected_shape", path: u.path, status: u.status, afterMs: null });
+}
 const errorOf = (f) => ({ kind: f.kind, path: f.path, status: f.status ?? null, message: f.detail });
 export const failed = (tool, f) => {
     if (f.kind === "http" && f.status === 400) {
@@ -363,18 +387,23 @@ function unexpectedShape(tool, error) {
         .map((i) => `${i.path.map(String).join(".") || "(root)"}: ${i.message}`)
         .join("; ");
     const detail = `the answer did not match this tool's output schema (${issues})`;
-    return failure("failed", `${tool} FAILED: EchelonGraph at ${SHOWN_BASE} answered, but ${detail}, so it is not relayed. ${NOT_A_FINDING}`, {
+    // #2948's review: this server's own schema refused what it built, which is no upstream failure: reported as
+    // output_schema (http.ts logs it at ERROR), not as unexpected_shape. The client's error kind is unchanged.
+    upstreamFailed({ failureClass: "output_schema", path: null, status: null, afterMs: null });
+    return failureResult("failed", `${tool} FAILED: EchelonGraph at ${SHOWN_BASE} answered, but ${detail}, so it is not relayed. ${NOT_A_FINDING}`, {
         kind: "unexpected_shape",
         path: null,
         status: null,
         message: detail,
-    });
+    }, null);
 }
 // Every success is checked against the tool's own outputSchema before it is returned.
 export const checked = (tool, schema, r) => {
     if (r.isError)
         return r;
-    const p = schema.safeParse(r.structuredContent);
+    // #3121: the published schema's success branch is open; this server's own answers are held to
+    // the closed one.
+    const p = (STRICT.get(schema) ?? schema).safeParse(r.structuredContent);
     return p.success ? r : unexpectedShape(tool, p.error);
 };
 // A success: content[0] is the data (cut to DATA_TEXT_BUDGET when it is larger, #2783), content[1]
@@ -439,13 +468,18 @@ export const realInstant = (s) => s !== undefined && Date.parse(s) > 0;
 // measured_at is the time the answer itself gives for its records, where it gives one:
 // summary.last_updated (MAX(modified) over the active records, core-backend cve/store.go
 // Summary) for cve_summary, the record's updated_at (when EchelonGraph last wrote it) for
-// get_cve, and none for a search page, whose rows each carry their own. None of them serves a
-// fleet-wide time at which the feed's pollers last completed, so freshness is null: the
-// summary's poller.last_poll_at is the answering instance's own NVD poller (cve/poller.go
-// Stats, in memory), and is relayed in data but not presented as the feed's freshness; the note
-// says what the whole poller block is (summaryPollerNote, #2647).
+// get_cve, and none for a search page, whose rows each carry their own. freshness is the
+// summary's nvd_poll block, the FLEET's last completed NVD poll, where the answer carries a usable
+// one (nvdPollFreshness, #3276); a search page and a record carry no poll-completion time, so
+// theirs is null. The summary's poller.last_poll_at is the answering instance's own NVD poller
+// (cve/poller.go Stats, in memory), and is relayed in data but never presented as the feed's
+// freshness; the note says what the whole poller block is (summaryPollerNote, #2647).
 const CVE_FEED_METHOD = "EchelonGraph's CVE Pulse feed: CVE records compiled from NVD, MITRE-CNA pre-NVD records, CISA-KEV, EPSS and GitHub GHSA, each polled from its source on a schedule.";
-const NO_FEED_FRESHNESS = "freshness is null: the CVE feed's answer carries no time at which its pollers last completed a poll for the feed as a whole.";
+// #3276: search_cves' and get_cve's, whose answers carry no poll-completion time. Through 3.0.2 it
+// said "the CVE feed's answer" carries none, read as the feed's, while cve_summary's answer carries
+// the fleet's last completed NVD poll; it now says where that is. Within 3 characters of the old
+// sentence's length, so get_cve's structured cut, at its 30,000-character budget, is unchanged.
+const NO_FEED_FRESHNESS = "freshness is null: this answer carries no poll-completion time; the CVE feed summary gives the fleet's last completed NVD poll.";
 function scoreStateOf(rec) {
     const v = boolAt(rec, "score_assessed");
     return v === true ? "assessed" : v === false ? "not_assessed" : "unstated";
@@ -632,6 +666,96 @@ function summaryPollerShaped(d) {
         note: ` Left out of the data above because the answer sent ${unusable.length === 1 ? "it" : "them"} in a JSON type other than the one this tool reads: ${listed(named)}.${relayed}`,
     };
 }
+// ── nvd_poll, the fleet's last completed NVD poll: cve_summary's freshness (#3276) ──
+//
+// Since #3242 (core-backend cve/handler.go nvdPollBlock) the summary answer carries nvd_poll beside
+// poller: last_completed_at, when the FLEET last completed an NVD poll (the durable
+// KeyNVDWindowCompleted row, the end of the last window fetched and stored without an error), in
+// RFC 3339; scope "fleet"; and interval, the poller's configured interval as Go's Duration.String
+// ("20m0s"), left out where the answering instance runs no poller. The API leaves the whole block
+// out when that time is unknown (none on record, or the read failed), and never puts the answering
+// instance's own counters in its place. Through 3.0.2 freshness was null and the note said the feed
+// served no poll-completion time, while the same answer's data carried one (production,
+// 2026-10-17T22:48Z: nvd_poll.last_completed_at 2026-10-17T22:45:09Z, scope fleet, interval 20m0s).
+//
+// So freshness.nvd_poll is that block, read as exposure_radar reads a radar's last_run_at: the time
+// as sent, relayed only when it is an RFC 3339 instant on a calendar date that exists, after the Go
+// zero time, and at most NVD_POLL_SKEW_MS after this server's clock (a later one is a clock or a
+// bug, never a poll that has completed), on a block whose scope is fleet; interval as sent where it
+// is a Go duration, else null. Anything else leaves freshness null, and the envelope's own note
+// says why: the answer carries no nvd_poll block (an older API, or one that could not read the
+// time), or the block it carries gives no such time. Nothing is filled in, and data relays the
+// block as sent either way.
+const NVD_POLL_SKEW_MS = 5 * 60_000;
+const RFC3339_INSTANT = /^(\d{4})-(\d{2})-(\d{2})T([01]\d|2[0-3]):[0-5]\d:[0-5]\d(\.\d{1,9})?(Z|[+-]([01]\d|2[0-3]):[0-5]\d)$/;
+const GO_DURATION = /^(\d+(\.\d+)?(ns|us|µs|ms|s|m|h))+$/;
+// A Go duration's length in milliseconds ("20m0s" is 1,200,000), or undefined when it is not one.
+const GO_UNIT_MS = { ns: 1e-6, us: 1e-3, "µs": 1e-3, ms: 1, s: 1_000, m: 60_000, h: 3_600_000 };
+function goDurationMs(s) {
+    if (!GO_DURATION.test(s))
+        return undefined;
+    let ms = 0;
+    for (const [, n, , unit] of s.matchAll(/(\d+(\.\d+)?)(ns|us|µs|ms|s|m|h)/g))
+        ms += Number(n) * GO_UNIT_MS[unit];
+    return ms;
+}
+// A last completed poll older than this many intervals (or than STALE_POLL_FALLBACK_MS when the
+// answer gives no usable interval) is said to be old: the CVE counts may lag NVD by that much.
+const STALE_POLL_INTERVALS = 3;
+const STALE_POLL_FALLBACK_MS = 60 * 60_000;
+// The instant's epoch milliseconds when s is an RFC 3339 date-time (its T and Z in either case, as
+// RFC 3339 allows) on a calendar date that exists, after the Unix epoch (so never the Go zero time); else undefined. Date.parse
+// alone takes 2026-02-30 as 2026-03-02.
+function rfc3339Ms(s) {
+    const t = s.toUpperCase();
+    const m = RFC3339_INSTANT.exec(t);
+    if (!m)
+        return undefined;
+    const [y, mo, d] = [Number(m[1]), Number(m[2]), Number(m[3])];
+    const day = new Date(Date.UTC(y, mo - 1, d));
+    if (day.getUTCFullYear() !== y || day.getUTCMonth() !== mo - 1 || day.getUTCDate() !== d)
+        return undefined;
+    const ms = Date.parse(t);
+    return Number.isFinite(ms) && ms > 0 ? ms : undefined;
+}
+const NO_NVD_POLL = "freshness is null: this answer carries no nvd_poll block (an older API, or the API holds no fleet NVD poll it could read).";
+// cve_summary's freshness from its answer, and the envelope's sentence about it. `now` is the clock
+// last_completed_at is held against: this server's, when the answer is composed.
+function nvdPollFreshness(d, now) {
+    const block = field(d, "nvd_poll");
+    if (block === undefined || block === null)
+        return { freshness: null, note: NO_NVD_POLL };
+    const unusable = (why) => ({
+        freshness: null,
+        note: `freshness is null: ${why}, so this answer gives no usable time at which the fleet last completed an NVD poll; data relays the block as sent.`,
+    });
+    if (!isPlainObject(block))
+        return unusable(`the answer's nvd_poll is ${jsonKind(block)}, where this tool reads an object`);
+    if (block.scope !== "fleet")
+        return unusable("the answer's nvd_poll.scope is not fleet");
+    const at = block.last_completed_at;
+    if (at === undefined || at === null)
+        return unusable("the answer's nvd_poll carries no last_completed_at");
+    const ms = typeof at === "string" ? rfc3339Ms(at) : undefined;
+    if (typeof at !== "string" || ms === undefined)
+        return unusable("the answer's nvd_poll.last_completed_at is not a real RFC 3339 time");
+    if (ms > now + NVD_POLL_SKEW_MS)
+        return unusable(`the answer's nvd_poll.last_completed_at is more than ${NVD_POLL_SKEW_MS / 60_000} minutes after this server's clock`);
+    const interval = typeof block.interval === "string" && GO_DURATION.test(block.interval) ? block.interval : null;
+    const every = interval === null ? "the answer gives no usable nvd_poll.interval, so interval is null" : `the poll runs at an interval of ${interval} (nvd_poll.interval)`;
+    // #3276 review: an old poll is said to be old, as exposure_radar says of a radar past its
+    // threshold (#3010), instead of being relayed as freshness with nothing said.
+    const intervalMs = interval === null ? undefined : goDurationMs(interval);
+    const limit = intervalMs !== undefined && intervalMs > 0 ? STALE_POLL_INTERVALS * intervalMs : STALE_POLL_FALLBACK_MS;
+    const stale = now - ms > limit
+        ? `freshness.nvd_poll.last_run_at is about ${age(now - ms)} before this answer, more than ${intervalMs !== undefined && intervalMs > 0 ? `${STALE_POLL_INTERVALS} times the poll's interval` : "an hour (the answer gives no usable interval)"}, so the CVE counts may lag NVD by about that much.`
+        : undefined;
+    return {
+        stale,
+        freshness: { nvd_poll: { last_run_at: at, scope: "fleet", interval } },
+        note: `freshness.nvd_poll is the fleet's last completed NVD poll: last_run_at is data.nvd_poll.last_completed_at, the end of the window the fleet's last completed NVD poll stored (whichever API instance ran it), never the answering instance's poller.last_poll_at, and ${every}.`,
+    };
+}
 async function cveSummary() {
     const tool = "cve_summary";
     try {
@@ -642,17 +766,20 @@ async function cveSummary() {
         // #2771: a poller field of another JSON type is left out, never a failure of the call.
         const { data, note: pollerShape } = summaryPollerShaped(r.data);
         const updated = strAt(data, "summary", "last_updated");
+        // #3276: the fleet's last completed NVD poll, where the answer carries a usable nvd_poll.
+        const fresh = nvdPollFreshness(data, Date.now());
         const env = {
             state: "measured",
             measured_at: instantOrNull(updated),
             method: CVE_FEED_METHOD,
             coverage: null,
-            freshness: null,
+            freshness: fresh.freshness,
             notes: [
                 realInstant(updated)
                     ? "measured_at is summary.last_updated: the newest modification time among the active CVE records these counts include."
                     : "measured_at is null: the answer carries no real summary.last_updated.",
-                NO_FEED_FRESHNESS,
+                fresh.note,
+                ...(fresh.stale ? [fresh.stale] : []),
             ],
         };
         const total = numAt(data, "summary", "total");
@@ -858,6 +985,38 @@ function bodNote(cve, rec) {
         return "";
     return ` score_factors.bod_26_04 is CISA BOD 26-04's remediation timeline for ${cve}: ${exposed} if the affected system is publicly exposed, ${internal} if it is not; whether a system is publicly exposed is its owner's to say. Its inputs: in CISA KEV ${kev}, ${auto}, ${ti}. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, not EchelonGraph's advice.`;
 }
+// #2879: what the scorer's components (core-backend scoring v4.0) say that the score does not, as
+// at most two sentences, each only where the record carries what it reads. Nothing for a record
+// scored before v4.0, so every answer before it reads as it did.
+//  - The score above the impact severity: echelongraph_score 9.0 on a CVSS 5.4 CVE is a KEV
+//    listing's floor (or an EPSS uplift), exploitation and not impact, and a model handed only
+//    "9.0 CRITICAL" reports a critical-impact flaw. Said only when the score is higher, naming the
+//    rule that raised it (score_factors.rule_triggered); a KEV CVE with no CVSS gets the
+//    "severity not yet published" form.
+//  - A null eg_likelihood.probability: no EPSS on record, never a probability of 0.
+function componentsNote(cve, rec) {
+    const out = [];
+    const score = numAt(rec, "echelongraph_score");
+    const rule = strAt(rec, "score_factors", "rule_triggered");
+    const by = rule === "kev_exploitation" ? "a CISA KEV listing floors it at 9.0" : rule === "epss_uplift" ? "EPSS lifts it toward 9.0" : null;
+    const sev = field(rec, "eg_severity");
+    if (sev !== null && typeof sev === "object" && score !== undefined && by) {
+        const s = numAt(sev, "score");
+        const band = strAt(sev, "severity");
+        const who = strAt(sev, "provider");
+        if (boolAt(sev, "assessed") === true && s !== undefined && band && score > s) {
+            out.push(` eg_severity is the impact severity of ${cve} alone: CVSS ${s.toFixed(1)} ${band}${who ? ` (${who})` : ""}. echelongraph_score ${score.toFixed(1)} is higher because ${by}: that is exploitation, not impact.`);
+        }
+        else if (boolAt(sev, "assessed") === false && strAt(sev, "unassessed_reason") === "kev_listed_no_cvss") {
+            out.push(` eg_severity is not assessed: ${cve} is exploited (CISA KEV) and no CVSS severity is published yet, so echelongraph_score ${score.toFixed(1)} is the floor for confirmed exploitation, not an impact rating.`);
+        }
+    }
+    const lik = field(rec, "eg_likelihood");
+    if (lik !== null && typeof lik === "object" && field(lik, "probability") === null && strAt(lik, "null_reason")) {
+        out.push(` eg_likelihood.probability is null: no FIRST EPSS probability is on record for ${cve}, so report its likelihood as unknown, not low.`);
+    }
+    return out.join("");
+}
 // #2841: one sentence on the record's remediation summary, where the API sends one.
 // #3070, #3076: the CNA's own date and fix sentence, named as the CNA's. Nothing when the record
 // carries neither; a value of another JSON type is not quoted (the outputSchema refuses it).
@@ -869,11 +1028,17 @@ function cnaRecordNote(cve, rec) {
     const by = who ? `its CNA, ${who},` : "its CNA";
     const date = strAt(rec, "date_public");
     const fix = strAt(rec, "cna_solution");
+    // #3178: a sentence of the record's workarounds is said to be its workaround.
+    const workaround = strAt(rec, "cna_solution_section") === "workaround";
     const parts = [];
     if (date)
         parts.push(` date_public is when ${cve} was made public as ${by} states it in the CVE record (datePublic), not the record's publication date.`);
-    if (fix)
+    if (fix && workaround) {
+        parts.push(` cna_solution is a fix statement from the CVE record's workarounds (cna_solution_section workaround), not its solutions, written by ${by} and relayed verbatim: it names the fixed release, and is not EchelonGraph's advice.`);
+    }
+    else if (fix) {
         parts.push(` cna_solution is the CVE record's own fix statement, written by ${by} and relayed verbatim: it names the fixed release, and is not EchelonGraph's advice.`);
+    }
     return parts.join("");
 }
 function remediationSummaryNote(cve, rec) {
@@ -911,7 +1076,7 @@ async function getCVE(cve_id) {
             return failed(tool, r);
         const written = strAt(r.data, "updated_at");
         const cve = strAt(r.data, "cve_id") ?? id;
-        return succeeded(r.data, `${okHead(tool, r.status)} Returned the record for ${cve}.${cveScoreNote(cve, r.data)}${bodNote(cve, r.data)}${kevTextNote(r.data)}${cnaRecordNote(cve, r.data)}${remediationSummaryNote(cve, r.data)}`, {
+        return succeeded(r.data, `${okHead(tool, r.status)} Returned the record for ${cve}.${cveScoreNote(cve, r.data)}${componentsNote(cve, r.data)}${bodNote(cve, r.data)}${kevTextNote(r.data)}${cnaRecordNote(cve, r.data)}${remediationSummaryNote(cve, r.data)}`, {
             state: "measured",
             measured_at: instantOrNull(written),
             method: CVE_FEED_METHOD,
@@ -1246,19 +1411,31 @@ function readWindow(v) {
     const undated = v.undated;
     if (!isCount(undated) || undated < 0 || !Number.isInteger(undated))
         return { bad: true };
-    if (undated > 0)
-        return { undated, bad: false };
+    if (undated > 0) {
+        // Over the dated rows only. Every row undated (from and to null) or a span that is not one
+        // relays no dated_window; the note still says how many rows carry no time.
+        const span = realInstant(from) && realInstant(to) && Date.parse(from) <= Date.parse(to);
+        return span ? { dated: { from, to, undated }, undated, bad: false } : { undated, bad: false };
+    }
     if (v.from === null && v.to === null)
         return { bad: false }; // nothing counted, so nothing dated
     if (!realInstant(from) || !realInstant(to) || Date.parse(from) > Date.parse(to))
         return { bad: true };
     return { window: { from, to }, bad: false };
 }
-// The sentence for a radar's window, or for the rows it leaves undated.
-function windowSentences(prefix, w, what) {
+// The sentence for a radar's window, or for the rows it leaves undated. `total`, where the answer
+// carries it, is how many rows the counts count, so the dated ones can be named too.
+function windowSentences(prefix, w, what, total) {
     if (w.window) {
         return [`${prefix}.window.from (${w.window.from}) and ${prefix}.window.to (${w.window.to}) are timestamps, not counts: ${what}. They span observations made at different times, not one observation time.`];
     }
+    if (w.dated) {
+        const d = w.dated;
+        const of = total !== undefined && total >= d.undated ? `${total - d.undated} of the ${total} rows it counts` : "the rows it counts that carry an observation time";
+        return [
+            `${prefix} carries no window over every row it counts: ${d.undated} of them have no observation time on record (${prefix}.dated_window.undated). ${prefix}.dated_window.from (${d.from}) and ${prefix}.dated_window.to (${d.to}) are timestamps, not counts, over ${of} only: ${what}. They span observations made at different times, not one observation time, and do not describe the undated rows.`,
+        ];
+    }
     if (w.undated !== undefined) {
         return [`${prefix} carries no window: ${w.undated} of the rows it counts have no observation time on record, so a window over the rest would not describe them.`];
     }
@@ -1298,6 +1475,8 @@ function readRadar(body, spec) {
         const w = readWindow(src[spec.window]);
         if (w.window)
             data.window = w.window;
+        else if (w.dated)
+            data.dated_window = w.dated;
         else if (w.bad)
             unusable.push(spec.window);
         undated = w.undated;
@@ -1558,7 +1737,7 @@ function readKEVExposure(body, now) {
         }
         sentences.push("kev_exposure.newest_kev[].cvss_v3_score and kev_exposure.newest_kev[].epss_score are the CVE record's CVSS v3 base score and EPSS probability (0 to 1), absent when the record has none: scores, not counts.");
     }
-    sentences.push(...windowSentences("kev_exposure", { window: data.window, undated, bad: false }, "when Shodan collected the banners of the oldest and the newest of the service×CVE pairs counted, Shodan's own times, not when EchelonGraph stored or re-checked a pair"));
+    sentences.push(...windowSentences("kev_exposure", { window: data.window, dated: data.dated_window, undated, bad: false }, "when Shodan collected the banners of the oldest and the newest of the service×CVE pairs counted, Shodan's own times, not when EchelonGraph stored or re-checked a pair", n("correlations")));
     sentences.push(...lastCheck("kev_exposure", data));
     const stale = staleCheck("kev_exposure", data, now);
     sentences.push(...stale);
@@ -1615,7 +1794,7 @@ function readExposedDatabases(body, now) {
     if (gated.length) {
         sentences.push(`${gated.join("; ")}. The names are index, database, table or field names in the Shodan or LeakIX banner or in the check's response, never record values, and the gate passes one unambiguous term (such as ssn or cardholder) or two distinct indicators. It is precision-first: a service whose names do not pass it is not counted, whatever it holds, so the other services are not shown to hold no personal or card data.`);
     }
-    sentences.push(...windowSentences("exposed_databases", { window: data.window, undated, bad: false }, "when EchelonGraph's check last confirmed the oldest and the newest of the services counted answering without authentication"));
+    sentences.push(...windowSentences("exposed_databases", { window: data.window, dated: data.dated_window, undated, bad: false }, "when EchelonGraph's check last confirmed the oldest and the newest of the services counted answering without authentication"));
     sentences.push(...lastCheck("exposed_databases", data));
     const stale = staleCheck("exposed_databases", data, now);
     sentences.push(...stale);
@@ -1664,7 +1843,7 @@ function readLeakedCredentials(body, now) {
     if (totals.length || rankings.length) {
         sentences.push("None of these is validated: each is a credential-shaped string in a public commit that passed EchelonGraph's filters, at most structurally checked (a checksum or format decode) and never tested against its provider, so none of them is a count of working credentials.");
     }
-    sentences.push(...windowSentences("leaked_credentials", { window: data.window, undated, bad: false }, "when EchelonGraph's detector last found the oldest and the newest of the (repository, secret) pairs counted in a public commit"));
+    sentences.push(...windowSentences("leaked_credentials", { window: data.window, dated: data.dated_window, undated, bad: false }, "when EchelonGraph's detector last found the oldest and the newest of the (repository, secret) pairs counted in a public commit"));
     sentences.push(...lastCheck("leaked_credentials", data));
     const stale = staleCheck("leaked_credentials", data, now);
     sentences.push(...stale);
@@ -1698,6 +1877,8 @@ function readShadowAI(sa, now) {
         used.add("confirmed_window");
     if (confirmedWindow.window && confirmed.total !== undefined)
         confirmed.window = confirmedWindow.window;
+    else if (confirmedWindow.dated && confirmed.total !== undefined)
+        confirmed.dated_window = confirmedWindow.dated;
     // Observed: every row of shadow_ct_observations, whatever its liveness.
     const observed = {};
     const total = take("total", numAt(stats, "total"));
@@ -1734,7 +1915,7 @@ function readShadowAI(sa, now) {
         ? `Shadow AI: the answer carries no usable stats.visible_by_category, so it does not say how many services are confirmed exposed${last24Visible === undefined ? "" : `; confirmed_exposed.last_24h (${last24Visible}) counts confirmed-exposed services first recorded in the last 24 h`}.`
         : `Shadow AI confirmed exposed: ${confirmed.total} (confirmed_exposed.total, the sum of confirmed_exposed.by_category: services EchelonGraph's probes found answering without an authentication gate, with liveness active or, during a re-check, rechecking)${last24Visible === undefined ? "" : `, ${last24Visible} of them first recorded in the last 24 h (confirmed_exposed.last_24h)`}. Of the shadow_ai numbers, only confirmed_exposed counts exposed services.`);
     if (confirmed.total !== undefined) {
-        sentences.push(...windowSentences("shadow_ai.confirmed_exposed", { window: confirmedWindow.window, undated: confirmedWindow.undated, bad: false }, "when EchelonGraph's verifier ran the probe that last decided the oldest and the newest of the services confirmed_exposed counts"));
+        sentences.push(...windowSentences("shadow_ai.confirmed_exposed", { window: confirmedWindow.window, dated: confirmedWindow.dated, undated: confirmedWindow.undated, bad: false }, "when EchelonGraph's verifier ran the probe that last decided the oldest and the newest of the services confirmed_exposed counts"));
     }
     if (total !== undefined) {
         sentences.push(`Shadow AI observed: ${total} (observed.total) counts every Certificate Transparency or Shodan observation on record, whatever its verification state: that many observed, not that many exposed.`);
@@ -2062,12 +2243,12 @@ function readMCPServers(src, now) {
 // below), and the result's note labels every number relayed in the same words. Each text below
 // that names Shodan carries SHODAN_OWNERSHIP (#2306).
 const EXPOSURE_RADAR_DESCRIPTION = `Aggregate totals from EchelonGraph's internet-exposure radars: kev_exposure, internet-facing services running actively-exploited (CISA-KEV) CVEs, plus the ransomware-linked subset, derived from Shodan data; exposed_databases, unauthenticated data stores and observability UIs, found through Shodan (LeakIX when Shodan query credits run low) and then confirmed by EchelonGraph's own identified check (not a pure read: on Redis it names its client, and on ClickHouse its query is recorded in the server's query log); leaked_credentials, sampled from public GitHub push events; and shadow_ai, services found through Certificate Transparency logs and Shodan and then checked by EchelonGraph's identified probes. ${SHODAN_OWNERSHIP} It also gives MCP-server counts: hostnames named like an MCP server in EchelonGraph's own Certificate Transparency feed (no Shodan data), each counted once by its latest verdict from EchelonGraph's identified MCP probe, which never sends tools/call. Service counts are distinct ip:port services, not machines. The result's note, and the outputSchema's description of each radar, label every number by what it counts. Of the shadow_ai numbers, only confirmed_exposed counts exposed services. A kev_exposure.newest_kev CVE whose exposure_state is not_assessed has no measurement in the answer: its 0 is not one.`;
-const RADAR_KEV_FIELDS = `kev_exposure: kev_exposure.distinct_hosts counts distinct ip:port services, not machines (a machine answering on two ports counts twice), with at least one CISA-KEV-listed CVE on record, and kev_exposure.ransomware_hosts those with a ransomware-linked one; kev_exposure.kev_cves_exposed and kev_exposure.ransomware_cves count distinct CVEs with at least one such service; kev_exposure.correlations counts service×CVE pairs, not services, so a service with three KEV CVEs counts three times. kev_exposure.top_products, kev_exposure.top_countries and kev_exposure.top_cves rank up to 12 products, 10 countries and 12 CVEs by those services; kev_exposure.top_cves[].cvss_v3_score and kev_exposure.top_cves[].epss_score are the highest CVSS v3 base score and EPSS probability recorded on that CVE's observations. kev_exposure.trend counts service×CVE pairs still on record by the week in which each was first recorded, over 12 weeks, so earlier weeks read low. kev_exposure.newest_kev lists the 15 CVEs that EchelonGraph's CVE records most recently mark as CISA-KEV-listed, each with an exposure_state: exposed, where kev_exposure.newest_kev[].exposed_hosts counts distinct ip:port services on record with it; or not_assessed, where the API's answer holds no measurement for that CVE (its 0 is not one) and no count is relayed, and this answer does not say whether the radar tracks that CVE: tracking is answered per CVE. kev_exposure.newest_kev[].cvss_v3_score and kev_exposure.newest_kev[].epss_score are the CVE record's CVSS v3 base score and EPSS probability. kev_exposure.window.from and kev_exposure.window.to are timestamps, not counts: when Shodan collected the banners of the oldest and the newest of the service×CVE pairs counted, a span of observations made at different times; with a counted pair that has no such time on record there is no window. ${SHODAN_OWNERSHIP}`;
-const RADAR_DB_FIELDS = `exposed_databases: exposed_databases.distinct_hosts counts distinct ip:port services the check confirmed answering without authentication, and exposed_databases.engines the distinct engine types among them; exposed_databases.top_engines and exposed_databases.top_countries rank up to 15 engines and 10 countries by those services. exposed_databases.pii_likely and exposed_databases.pci_likely count services whose schema names (never record values) pass a high-confidence, precision-first gate for personal or payment-card data, so a service outside them is not shown to hold no such data. exposed_databases.window.from and exposed_databases.window.to are timestamps, not counts: when EchelonGraph's check last confirmed the oldest and the newest of the services counted, a span of checks made at different times; with a counted service that has no such time on record there is no window.`;
-const RADAR_LEAKED_FIELDS = `leaked_credentials: leaked_credentials.total counts (repository, secret) pairs, not distinct secrets, so one secret in three repositories counts three times; leaked_credentials.distinct_secrets counts each secret once and leaked_credentials.distinct_repos counts repositories; leaked_credentials.top_providers and leaked_credentials.top_types rank up to 15 providers and secret types by those pairs. None is validated: each is a credential-shaped string that passed EchelonGraph's filters, at most structurally checked and never tested against its provider. leaked_credentials.window.from and leaked_credentials.window.to are timestamps, not counts: when EchelonGraph's detector last found the oldest and the newest of the pairs counted.`;
+const RADAR_KEV_FIELDS = `kev_exposure: kev_exposure.distinct_hosts counts distinct ip:port services, not machines (a machine answering on two ports counts twice), with at least one CISA-KEV-listed CVE on record, and kev_exposure.ransomware_hosts those with a ransomware-linked one; kev_exposure.kev_cves_exposed and kev_exposure.ransomware_cves count distinct CVEs with at least one such service; kev_exposure.correlations counts service×CVE pairs, not services, so a service with three KEV CVEs counts three times. kev_exposure.top_products, kev_exposure.top_countries and kev_exposure.top_cves rank up to 12 products, 10 countries and 12 CVEs by those services; kev_exposure.top_cves[].cvss_v3_score and kev_exposure.top_cves[].epss_score are the highest CVSS v3 base score and EPSS probability recorded on that CVE's observations. kev_exposure.trend counts service×CVE pairs still on record by the week in which each was first recorded, over 12 weeks, so earlier weeks read low. kev_exposure.newest_kev lists the 15 CVEs that EchelonGraph's CVE records most recently mark as CISA-KEV-listed, each with an exposure_state: exposed, where kev_exposure.newest_kev[].exposed_hosts counts distinct ip:port services on record with it; or not_assessed, where the API's answer holds no measurement for that CVE (its 0 is not one) and no count is relayed, and this answer does not say whether the radar tracks that CVE: tracking is answered per CVE. kev_exposure.newest_kev[].cvss_v3_score and kev_exposure.newest_kev[].epss_score are the CVE record's CVSS v3 base score and EPSS probability. kev_exposure.window.from and kev_exposure.window.to are timestamps, not counts: when Shodan collected the banners of the oldest and the newest of the service×CVE pairs counted, a span of observations made at different times; with a counted pair that has no such time on record there is no window, and kev_exposure.dated_window.from and kev_exposure.dated_window.to span the dated pairs only, while kev_exposure.dated_window.undated counts the pairs with none. ${SHODAN_OWNERSHIP}`;
+const RADAR_DB_FIELDS = `exposed_databases: exposed_databases.distinct_hosts counts distinct ip:port services the check confirmed answering without authentication, and exposed_databases.engines the distinct engine types among them; exposed_databases.top_engines and exposed_databases.top_countries rank up to 15 engines and 10 countries by those services. exposed_databases.pii_likely and exposed_databases.pci_likely count services whose schema names (never record values) pass a high-confidence, precision-first gate for personal or payment-card data, so a service outside them is not shown to hold no such data. exposed_databases.window.from and exposed_databases.window.to are timestamps, not counts: when EchelonGraph's check last confirmed the oldest and the newest of the services counted, a span of checks made at different times; with a counted service that has no such time on record there is no window, and exposed_databases.dated_window.from and exposed_databases.dated_window.to span the dated services only, while exposed_databases.dated_window.undated counts those with none.`;
+const RADAR_LEAKED_FIELDS = `leaked_credentials: leaked_credentials.total counts (repository, secret) pairs, not distinct secrets, so one secret in three repositories counts three times; leaked_credentials.distinct_secrets counts each secret once and leaked_credentials.distinct_repos counts repositories; leaked_credentials.top_providers and leaked_credentials.top_types rank up to 15 providers and secret types by those pairs. None is validated: each is a credential-shaped string that passed EchelonGraph's filters, at most structurally checked and never tested against its provider. leaked_credentials.window.from and leaked_credentials.window.to are timestamps, not counts: when EchelonGraph's detector last found the oldest and the newest of the pairs counted; with a counted pair that has no such time on record there is no window, and leaked_credentials.dated_window.from and leaked_credentials.dated_window.to span the dated pairs only, while leaked_credentials.dated_window.undated counts those with none.`;
 // What the three stats radars' last_run_at is, and what is left out: the outputSchema's description of data.
 const RADAR_LAST_RUN_FIELDS = `A field this version cannot label is left out of data and named in the note. Each of the kev_exposure, exposed_databases and leaked_credentials radars also carries generated_at, when the API computed its totals, and, when the API can tell, last_run_at. kev_exposure.last_run_at, exposed_databases.last_run_at and leaked_credentials.last_run_at are timestamps, not counts: each is when that radar last completed a check, a cycle whose reads succeeded, among them a Shodan search (for exposed_databases, or its LeakIX fallback) that answered at least one query, or for leaked_credentials a read of the public GitHub event stream. A cycle that read nothing does not move it, and it is not the time of every record a radar's numbers count, which cover everything still on record, not only what the last check found. A radar whose answer carries no last_run_at has none in the result, and the note says nothing about it. ${SHODAN_OWNERSHIP}`;
-const RADAR_SHADOW_AI_FIELDS = `shadow_ai: the result is regrouped by what each number counts. shadow_ai.confirmed_exposed counts services EchelonGraph's probes found answering without an authentication gate (liveness active, or rechecking during a re-check): confirmed_exposed.total is the sum of confirmed_exposed.by_category, and confirmed_exposed.last_24h counts those first recorded in the last 24 h. Of the shadow_ai numbers, only confirmed_exposed counts exposed services. confirmed_exposed.window.from and confirmed_exposed.window.to are timestamps, not counts: when EchelonGraph's verifier ran the probe that last decided the oldest and the newest of those services, a span of probes made at different times. shadow_ai.observed counts every Certificate Transparency or Shodan observation on record, whatever its verification state: its numbers are observed, not exposed. They are observed.total; observed.by_category (the same observations by category); observed.last_24h (those first recorded in the last 24 h); observed.trend_30d (observations per UTC day over the last 30 days); and observed.top_products, observed.top_countries and observed.top_issuers (up to ten products, countries and issuers ranked by observations, where an issuer is the certificate's CA for a Certificate Transparency observation and the hosting operator Shodan reports for a Shodan one). shadow_ai.authentication counts observations by probe outcome: authentication.observed where a probe observed an authentication gate (a 401/403, a login page or an auth marker), and authentication.not_determined where the service answered but no probe could tell. Neither authentication count is part of confirmed_exposed, and observed.total minus confirmed_exposed.total is not a count of secured services. The shadow-AI poller block carries only running and last_run_at: last_run_at is when the radar's leader last completed a Certificate Transparency (crt.sh) cycle, and its running is true only when that was within ${SHADOW_AI_SILENT_AFTER} of the answer. ${SHODAN_OWNERSHIP}`;
+const RADAR_SHADOW_AI_FIELDS = `shadow_ai: the result is regrouped by what each number counts. shadow_ai.confirmed_exposed counts services EchelonGraph's probes found answering without an authentication gate (liveness active, or rechecking during a re-check): confirmed_exposed.total is the sum of confirmed_exposed.by_category, and confirmed_exposed.last_24h counts those first recorded in the last 24 h. Of the shadow_ai numbers, only confirmed_exposed counts exposed services. confirmed_exposed.window.from and confirmed_exposed.window.to are timestamps, not counts: when EchelonGraph's verifier ran the probe that last decided the oldest and the newest of those services, a span of probes made at different times; with one that has no such time there is no window, and confirmed_exposed.dated_window.from and confirmed_exposed.dated_window.to span the dated ones only, while confirmed_exposed.dated_window.undated counts those with none. shadow_ai.observed counts every Certificate Transparency or Shodan observation on record, whatever its verification state: its numbers are observed, not exposed. They are observed.total; observed.by_category (the same observations by category); observed.last_24h (those first recorded in the last 24 h); observed.trend_30d (observations per UTC day over the last 30 days); and observed.top_products, observed.top_countries and observed.top_issuers (up to ten products, countries and issuers ranked by observations, where an issuer is the certificate's CA for a Certificate Transparency observation and the hosting operator Shodan reports for a Shodan one). shadow_ai.authentication counts observations by probe outcome: authentication.observed where a probe observed an authentication gate (a 401/403, a login page or an auth marker), and authentication.not_determined where the service answered but no probe could tell. Neither authentication count is part of confirmed_exposed, and observed.total minus confirmed_exposed.total is not a count of secured services. The shadow-AI poller block carries only running and last_run_at: last_run_at is when the radar's leader last completed a Certificate Transparency (crt.sh) cycle, and its running is true only when that was within ${SHADOW_AI_SILENT_AFTER} of the answer. ${SHODAN_OWNERSHIP}`;
 const RADAR_MCP_FIELDS = `mcp_servers: counts and timestamps only, no hostname. mcp_servers.total counts hostnames the AI-exposure radar has checked for an MCP server, each once by its latest verdict on record, and not every one is an MCP server; EchelonGraph's own control servers are left out, and mcp_servers.own_controls_excluded counts them; hostnames whose owner opted out of scanning are not checked again while the opt-out stands, so their last verdict is left out too, and mcp_servers.withheld_opted_out counts them. mcp_servers.total is mcp_servers.protected plus mcp_servers.pending_readjudication plus mcp_servers.not_assessed. mcp_servers.protected counts hostnames whose /mcp endpoint asked for credentials and whose OAuth protected-resource metadata validated under RFC 9728; mcp_servers.prm_via divides them by where that document was found: mcp_servers.prm_via.header, mcp_servers.prm_via.wellknown_path and mcp_servers.prm_via.wellknown_root. mcp_servers.pending_readjudication counts verdicts of a rule since replaced, not yet re-checked. mcp_servers.not_assessed counts the rest, whose protection the radar could not assess (not assessed does not mean unprotected), and mcp_servers.not_assessed_by_reason puts each in one bucket. mcp_servers.not_assessed_by_reason.identified_no_challenge holds servers that identified themselves as MCP servers and did not ask for credentials at the handshake. That is normal in MCP: authorization is optional in the spec, and a server can enforce it at tools/call instead, which EchelonGraph never sends, so this bucket is not a finding of exposure. ${MCP_CHALLENGE_REASON_FIELDS} hold endpoints that asked for credentials but whose RFC 9728 metadata did not validate, by why, so none of them is shown to lack protection; mcp_servers.not_assessed_by_reason.challenge_unadjudicated holds endpoints that asked for credentials before that check existed, not yet re-checked. mcp_servers.not_assessed_by_reason.no_http_answer holds hostnames that gave no HTTP answer, and mcp_servers.not_assessed_by_reason.not_identified_as_mcp hostnames whose HTTP answer identified no MCP server. mcp_servers.era divides every counted hostname by protocol era: mcp_servers.era.legacy; mcp_servers.era.dual, a lower bound; mcp_servers.era.modern, not proven modern-only; mcp_servers.era.unknown; and mcp_servers.era.not_measured, recorded before the era probe and not re-checked since. mcp_servers.transport divides them by transport: mcp_servers.transport.streamable_http, mcp_servers.transport.legacy_sse, mcp_servers.transport.unknown and mcp_servers.transport.not_measured. mcp_servers.window.from and mcp_servers.window.to are when the oldest and the newest of the verdicts counted were last checked. mcp_servers.last_run_at is a timestamp, not a count: when the AI-exposure radar, which checks other AI services too, last completed a check; mcp_servers.enabled is whether one completed within ${MCP_ENABLED_WITHIN} of the answer, and mcp_servers.counted_at is when the API read the counts. A partition whose buckets do not add up to the count it divides is left out and named; an answer that does not say it is the MCP-server counts, or whose mcp_servers.total, mcp_servers.protected, mcp_servers.pending_readjudication and mcp_servers.not_assessed are missing or contradict each other, is a failure.`;
 // exposure_radar's envelope. Every radar answered, but no stats answer says when the services
 // or records it counts were observed: each count covers everything that radar still holds on
@@ -2226,10 +2407,191 @@ const SUCCESS_STATE = "measured: a measurement of what was asked; an exposure co
 const DATA_TRUNCATED_FIELD = "false: data is the answer whole. true: the structured result would pass 30,000 characters of JSON with data whole, so data is cut (DATA CUT): the entries of some of its lists keep only some of their fields, or the lists only some of their entries, truncated gives each, and no string is shortened. The same call with full: true returns data whole.";
 const TRUNCATED_FIELD = "Present when data_truncated is true: each list of data that was cut, by its path in data (a dot between the names of an object and a list inside it), with total, its entries in the answer, returned, the entries data holds, and thinned, true when each of them keeps only some of its fields.";
 const TRUNCATED = z.record(z.string(), z.strictObject({ total: z.number().int().min(0), returned: z.number().int().min(0), thinned: z.literal(true).optional() }));
+// #3121: the success branch is published open to fields it does not name, and this server holds
+// its own answers to the closed one (STRICT, read by checked). Through 3.0.0 both branches were
+// closed (additionalProperties false), and a client validates against the outputSchema it listed,
+// which the hosted endpoint never tells it to list again (stateless, listChanged false): a Claude
+// Code session that listed the tools under 2.7.2 failed its first check_sbom call once 3.0.0 went
+// live, "Structured content does not match the tool's output schema: data must NOT have additional
+// properties" (ajv's root is "data"; 3.0.0 added data_truncated and truncated to every success),
+// until it reconnected. So a field added beside them in a minor release would break every such
+// session too, against the README's semver promise. Opening the success branch keeps such a field
+// additive for a client holding an older list; the failure branch stays closed (a failure is never
+// read as data), and data keeps each tool's own schema. The suite validates answers against the
+// closed branch (test/strict-output.mjs), and checked() does here, so a field this server adds
+// without naming it in the schema still fails, as it did when the branch was closed.
+//
+// 3.0.2: every output schema is built once per process, and its strict copy with it. The hosted
+// endpoint builds a server for each request (http.ts: createMcpHandler's stateless leg calls
+// createServer), and through 3.0.1 the tool modules that take envelopeSchema from this file
+// (check_affected, check_sbom, epss_history, kev_recent, scan_manifest and the three vendor-advisory
+// tools) built their output schemas in their register functions, so once per request in flight.
+// 3.0.1's strict copy doubled those: 1,371 KB of heap per server, against 3.0.0's 1,168
+// (64 servers held at once, node --expose-gc). test/http-memory.test.mjs's "served as they come"
+// case holds 64 requests in flight beside two 5,000,000-character SBOMs; it failed the 3.0.1
+// release run at Dockerfile.http's 128 MiB, and passed here only at 128, where 3.0.0 passes at
+// 112. At 112 V8 aborted 3.5 s in, with 59 servers live and both documents still at their first
+// batches, so before either answer was cut (a heap snapshot near the limit). Each such module now
+// keeps its schemas per envelopeSchema, as cve_intel, cve_remediation and get_cwe already did
+// (schemasOnce): 611 KB a server, and the case passes at --max-old-space-size=80.
+//
+// #3268: and every level of the success branch is published open, not only its root. #3121 opened
+// the root alone: 3.0.2 still published 86 objects below it with additionalProperties false (40 in
+// data, among them exposure_radar's and cve_intel's data itself, 23 in coverage, 7 in freshness, 16
+// in truncated) and 12 string enums with no fallback (scan_manifest's manifest.files[].format and
+// not_checked[].reason, exposure_radar's newest_kev[].exposure_state among them). A field added
+// under any of them, or a value added to any of them, fails a client holding the older list the
+// same way, and 2.6.3 and 2.7.0 had each added such fields. So the JSON Schema a client is served
+// (tools/list, through the SDK's ~standard.jsonSchema.output) is the one zod builds, with every
+// object of the success branch open (additionalProperties {}, as z.looseObject publishes it) and
+// every string enum or const in it open as each tool's open enums already are (anyOf: the known
+// values, or any string), the values still listed: openSuccess, in one place here rather than at
+// each schema. `state` stays closed: it is what tells a success from a failure. The failure branch
+// is left as built, closed at every level (#3121's decision). What this server holds its own
+// answers to is unchanged: checked() reads STRICT, closed wherever its tool closed it, and so does
+// the suite (closedOutputSchema, test/strict-output.mjs). The opened schema is built once per
+// process and target and shared, frozen, by every server (each HTTP request's included), so it adds
+// nothing per request: the SDK asks for it each time it registers a tool on a server and for each
+// tools/list, and is handed the same object, where zod built a new one each time before.
+// test/open-success.test.mjs walks every tool's tools/list answer for any closed object or enum in a
+// success branch, with controls, and test/schema-compat.mjs compares a candidate with the last
+// release.
+const STRICT = new WeakMap();
+// Every envelope built in this process (16, one a tool, each built once), for closedOutputSchema.
+const ENVELOPES = new Set();
 export function envelopeSchema(o) {
+    const published = envelopeOf(o, z.looseObject);
+    STRICT.set(published, envelopeOf(o, z.strictObject));
+    publishOpen(published);
+    ENVELOPES.add(published);
+    return published;
+}
+const standardOf = (s) => s["~standard"];
+// The target the SDK converts every outputSchema with (standardSchemaToJsonSchema).
+const OUTPUT_TARGET = "draft-2020-12";
+// The published schema's JSON Schema output, opened by openSuccess, made once per target and shared.
+function publishOpen(published) {
+    const std = standardOf(published);
+    const made = new Map();
+    const output = (o) => {
+        if (o?.libraryOptions)
+            return openSuccess(std.jsonSchema.output(o));
+        let json = made.get(o?.target);
+        if (!json)
+            made.set(o?.target, (json = deepFreeze(openSuccess(std.jsonSchema.output(o)))));
+        return json;
+    };
+    Object.defineProperty(published, "~standard", {
+        value: { ...std, jsonSchema: { ...std.jsonSchema, output } },
+        configurable: true,
+        writable: true,
+        enumerable: false,
+    });
+}
+const isNode = (x) => x !== null && typeof x === "object" && !Array.isArray(x);
+const isSuccessBranch = (b) => {
+    const values = isNode(b) && isNode(b.properties) && isNode(b.properties.state) ? b.properties.state.enum : undefined;
+    return Array.isArray(values) && values.includes("measured");
+};
+// A string enum or const: one value of a list, or the one value.
+const isClosedEnum = (n) => (Array.isArray(n.enum) && n.enum.length > 0 && n.enum.every((v) => typeof v === "string")) || typeof n.const === "string";
+// { type: "string" } and nothing else that constrains it: the fallback of an open enum.
+const isAnyString = (n) => isNode(n) && n.type === "string" && Object.keys(n).every((k) => k === "type" || k === "description");
+// `json` with each success branch (state measured or not_assessed) open at every level: each object
+// admits properties it does not name, and each string enum or const admits any string, its values
+// kept as the first branch of an anyOf. A branch's own `state` is left closed, and so is every
+// failure branch. Edits `json` in place, which zod made for this call.
+//
+// The envelope's `coverage` and `freshness` slots too: a tool built with neither (envelopeOf's
+// z.null()) published { type: "null" } there, 13 freshness slots and 2 coverage slots (cve_summary,
+// get_cve) after #3276 gave cve_summary's freshness an object. A client holding such a list refuses
+// the object a later release puts in the slot, as 3.0.2's clients refuse cve_summary's freshness
+// (#3276) and epss_history's coverage fields. So a success branch publishes each null-only slot as
+// null or an open object (OPEN_SLOT). Nothing it answers changes: checked() and the suite still hold
+// the slot to null (STRICT), so this server sends null there until a change gives the slot a schema.
+// The failure branch keeps its null.
+const OPEN_SLOTS = ["coverage", "freshness"];
+const OPEN_SLOT = () => [{ type: "object", additionalProperties: {} }, { type: "null" }];
+const onlyNull = (n) => isNode(n) && n.type === "null" && ["anyOf", "oneOf", "allOf", "enum", "const"].every((k) => n[k] === undefined);
+export function openSuccess(json) {
+    for (const k of ["oneOf", "anyOf"]) {
+        const branches = json[k];
+        if (!Array.isArray(branches))
+            continue;
+        for (const b of branches) {
+            if (!isSuccessBranch(b))
+                continue;
+            openNode(b, true);
+            const props = b.properties;
+            for (const slot of OPEN_SLOTS) {
+                const n = props[slot];
+                if (!onlyNull(n))
+                    continue;
+                const { type: _type, ...rest } = n;
+                props[slot] = { anyOf: OPEN_SLOT(), ...rest };
+            }
+        }
+    }
+    return json;
+}
+function openNode(n, isBranch = false) {
+    if (n.additionalProperties === false)
+        n.additionalProperties = {};
+    else if (isNode(n.additionalProperties))
+        n.additionalProperties = openNode(n.additionalProperties);
+    for (const k of ["properties", "patternProperties", "$defs", "definitions"]) {
+        const m = n[k];
+        if (isNode(m))
+            for (const [name, s] of Object.entries(m))
+                if (isNode(s) && !(isBranch && k === "properties" && name === "state"))
+                    m[name] = openNode(s);
+    }
+    for (const k of ["items", "propertyNames", "contains", "not", "if", "then", "else"])
+        if (isNode(n[k]))
+            n[k] = openNode(n[k]);
+    for (const k of ["anyOf", "oneOf", "allOf", "prefixItems"]) {
+        const list = n[k];
+        if (!Array.isArray(list))
+            continue;
+        // An enum already beside a plain string (z.union([z.enum(...), z.string()])) is open as it is.
+        const open = k === "anyOf" && list.some(isAnyString);
+        n[k] = list.map((s) => (!isNode(s) || (open && isClosedEnum(s)) ? s : openNode(s)));
+    }
+    if (!isClosedEnum(n))
+        return n;
+    const { type: _type, enum: values, const: one, ...rest } = n;
+    const known = values !== undefined ? { type: "string", enum: values } : { type: "string", const: one };
+    const anyOf = [known, { type: "string" }];
+    return rest.anyOf === undefined ? { ...rest, anyOf } : { ...rest, allOf: [...(rest.allOf ?? []), { anyOf }] };
+}
+function deepFreeze(x) {
+    if (x !== null && typeof x === "object" && !Object.isFrozen(x)) {
+        for (const v of Object.values(x))
+            deepFreeze(v);
+        Object.freeze(x);
+    }
+    return x;
+}
+// For the suite (test/strict-output.mjs): the closed JSON Schema this server holds its own answers
+// to (STRICT, as checked() reads it) for `published`, an outputSchema as tools/list serves it, or
+// undefined when no envelope of this process publishes it. Every tool's envelope is built by its
+// first registration, so call createServer() once before.
+export function closedOutputSchema(published) {
+    if (!isNode(published))
+        return undefined;
+    const want = JSON.stringify(published.oneOf);
+    for (const e of ENVELOPES) {
+        if (JSON.stringify(standardOf(e).jsonSchema.output({ target: OUTPUT_TARGET }).oneOf) !== want)
+            continue;
+        const strict = STRICT.get(e);
+        return strict ? { type: "object", ...standardOf(strict).jsonSchema.output({ target: OUTPUT_TARGET }) } : undefined;
+    }
+    return undefined;
+}
+function envelopeOf(o, success) {
     const coverage = o.coverage ? o.coverage.nullable() : z.null();
     return z.discriminatedUnion("state", [
-        z.strictObject({
+        success({
             state: z.enum(["measured", "not_assessed"]).describe(SUCCESS_STATE),
             measured_at: Instant.nullable().describe("When the underlying observation was made, as the API states it; null when the answer does not say or holds no observation."),
             method: z.string().describe("How the numbers were produced."),
@@ -2275,8 +2637,8 @@ const CPE_CONFIGURATIONS_DESCRIPTION = "NVD's configurations array as NVD sent i
 // templates, internal/cve/fix_statement.go). The last two are the record's own words: get_cve
 // relays the solution's sentence as cna_solution, and the description is in the record.
 // One constant string each (the site's tool-claims check folds only constant strings).
-const PATCH_EVIDENCE_LABELS = ["vendor_patch", "fixed_version", "release_reference", "vendor_advisory_fix", "nvd_patch_reference", "cna_patch_reference", "cna_solution", "description_fix"];
-const PATCH_EVIDENCE_SOURCES = "vendor_patch (a vendor patch on record, from Ubuntu or Red Hat), fixed_version (a fixed version recorded for an affected package, or the fixed bound of an affected version range), release_reference (a reference that EchelonGraph confirmed through the GitHub API is a published release containing the fix, or a pull request or commit that a published release contains), vendor_advisory_fix (a vendor advisory that lists a fix for the CVE under the vendor's own structured category: Red Hat's CSAF vendor_fix, Microsoft's Vendor Fix), nvd_patch_reference (an NVD reference tagged Patch), cna_patch_reference (a reference the CVE's CNA tagged patch in its CVE record), cna_solution (a sentence of the CVE record's solutions, written by its CNA, that names a fixed version; relayed as cna_solution) and description_fix (a sentence of the CVE description that names a fixed version)";
+const PATCH_EVIDENCE_LABELS = ["vendor_patch", "fixed_version", "release_reference", "vendor_advisory_fix", "nvd_patch_reference", "cna_patch_reference", "cna_solution", "description_fix", "vendor_fix_released"];
+const PATCH_EVIDENCE_SOURCES = "vendor_patch (a vendor patch on record, from Ubuntu or Red Hat), fixed_version (a fixed version recorded for an affected package, or the fixed bound of an affected version range), release_reference (a reference that EchelonGraph confirmed through the GitHub API is a published release containing the fix, or a pull request or commit that a published release contains), vendor_advisory_fix (a vendor advisory that lists a fix for the CVE under the vendor's own structured category: Red Hat's CSAF vendor_fix, Microsoft's Vendor Fix), nvd_patch_reference (an NVD reference tagged Patch), cna_patch_reference (a reference the CVE's CNA tagged patch in its CVE record), cna_solution (a sentence of the CVE record's solutions or workarounds, written by its CNA, that names a fixed version; relayed as cna_solution), description_fix (a sentence of the CVE description that names a fixed version) and vendor_fix_released (the vendor states, in the CVE record, that a fix is released and the record names no fixed version; check the vendor's advisory)";
 // #3070, #3076: what the CVE record's CNA wrote, as GET /cves/:id serves it (core-backend
 // cna_record.go). One constant string each.
 const CVE_CNA_ABSENT = "Absent where EchelonGraph has not read the CVE record's CNA container yet, where the record has none, for a REJECTED CVE, and from an API older than the field.";
@@ -2284,12 +2646,26 @@ const DATE_PUBLIC_FIELD = "When the vulnerability was made public, as the CVE re
     CVE_CNA_ABSENT;
 const DATE_PUBLIC_SOURCE_FIELD = "Whose date date_public is: cna, the CVE record's CNA. Absent whenever date_public is.";
 const CNA_FIELD = "The CNA that wrote the CVE record: short_name as the record gives it, and name, the CVE Program's name for that CNA (the short name where its list does not hold it). " + CVE_CNA_ABSENT;
-const CNA_SOLUTION_FIELD = "The sentence of the CVE record's solutions, written by its CNA, that names a released fix, verbatim: what makes cna_solution patch evidence. It is the CNA's text, not EchelonGraph's advice. Absent where the record's solutions name no fixed version, as well as where the field itself is: " +
+const CNA_SOLUTION_FIELD = "The sentence of the CVE record's solutions or workarounds, written by its CNA, that names a released fix, verbatim: what makes cna_solution patch evidence. It is the CNA's text, not EchelonGraph's advice. cna_solution_section says which of the two sections it is. Absent where the record's solutions name no fixed version, as well as where the field itself is: " +
     CVE_CNA_ABSENT;
+// #3178: which section cna_solution is. MCP relays a field its outputSchema does not describe without saying what it
+// is, so the section is described here, beside the sentence.
+const CNA_SOLUTION_SECTION_FIELD = "Which section of the CVE record cna_solution was read from: solution (the record's solutions) or workaround (its workarounds, read only where its solutions name no fix: a temporary measure the CNA lists beside its fix). A workaround's sentence is the record's workaround, never its solution. Present whenever cna_solution is; absent from an API older than the field.";
 // #2842: what the descriptions say; the sources, and that patch_available once true is never set
 // back, are the outputSchema's (PATCH_AVAILABLE_FIELD, PATCH_EVIDENCE_FIELD).
-const PATCH_AVAILABLE_DESCRIPTION = "patch_available is true when EchelonGraph holds evidence of a fix for the CVE, and patch_evidence names its sources, strongest first. patch_available false means no fix evidence is on record, which is not a finding that no fix exists.";
-const PATCH_AVAILABLE_FIELD = "true: EchelonGraph holds evidence of a fix for the CVE, its sources named in patch_evidence. false: no fix evidence is on record, which is not a finding that no fix exists. Once true it is never set back to false. An answer with no patch_evidence (an API older than that field) does not name the evidence, and a false there is not a finding that no fix exists either.";
+const PATCH_AVAILABLE_DESCRIPTION = "patch_available is true when EchelonGraph holds, or once held, fix evidence for the CVE; patch_evidence is what it holds now, strongest first. patch_available false means no fix evidence is on record, which is not a finding that no fix exists.";
+// #3138: true says evidence was held at some point, not that it is held now: the sources held now
+// are patch_evidence's, and true beside an empty one is a withdrawal (requiredText.ts
+// PATCH_AVAILABLE_WITHDRAWN, pinned there). #3138's review: round 1 changed the field text only,
+// and this sentence, in get_cve's and search_cves' descriptions, still said true means
+// EchelonGraph holds evidence; it now says "holds, or once held", in 9 more characters than it
+// had, as get_cve's description had 9 left under #2924's headroom of 100 below the 2,048 cut
+// (get_cve 1,948 characters, search_cves 1,807; test/prompts-resources.test.mjs holds the
+// headroom, test/client-cut.mjs (b) the cut, and marketing-site lib/mcpToolClaims.test.ts the
+// word "for" in get_cve's description, which its /pulse/mcp row uses).
+const PATCH_AVAILABLE_FIELD = "true: EchelonGraph holds, or once held, evidence of a fix for the CVE; patch_evidence names the sources it holds now. " +
+    PATCH_AVAILABLE_WITHDRAWN +
+    " false: no fix evidence is on record, which is not a finding that no fix exists. An answer with no patch_evidence (an API older than that field) does not name the evidence, and a false there is not a finding that no fix exists either.";
 const PATCH_EVIDENCE_FIELD = "The sources of the fix evidence EchelonGraph holds for the CVE, strongest first: " +
     PATCH_EVIDENCE_SOURCES +
     ". Empty where none was found when EchelonGraph last computed it. Absent (an API older than the field): the answer does not name the evidence.";
@@ -2305,6 +2681,13 @@ const KEV_NOTES_URLS_FIELD = "The https links in CISA's notes for the CVE, in CI
 // #2841: what get_cve's remediation is. One constant string (the site's tool-claims check folds
 // only constant strings).
 const REMEDIATION_SUMMARY_FIELD = "A capped summary (at most 1,500 characters of JSON) of how the CVE is fixed, as its sources state it: fix_status first (the API's fix-status rule: state, basis, described_by, solution_by, stated_in_record, listed_in_patch_table and unread_inputs), vendor_remediation_kinds (per kind, the vendor advisories listing one for this CVE, by the vendor's own category), vendor_advisories, vendors_not_parsed, kev_required_action (CISA's, verbatim), fixed_branches_count, fixed_versions (per package, fixed versions on record), fix_references (URLs tagged Patch or Mitigation by NVD, or patch or mitigation by the CNA), failed_sections, truncated, and see, the name of the tool that returns the whole, with each text. A kind missing from vendor_remediation_kinds is not a finding that no such remediation exists. Absent for a REJECTED CVE and from an API older than the field.";
+// #2879: the scorer's three components (core-backend scoring v4.0, components.go), which GET
+// /cves/:id serves at the top level. One constant string each (the site's tool-claims check folds
+// only constant strings). eg_likelihood is FIRST's EPSS until EchelonGraph's calibrated model
+// (#2874) replaces it, and says so: it is never presented as EchelonGraph's own probability.
+const EG_SEVERITY_FIELD = "Impact severity alone (scorer v4.0): the CVSS base score from the best-provenance CVSS EchelonGraph holds, which no CISA KEV listing, EPSS probability or EG-KEV tier raises. score (0-10) and severity (the CVSS band), with metric cvss_base, cvss_version, vector, source and provider. assessed false, with score and severity null and unassessed_reason, where no CVSS of any version is published: kev_listed_no_cvss reads exploited, severity not yet published. Absent from a record scored before v4.0.";
+const EG_LIKELIHOOD_FIELD = "A probability with a horizon (scorer v4.0): probability is FIRST's EPSS probability of exploitation activity in the next 30 days (source first_epss, horizon_days 30, with epss_percentile, epss_score_date and epss_model_version where stored), not EchelonGraph's own model. null, with null_reason no_epss_on_record, where no EPSS is on record: the likelihood is unknown, not low. exploited (true when CISA KEV lists the CVE or EG-KEV rates it Tier 1) and exploited_sources report confirmed exploitation apart from it; it is never folded into probability. Absent from a record scored before v4.0.";
+const EG_PRIORITY_FIELD = "The decision (scorer v4.0): ssvc, the decision CISA's SSVC table gives as EchelonGraph applies it (decision at medium mission impact, as echelongraph_ssvc_decision, and by_mission), null with null_reason not_assessed for a CVE EchelonGraph has not assessed; bod_26_04, CISA BOD 26-04's timeline if_publicly_exposed and if_not_publicly_exposed (CERT/CC's keys 3DF, 3D, 14D, 60D, FSU); inputs, kev, exploitation, automatable and technical_impact, each with its source. Absent from a record scored before v4.0.";
 const CVERecord = z.looseObject({
     cve_id: opt(z.string()),
     description: opt(z.string()),
@@ -2313,15 +2696,38 @@ const CVERecord = z.looseObject({
     cvss_v4_score: opt(z.number()),
     cvss_v4_severity: opt(z.string()),
     // #2535: the score is a score only beside score_assessed true (see cveScoreNote).
-    echelongraph_score: opt(z.number()).describe("EchelonGraph's 0-10 score for the CVE: a score only when score_assessed is true. With score_assessed false it is a placeholder, not a rating."),
+    // #2879: what the number is, since the scorer publishes the impact severity apart (eg_severity).
+    echelongraph_score: opt(z.number()).describe("EchelonGraph's 0-10 score for the CVE: severity, escalated by confirmed exploitation (a CISA KEV listing floors it at 9.0) and lifted toward 9.0 by EPSS; eg_severity is the impact severity alone. A score only when score_assessed is true. With score_assessed false it is a placeholder, not a rating."),
     echelongraph_severity: opt(z.string()).describe("The severity band of echelongraph_score: a rating only when score_assessed is true. With score_assessed false it is a placeholder (NONE)."),
-    echelongraph_risk: opt(z.number()).describe("EchelonGraph's 0-100 risk priority, fused from the score, exploitation and automatability: a rating only when score_assessed is true. With score_assessed false it is a placeholder."),
+    echelongraph_risk: opt(z.number()).describe("EchelonGraph's 0-100 risk priority, fused from impact severity (eg_severity, from scorer v4.0; the score before it), exploitation and automatability, with EchelonGraph's hand-set weights: a rating only when score_assessed is true. With score_assessed false it is a placeholder."),
+    // #2879: the three components, relayed as the API sends them (componentsNote words them).
+    eg_severity: opt(z.looseObject({
+        assessed: opt(z.boolean()),
+        score: opt(z.number()),
+        severity: opt(z.string()),
+        source: opt(z.string()),
+        provider: opt(z.string()),
+        unassessed_reason: opt(z.string()),
+    })).describe(EG_SEVERITY_FIELD),
+    eg_likelihood: opt(z.looseObject({
+        probability: opt(z.number()),
+        null_reason: opt(z.string()),
+        horizon_days: opt(z.number()),
+        source: opt(z.string()),
+        exploited: opt(z.boolean()),
+        exploited_sources: opt(z.array(z.string())),
+    })).describe(EG_LIKELIHOOD_FIELD),
+    eg_priority: opt(z.looseObject({
+        ssvc: opt(z.looseObject({ decision: opt(z.string()), mission: opt(z.string()) })),
+        bod_26_04: opt(z.looseObject({ if_publicly_exposed: opt(z.array(z.string())), if_not_publicly_exposed: opt(z.array(z.string())) })),
+        inputs: z.unknown().optional(),
+    })).describe(EG_PRIORITY_FIELD),
     score_confidence: opt(z.string()).describe("How confident EchelonGraph is in its score: NONE when score_assessed is false."),
     score_assessed: opt(z.boolean()).describe("Whether EchelonGraph has scored the CVE. true: echelongraph_score, echelongraph_severity and echelongraph_risk are its score. false: the CVE is NOT YET SCORED, not scored 0, and any of those three it carries is a placeholder, not a rating; the API may leave them out. Absent (an API older than the field): the answer does not say whether the CVE was scored."),
     score_unassessed_reason: opt(z.string()).describe("Why score_assessed is false: no_signal, no source has yet published severity data EchelonGraph can score; or rejected, the record was withdrawn by its numbering authority and is never scored. Absent when the CVE is scored."),
     // #2880: the SSVC decision, and CISA BOD 26-04's timeline (bodNote words it in the note).
     echelongraph_ssvc_decision: opt(z.string()).describe("The SSVC decision (Act, Attend, Track* or Track) EchelonGraph computes with CISA's decision table at medium mission impact. CISA publishes the table and, for some CVEs, its inputs, not a decision for a CVE. score_factors.ssvc gives the decision at low, medium and high mission impact, with each input and its source."),
-    score_factors: z.unknown().optional().describe("EchelonGraph's evidence for its score. ssvc: the SSVC decision at every mission impact level, each input with its source. bod_26_04 (scorer v3.4 and later): CISA BOD 26-04's remediation timeline, if_publicly_exposed and if_not_publicly_exposed, each a list of CERT/CC's keys (3DF, 3D, 14D, 60D, FSU) named in timelines, with kev, automatable and technical_impact, each with its source; source cisa_bod_26_04_default is CISA's own default for a CVE not in KEV that nobody has assessed."),
+    score_factors: z.unknown().optional().describe("EchelonGraph's evidence for its score. ssvc: the SSVC decision at every mission impact level, each input with its source. bod_26_04 (scorer v3.4 and later): CISA BOD 26-04's remediation timeline, if_publicly_exposed and if_not_publicly_exposed, each a list of CERT/CC's keys (3DF, 3D, 14D, 60D, FSU) named in timelines, with kev, automatable and technical_impact, each with its source; source cisa_bod_26_04_default is CISA's own default for a CVE not in KEV that nobody has assessed. eg_severity, eg_likelihood and eg_priority (scorer v4.0): the same objects as the record's top-level fields. eg_risk.severity_source (v4.0): what EG Risk's severity term read, eg_severity, vendor_severity, or unknown_kev_most_urgent (no severity published for a CISA KEV CVE, so the most urgent value)."),
     epss_score: opt(z.number()),
     epss_percentile: opt(z.number()),
     kev_listed: opt(z.boolean()),
@@ -2340,6 +2746,8 @@ const CVERecord = z.looseObject({
     date_public_source: opt(z.string()).describe(DATE_PUBLIC_SOURCE_FIELD),
     cna: opt(z.looseObject({ short_name: opt(z.string()), name: opt(z.string()) })).describe(CNA_FIELD),
     cna_solution: opt(z.string()).describe(CNA_SOLUTION_FIELD),
+    // #3178: a section the API adds later is relayed, never a failed call (as patch_evidence's labels).
+    cna_solution_section: opt(z.union([z.enum(["solution", "workaround"]), z.string()])).describe(CNA_SOLUTION_SECTION_FIELD),
     references: z.unknown().optional(),
     // #2720: NVD's configurations, losslessly, beside the flat list (see cpeConfigurationsNote).
     cpe_match: z.unknown().optional().describe(CPE_MATCH_DESCRIPTION),
@@ -2361,6 +2769,18 @@ const SUMMARY_NVD_FIELDS = "summary.nvd_critical, summary.nvd_high, summary.nvd_
 // outputSchema's, names each counter and says what is left out.
 const SUMMARY_POLLER_HEAD = "poller holds the in-memory counters of the NVD poller of the one API instance that answered, counted since that instance last started and zeroed on every restart: they describe that instance, never the feed's size, intake, reliability or freshness. Whenever the answer carries poller the note says so.";
 const SUMMARY_POLLER_DESCRIPTION = "poller holds the in-memory counters of the NVD poller of the one API instance that answered (cves_ingested, cves_skipped, http_retries, poll_count, poll_errors, last_poll_at, last_poll_dur_ms, interval), counted since that instance last started and zeroed on every restart: they describe that instance, never the feed's size, intake, reliability or freshness. Whenever the answer carries poller the note says so. A poller field the answer sends in a JSON type other than the one described here is left out of data and named in the note, and a poller that is neither a JSON object nor null is left out whole: summary is relayed either way.";
+// #3276: what data.nvd_poll is, and cve_summary's freshness, which relays it (nvdPollFreshness). A
+// constant string, as every schema text here is; its 5 minutes are NVD_POLL_SKEW_MS.
+const NVD_POLL_DATA_FIELD = "When the fleet of API instances last completed an NVD poll: last_completed_at (RFC 3339; the end of the last window fetched and stored without an error), scope fleet, and interval, the poll's interval. The answer leaves it out where that time is unknown. freshness.nvd_poll relays it where scope is fleet and last_completed_at is a real RFC 3339 time at most 5 minutes after this server's clock.";
+const NVD_POLL_FRESHNESS = z.strictObject({
+    nvd_poll: z
+        .strictObject({
+        last_run_at: Instant.describe("data.nvd_poll.last_completed_at as the API sent it: the end of the window the fleet's last completed NVD poll stored, whichever API instance ran it; never the answering instance's poller.last_poll_at."),
+        scope: z.literal("fleet").describe("Whose poll it is: the fleet's, as data.nvd_poll.scope says."),
+        interval: z.string().nullable().describe("data.nvd_poll.interval as the API sent it, a Go duration such as 20m0s: the interval the NVD poll runs at; null where the answer gives none in that form."),
+    })
+        .describe("The fleet's last completed NVD poll, from data.nvd_poll. freshness is null where the answer carries no nvd_poll, or one without such a time."),
+});
 // One of the NVD histogram's four labelled buckets (#2641).
 const nvdBand = (label) => opt(z.number()).describe(`Of the active CVEs total counts, those whose NVD CVSS severity label is ${label}: NVD's label, as provenance, never EchelonGraph's severity band.`);
 const CVE_SUMMARY_OUTPUT = envelopeSchema({
@@ -2404,9 +2824,24 @@ const CVE_SUMMARY_OUTPUT = envelopeSchema({
             .nullable()
             .optional()
             .describe(SUMMARY_POLLER_DESCRIPTION),
+        // #3276: the fleet's last completed NVD poll, which nvdPollFreshness reads into freshness. Its
+        // fields are named and described but untyped, and a block that is no object is admitted too:
+        // as #2771 holds for poller, one of another JSON type leaves freshness null and is relayed as
+        // sent, never a failed call.
+        nvd_poll: z
+            .union([
+            z.looseObject({
+                last_completed_at: z.unknown().optional().describe("When the fleet last completed an NVD poll, in RFC 3339: the end of the last window fetched and stored without an error."),
+                scope: z.unknown().optional().describe("Whose poll it is: fleet, every API instance's, never the answering instance's alone."),
+                interval: z.unknown().optional().describe("The poll's configured interval, a Go duration such as 20m0s."),
+            }),
+            z.unknown(),
+        ])
+            .optional()
+            .describe(NVD_POLL_DATA_FIELD),
     }),
     coverage: null,
-    freshness: null,
+    freshness: NVD_POLL_FRESHNESS,
 });
 const SEARCH_CVES_OUTPUT = envelopeSchema({
     data: z.looseObject({
@@ -2431,15 +2866,22 @@ const SEARCH_CVES_OUTPUT = envelopeSchema({
 });
 const GET_CVE_OUTPUT = envelopeSchema({ data: CVERecord, coverage: null, freshness: null });
 const CountryRows = z.array(z.looseObject({ country: opt(z.string()), hosts: opt(z.number()) }));
+// #3016: what each KEV flag is (requiredText.ts KEV_LISTED_DEPRECATED, which says why). The note
+// says what the record holds in words (exposureNote's kev sentence); these say it beside each field,
+// for a client that reads data alone. kev_catalog_listed is cves.kev_listed, which the KEV fetcher
+// sets only on a CVE row that exists, and the API answers false where there is none.
+const KEV_LISTED_FIELD = `${KEV_LISTED_DEPRECATED} ${KEV_OBSERVATION_FLAG}: false for a CISA-KEV CVE the radar holds no service for (CVE-2024-3400 on 2026-10-10: kev_listed false, kev_catalog_listed true). kev_catalog_listed is the catalog flag.`;
+const KEV_SEEN_FIELD = `true: at least one of the radar's service rows for the CVE carries the CISA-KEV flag copied in when the radar matched that service; false where none does, as for a CVE the radar holds no service for. ${KEV_OBSERVATION_FLAG}.`;
+const KEV_CATALOG_FIELD = `${KEV_CATALOG_FLAG} true when EchelonGraph's CVE record marks the CVE as CISA-KEV-listed. false also where EchelonGraph holds no record of the CVE, so a false says what EchelonGraph's data holds, not that the CVE is outside CISA's catalog.`;
 const CVE_EXPOSURE_OUTPUT = envelopeSchema({
     data: z.looseObject({
         cve_id: opt(z.string()),
         exposed_hosts: opt(z.number()),
         countries: opt(z.number()),
         tracked: opt(z.boolean()),
-        kev_listed: opt(z.boolean()),
-        kev_catalog_listed: opt(z.boolean()),
-        kev_seen_in_observations: opt(z.boolean()),
+        kev_listed: opt(z.boolean()).describe(KEV_LISTED_FIELD),
+        kev_catalog_listed: opt(z.boolean()).describe(KEV_CATALOG_FIELD),
+        kev_seen_in_observations: opt(z.boolean()).describe(KEV_SEEN_FIELD),
         ransomware: opt(z.boolean()),
         top_countries: opt(CountryRows),
         top_products: opt(z.array(z.looseObject({ product: opt(z.string()), hosts: opt(z.number()) }))),
@@ -2466,11 +2908,20 @@ const zRow = (spec) => z.strictObject({
 });
 // A relayed observation window (#2438): two instants, never a count.
 const Window = z.strictObject({ from: Instant, to: Instant });
+// The window over the dated rows only, beside how many rows carry no time (#2438, 2026-10-18):
+// relayed when undated is above 0, never as `window`.
+const DatedWindow = z
+    .strictObject({
+    from: Instant,
+    to: Instant,
+    undated: z.number().int().min(1).describe("How many of the rows the counts count have no observation time on record. from and to do not describe them."),
+})
+    .describe("Timestamps over the dated rows only, relayed when some counted rows carry no observation time: a span of observations made at different times, never one observation time and never a count.");
 const zRadar = (spec, rows = {}) => z.strictObject({
     ...Object.fromEntries(spec.counts.map((k) => [k, z.number().optional()])),
     ...Object.fromEntries(Object.entries(spec.rows).map(([k, rs]) => [k, (rows[k] ?? z.array(zRow(rs))).optional()])),
     ...Object.fromEntries(spec.instants.map((k) => [k, Instant.optional()])),
-    ...(spec.window ? { window: Window.optional() } : {}),
+    ...(spec.window ? { window: Window.optional(), dated_window: DatedWindow.optional() } : {}),
 });
 // A newest_kev row as newestKEVRow relays it: `tracked` is read, not relayed, and a count only
 // when the row's exposure_state is not not_assessed.
@@ -2485,7 +2936,7 @@ const CountMap = z.record(z.string(), z.number());
 const countRowsOf = (label) => z.array(z.strictObject({ [label]: z.string(), count: z.number() }));
 const ShadowAIData = z.strictObject({
     confirmed_exposed: z
-        .strictObject({ total: z.number().optional(), by_category: CountMap.optional(), last_24h: z.number().optional(), window: Window.optional() })
+        .strictObject({ total: z.number().optional(), by_category: CountMap.optional(), last_24h: z.number().optional(), window: Window.optional(), dated_window: DatedWindow.optional() })
         .optional(),
     observed: z
         .strictObject({
@@ -2573,11 +3024,19 @@ const CVE_ID_ARG = z.string().describe("a CVE ID, e.g. CVE-2023-44487");
 // What each description says about its structured result, naming only fields its schema holds.
 // #2842: the generic rule for the result's last text block is in the README and the methodology
 // resource, not in each description.
-const FEED_ENVELOPE = "Its freshness is null: the feed serves no poll-completion time.";
+// #3276: search_cves' and get_cve's. Through 3.0.2 it said "the feed serves no poll-completion
+// time", false since cve_summary's answer carries the fleet's last completed NVD poll (#3242). Its
+// length is the old one's: get_cve's description sits at the #2924 headroom floor.
+const FEED_ENVELOPE = "freshness is null: this answer carries no poll-completion time.";
 // #2771: cve_summary's own, since its data is the API's JSON less each poller field (or the whole
 // poller) summaryPollerShaped leaves out. Like SUMMARY_POLLER_DESCRIPTION it uses none of #2610's
 // six words ("any", "not", "rating", "scored", "source", "yet").
-const CVE_SUMMARY_ENVELOPE = "Its structured result's state is measured, with freshness null (the feed serves no poll-completion time) and data equal to the API's JSON less each poller field (or the whole poller) the note names as left out.";
+// #3276: freshness is the answer's nvd_poll (nvdPollFreshness). It replaces "The feed is polled from
+// its sources on a schedule; this is the state as of that update." too, which fit the #2924
+// headroom only with it gone; CVE_FEED_METHOD still says each source is polled on a schedule. Its
+// "from" is the one outside SUMMARY_NONE_DESCRIPTION that backs the /pulse/mcp row's "from" (the
+// site's #2610 control fails without it).
+const CVE_SUMMARY_ENVELOPE = "Its structured result's state is measured, with freshness.nvd_poll the fleet's last completed NVD poll and its interval, from the answer's nvd_poll (freshness null without one), and data equal to the API's JSON less each poller field (or the whole poller) the note names as left out.";
 // #2610: what cve_summary says summary.none is (summaryNoneNote), one constant string for the same
 // reason as SCORE_ASSESSED_DESCRIPTION below.
 const SUMMARY_NONE_DESCRIPTION = "summary.none is not a severity rating of None: it counts the active CVEs with no severity band from any source, that is, CVEs not yet scored, and the answer may carry the same count again as summary.unscored. Whenever summary.none is above zero the note says so, and names those CVEs not yet scored, not CVEs rated None.";
@@ -2598,9 +3057,14 @@ const TOOL_KIT = { api, succeeded, failed, badInput, crashed, checked, okHead, e
 // tools/list answers in registration order, which is the order below.
 export function createServer() {
     const server = new McpServer({ name: NAME, version: VERSION }, { instructions: INSTRUCTIONS, capabilities: { tools: { listChanged: false }, prompts: { listChanged: false }, resources: { listChanged: false } } });
+    // #3015: arguments that break a tool's inputSchema get badInput's envelope (state invalid_input,
+    // notes naming each argument and its rule), not the SDK's bare "Input validation error" text.
+    // Before the first registerTool, so every tool below and in src/tools/ is covered; tools/list's
+    // inputSchemas are unchanged (schemaRefusal.ts).
+    withSchemaRefusal(server, badInput);
     server.registerTool("cve_summary", {
         title: "CVE feed summary",
-        description: `Summary of EchelonGraph's CVE Pulse feed: summary.total active CVEs, their counts by severity band (summary.critical, summary.high, summary.medium, summary.low), the count with no band (summary.none), and summary.last_updated, the newest modification time among those records. ${SUMMARY_NONE_DESCRIPTION} ${SUMMARY_NVD_DESCRIPTION} ${SUMMARY_REJECTED_DESCRIPTION} ${SUMMARY_POLLER_HEAD} The feed is polled from its sources on a schedule; this is the state as of that update. ${CVE_SUMMARY_ENVELOPE} ${TEXT_BUDGET_DESCRIPTION}`,
+        description: `Summary of EchelonGraph's CVE Pulse feed: summary.total active CVEs, their counts by severity band (summary.critical, summary.high, summary.medium, summary.low), the count with no band (summary.none), and summary.last_updated, the newest modification time among those records. ${SUMMARY_NONE_DESCRIPTION} ${SUMMARY_NVD_DESCRIPTION} ${SUMMARY_REJECTED_DESCRIPTION} ${SUMMARY_POLLER_HEAD} ${CVE_SUMMARY_ENVELOPE} ${TEXT_BUDGET_DESCRIPTION}`,
         inputSchema: z.object({ full: FULL_ARG }),
         outputSchema: CVE_SUMMARY_OUTPUT,
         annotations: ANNOTATIONS,
@@ -2658,7 +3122,7 @@ export function createServer() {
     registerCveRemediation(server);
     registerGetCwe(server);
     // #2719: vendor_advisories_for_cve, get_vendor_advisory, search_vendor_advisories.
-    registerVendorAdvisoryTools(server, { api, failed, describeFailure, badInput, crashed, succeeded, checked, okHead, envelopeSchema, annotations: ANNOTATIONS });
+    registerVendorAdvisoryTools(server, { api, failed, describeFailure, badInput, failure, crashed, succeeded, checked, okHead, envelopeSchema, annotations: ANNOTATIONS });
     // #2722: prompts and resources, in prompts.ts and resources.ts. Both lists are fixed per
     // connection, so listChanged is false above.
     registerPrompts(server, { cveId: CVE_ID });