160-tool MCP server for real-time global intelligence from free public APIs: markets, liquidity, prediction markets, SEC filings, conflict, military, aircraft-cohort early warning, migration and border flows, cyber, climate, news and more. Dated observation history, 29 research prompts, cited briefs, geofences, SSE dashboard. MIT, no paid API keys.
Python ai-toolsai-watchanthropicclaudecybersecuritydashboardgeofencinggeopoliticalgeospatialintelligencemarketsmcpmigrationmilitarymodel-context-protocolnuclearosintreal-timespace-weatherthreat-intelligence
Merge feat/prediction-markets: Kalshi, cross-venue compare, settled Brier
Phoenix Agent (mac-studio)78deb8493836
diff --cc CHANGELOG.mdindex f66500c,a864ad0..f36dcd5--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -2,475 -2,46 +2,515 @@@## Unreleased+### Fixed: development runs no longer touch user databases+- Temporal and keyword spike databases now follow `XDG_CACHE_HOME` like+ the cache: `$XDG_CACHE_HOME/world-intel-mcp/temporal.db` and+ `$XDG_CACHE_HOME/world-intel-mcp/keyword_spikes.db`. With it unset, they+ remain in `~/.cache/world-intel-mcp/`. Users who set `XDG_CACHE_HOME`+ can keep existing baselines by moving these two files from+ `~/.cache/world-intel-mcp/` to `$XDG_CACHE_HOME/world-intel-mcp/`.+ Importing the package no longer opens databases; they open on first use.+- Apply per-source request spacing to every HTTP retry, including JSON,+ text, XML and binary fetches.++### Added: liquidity and money (Phase 29)+Keyless sources only: the FRED graph CSV (`fred.stlouisfed.org/graph/fredgraph.csv`,+allowed by robots.txt with `Crawl-delay: 1`, honored by a 1 s `fred-graph` rate+floor) and the ECB Data Portal (SDMX-JSON). Every point carries `observed_at`,+`value` and `units`; every series is typed `amount_outstanding`, `flow`,+`growth_rate`, `index` or `unknown` and carries a freshness block that flags data older than+its publication cadence allows (a served stale cache copy or an outage shows up+there). `published_at` is null: neither payload carries release dates, and the+responses say so. `limit=0` returns the full history.+- `intel_net_liquidity`: weekly Fed total assets (WALCL) minus Treasury General+ Account (WDTGAL) minus overnight reverse repo (RRPONTSYD), in USD billions.+ WALCL and WDTGAL are USD millions and are divided by 1,000; RRPONTSYD is already+ USD billions. One point per WALCL Wednesday; the TGA must be reported for that+ Wednesday; RRP comes from that day or, when blank on or after 2013-09-23,+ Tuesday only. Before that date a blank Wednesday has no fallback. Each point+ names the RRP date used. Weeks without aligned components are skipped and counted, never filled+ with zero, and a failed component makes the whole response an error. The TGA+ term is the Wednesday level (WDTGAL), not the week average (WTREGEN). A+ `method` block, returned with errors too, states each term's observation basis+ (WALCL and WDTGAL Wednesday levels in USD millions, RRPONTSYD daily in USD+ billions), its conversion, the RRP alignment and why WTREGEN is not used.+- `intel_liquidity_board`: latest reading and change vs the previous observation+ for the Fed balance sheet, TGA, RRP, net liquidity, US M2, euro area M1/M2/M3+ stocks and Eurosystem total assets, sortable by `biggest_move` or `newest`.+ `biggest_move` ranks absolute changes in billions of each row currency, with+ no FX conversion; observation horizons differ. Percentage changes do not+ affect ranking. A+ failed source becomes an `unavailable` row; net liquidity is dropped, not+ computed with a zero term, when any of its components fails. A `blocked` list+ names each measure not covered with its publisher and the status measured on+ 2026-10-17.+- `intel_money_supply`: US M2 (FRED M2SL) and euro area M1, M2 and M3 from the ECB+ BSI dataset (end-of-month stocks, monthly flows, annual growth rates), kept+ separate and never summed. US M3 is reported as discontinued (FRED M3SL ends at+ 2006-02-01).+- `intel_fed_liquidity_series`: WALCL, WDTGAL, WTREGEN, RRPONTSYD or M2SL with full+ history; blank source dates (2,833 for RRPONTSYD on 2026-10-17, 2,679 of them+ before 2013-09-23, when daily values begin) are counted, not read as zero.+- `intel_ecb_series`: any ECB BSI or ILM series by SDMX key, with units, scale,+ titles and provisional flags taken from the response. A growth rate's change is+ reported in points, not as a percent of a percent.+- Stale cache responses carry `served_from_stale_cache` and `cache_age_seconds`,+ and name the upstream failure in `data_gaps`. Only parsed bodies enter the cache.+ ECB 404 and empty responses are final no-data answers, without outage retries.+ Missing ECB roles and board rows are named; index bases, provisional status+ and percentage-point change units are retained. ECB keys must specify every+ dimension and request at most 50 series combinations.+- CLI: `intel liquidity`, `intel net-liquidity`, `intel money-supply`,+ `intel fed-liquidity`, `intel ecb-series`. Collector: `liquidity_board` and+ `net_liquidity` (group `liquidity`).+- Live reading 2026-10-17: net liquidity for Wednesday 2026-10-14 was+ USD 5,869.615 billion (WALCL 6,755,639 million, WDTGAL 885,823 million,+ RRPONTSYD 0.201 billion, all observed 2026-10-14).++Not added, measured 2026-10-17: ICI money market fund assets and ETF net issuance+(403 on every path, robots.txt included); FINRA margin statistics (the finra.org+Terms of Use, Restrictions d and e, forbid building a database from the site and+data mining, scraping or harvesting tools, robots included); BLS public API (keyless+v1 answers for CPI-U and payrolls, but api.bls.gov robots.txt disallows all paths+and the terms page answers 403). Fund flows and ETF net issuance therefore have no+source here, and no proxy is substituted for any of these measures.+### Added: news vs market reaction+- `intel_news_market_reaction` (CLI: `intel news-reaction`): the companies and+ countries named in recent story clusters, mapped to a listing (the entity+ table's ticker; a US ticker is annotated with its registrant when SEC's+ company_tickers.json lists it) or to the country's primary index (the table+ `intel_country_stocks` uses), with the move on the story's market session+ from Yahoo daily bars. Company rows give the stock's close-to-close return+ (adjusted closes), the benchmark's return over the same two dates (SPY for+ US listings, the exchange country's index otherwise) and the excess return;+ country rows give the index return and a z-score against its previous+ up-to-20 sessions.+- Session rule, stated in every response: the story time (earliest+ `published` in the cluster; that article also gives the headline and link)+ is converted to the exchange's timezone; before the regular close on a+ trading day it is that session, at or after the close the next one, and a+ weekend or holiday (read from the listing's own bars) maps to the next+ trading day. Each row names the close it used (`close_time_used`). A+ session that has not closed, or whose last bar Yahoo has not finalized+ (its regularMarketTime is before the close), is `pending`.+- Honest gaps: a failed quote, an expired cached chart or SEC file served+ during an outage, a missing benchmark bar, a stock series missing a day its+ benchmark traded (also between the two dates of a return), a cluster whose+ articles map to different sessions, a story timestamp later than the+ collection time and a story older than the bar range are each a `data_gap`+ row or line with the reason and no number, never a 0% move. A bar Yahoo+ fills for a day without trading (open, high, low and close equal to the+ previous close, no volume) is dropped, not read as a 0% session.+ `data_gaps` also names a listing whose Yahoo close differs from its zone's+ standard close, and a chart without adjusted closes. Stories whose earliest+ article is older than `max_age_hours` (default 168) are left out and+ counted. Unmapped names (companies without a ticker in the entity table,+ countries without an index) are listed, not dropped. Company names that are+ also common words (apple, amazon, meta, shell, bp, alphabet, chevron,+ samsung) are excluded with a stated reason unless the headlines carry a+ corroborating term or an article comes from a feed where the company sense+ dominates (a hyphen-joined use such as "meta-analysis" does not count); a+ phrase marking the other sense ("big apple", "amazon rainforest", "chevron+ ruling", "25 bp") excludes the name. A country gets an index row only when+ the headlines use its name; one named only by a demonym, capital or code,+ or inside a longer name such as "Gulf of Mexico", is listed as excluded.+ Responses say they describe same-session co-movement, not causation, and+ are not a trading signal. Tools 139 -> 140.++### Added: research guide over MCP (prompts and resources)+- The server now answers `resources/list`, `resources/read`, `prompts/list`+ and `prompts/get`, and advertises the resources and prompts capabilities+ at initialize. Before this it exposed tools only. No tools were added or+ changed.+- `intel://guide` (markdown): how to ask a strong question (period,+ comparison, measure, place), what an answer contains, what this server+ will not do, the worked prompts, and every registered tool grouped by+ domain module. Built from the live registry on every read; a test fails+ if a registered tool is missing or listed twice.+- `intel://guide/source-health` (JSON): open circuit breakers, stale+ serves, stale cache prefixes, cache freshness, and which keyed sources+ have their variables set (names only, never values). Reads in-process+ state and the cache database only; reading it starts no fetch. It says+ that breaker state covers this server process only. The keyed-source+ list is checked against the credentials `sources/*.py` actually read.+- `intel://guide/measures` (markdown): stock versus flow, growth versus+ acceleration, percentage points, seasonal adjustment, the three dates+ (observation, publication, collection), revisions, correlation and+ timing offsets, composite scores, missing data versus zero.+- 29 prompts across conflict, markets, hazards, migration, aviation, cyber,+ infrastructure, maritime, areas of interest, news, politics, sanctions,+ health, stored history and country views. Each names the tools to call+ and the limits to respect; arguments (country, topic, period and so on)+ are validated, and a missing, unknown or invalid one is an+ `invalid params` error. A test fails if any prompt names a tool that is+ not registered.+- `intel guide` prints the guide markdown; `intel guide --measures` prints+ the glossary.+- A test spawns the installed `world-intel-mcp` console script and drives+ initialize, resources/list, resources/read, prompts/list, prompts/get+ and tools/list over stdio.++### Added: tropical cyclone forecast tracks+- `intel_cyclones` and `intel_jtwc_cyclones` take `include_forecast`+ (boolean, default false). With it, each storm gains a `forecast`: the+ `initial` fix and forecast `points` (forecast hour, UTC valid time,+ latitude and longitude, max wind and gust in knots, status such as+ POST-TROP/REMNT LOW or DISSIPATED, and the agency's section label),+ `track_status`, and the advisory or warning number and issue time.+ Without it, both responses and the collector's NHC call are unchanged.+- NHC points come from the forecast/advisory text that CurrentStorms.json+ links: the one NHC product that states UTC valid times and post-tropical+ status outright (the KMZ track gives local times, and the shapefile+ labels a post-tropical remnant low "Subtropical Depression"). The cone+ comes from the linked CONE.kmz: its one ring, simplified+ (Douglas-Peucker, 0.01 degrees; Hurricane Trudy advisory 17 went from+ 1,167 vertices to 56) to `[lat, lon]` vertices, with the source vertex+ count, the tolerance, and a note pointing at the official geometry+ (`cone_url`).+- JTWC points come from each storm's linked warning text (its forecast,+ extended outlook and long range outlook blocks). JTWC links no cone:+ `cone_status` is `not_published`, and `data_gaps` says so.++### Data honesty: forecast tracks+- `data_gaps` names every track or cone not delivered, per storm, with a+ status: `fetch_failed`, `unparsed`, `refused_link`, `not_linked`,+ `not_published` or `not_fetched_cap` (at most 10 storms per call; the rest are named,+ never dropped). A failure marks the response `degraded`; a product the+ agency does not link is a gap, not degradation. A quiet basin still+ answers zero storms, not degraded, and makes no product fetches; a feed+ outage keeps its existing degraded shape and makes none either.+- The text pages are per storm bin, not per issuance, so one can lag the+ feed: an advisory or warning number that disagrees with the feed is+ returned as `stale_advisory` or `stale_warning` with the expected+ number, and its cached copy is dropped.+- Each product is fetched once per issuance (cache keys carry the+ advisory or warning number; one-hour TTL) under its own circuit breaker+ (`nhc-forecast`, `nhc-gis`, `jtwc-warning`), so a product outage does+ not trip the warning feeds' breakers.+- Remote KML is parsed with the standard library: strict UTF-8, any+ DOCTYPE refused, size caps (KMZ 2 MB, KML 8 MB), and a cone with more+ than one ring refused, never trimmed. A ring of more than 10,000+ vertices is refused before simplifying, and simplifying runs off the+ event loop.+- Product links come from the agencies' feeds and are fetched only when+ they are https on the agency's own host (www.nhc.noaa.gov,+ www.metoc.navy.mil). Any other link is reported as `refused_link` and+ never requested.+- Measured 2026-10-17: every product used answered HTTP 200 without a+ key; nhc.noaa.gov robots.txt disallows nothing and the NWS disclaimer+ puts the products in the public domain. The JTWC home page and+ robots.txt answered 403 (CloudFront "Request blocked"), so JTWC's site+ terms could not be read; its RSS and warning texts served 200 to the+ same client. Wind radii and seas are not parsed.++### Added: observation history and collection health+- A history store in the cache SQLite file. Every collector source run is a+ capture: source, collected_at, status (ok, degraded or error), duration,+ record count, reason and payload hash. A failed fetch is an error capture+ with its reason and no record count, never an ok capture with zero+ records. An empty payload is degraded, because a quiet period and a+ silent upstream failure look the same.+- Payload bodies are kept once per distinct payload as compressed JSON+ (top-level fetch-time stamps are ignored when hashing). Retention, each+ 0 = keep forever: `WORLD_INTEL_HISTORY_PAYLOAD_DAYS` (default 7) for+ bodies, `WORLD_INTEL_HISTORY_CAPTURE_DAYS` (default 30) for the run log,+ `WORLD_INTEL_HISTORY_DAYS` (default 365) for observations. Measured over+ three full 55-source cycles: 90 KB and 193 KB of new compressed bodies in+ the two follow-up cycles (about 70 KB from sources that change every+ cycle, plus the military flight snapshot when it succeeds) and about+ 14 KB of capture rows per cycle. At `--interval 300` that is about+ 130-340 MB of bodies at the 7-day default and about 100 MB of run log at+ 30 days. Quote observations on a trading day were not measured.+- Observations with three dates: `observed_at` (from the payload, or null+ when it has none; never the collection time), `published_at` (when the+ payload names a release time) and `collected_at`. Built-in extractors:+ NOAA Kp, USGS per-event magnitude, FRED-sourced central bank rates+ (curated rows are skipped), Yahoo index and commodity quotes (null+ `observed_at`: the payload carries no quote time).+ `history.register_extractor()` is the public API for new sources.+- MCP tools `intel_collection_health`, `intel_capture_history`,+ `intel_series_history` and `intel_revisions`, and the CLI group+ `intel history health|captures|series|revisions`. History accrues only+ while the collector runs.+- The collector records every source outcome of a cycle in one+ transaction. Its summary gains a `history` key (and the CLI summary a+ History line); a history write failure is reported there and in the+ log, and never fails the cycle.+- Expected cadence for health is 300 s (the shipped plist interval);+ `WORLD_INTEL_HISTORY_CADENCE_S` and+ `WORLD_INTEL_HISTORY_CADENCES=source=seconds,...` override it.++### Notes+- The cycle summary's `successes` still counts a source that returned+ `{"error": ...}` (unchanged, pinned by an existing test); that run's+ history capture is an error.+- Tools 139 -> 143.++### Added: news signals (ROADMAP Phase 29)+- `intel_hostility_timeline`: per UTC day, GDELT DOC 2.0 coverage of a+ country or a pair of countries (`timelinevolraw`): matching articles,+ articles that also use threat / sanction / force / criticism terms (one+ GDELT query per category, every term listed in `queries`), GDELT's total+ monitored articles, and average tone (`timelinetone`, weighted by the+ per-bucket article counts). A failed call leaves its column null for+ every day; a day GDELT did not return is null in every column; both are+ listed in `data_gaps`. Partial days (GDELT answered 2026-10-17 in+ 15-minute buckets for 3 days and hourly buckets for 7) are flagged+ `partial`, judged from the first category series that answered when the+ base call failed, and today's unfinished UTC day is flagged+ `in_progress`. A+ failed call is retried once.+- `intel_situations`: country pairs ("between": a headline naming two or+ more countries) and single countries ("inside": a headline naming one)+ ranked over a recent RSS window by most covered, most hostile (headline+ keyword heuristic, `classifier.classify_hostility`) or biggest change.+ Change is defined in the response: current minus prior window, counted+ only over feeds whose retained history reaches back past the prior+ window's start; the feeds that do not are named.+- `intel_top_stories`: story clusters in the window carried by at least+ `min_outlets` distinct outlets, plus attention: the countries and+ organizations whose headline mentions grew most against the prior window.+- `intel_news_clusters` clusters gain `outlets` and `outlet_count`+ (distinct publishers among all members; sister feeds such as BBC World+ and BBC Mundo count once). Existing keys are unchanged.+- CLI: `intel hostility COUNTRY [OTHER]`, `intel situations`,+ `intel top-stories`. Nulls render as `n/a`, never 0; partial days are+ marked `*` and today `~`.+- Collector: `situations` and `top_stories` (57 sources).++### Changed+- Concurrent `fetch_news_feed` reads of the same feed set share one+ request per feed. The collector starts its four news sources in one+ gather, and each used to request every feed itself; measured live+ 2026-10-17, a news-group cycle made 119 feed requests for 119 feeds+ (4 of 4 sources ok, 9.8 s). Each caller still gets its own limit and+ its own item copies, and a caller's timeout does not cancel the read+ the others are waiting on.+- Live GDELT calls are spaced at least 5 s apart by the fetcher+ (`_SOURCE_RATE_LIMITS["gdelt"]`), for every GDELT caller: GDELT's 429+ body asks for "one every 5 seconds" (measured 2026-10-17). Cache hits are+ not delayed. The limiter is per process, so the MCP server and the+ collector do not share it, and the fetcher's own retries inside one call+ are not spaced by it.++### Fixed+- RSS outage read as a slow news day (ROADMAP Phase 24.5):+ `fetch_news_feed` returned `count: 0` with no marker when every feed+ failed. It now reports `feeds_attempted`, `feeds_ok`, `feeds_failed` and+ `feeds_stale` on every call, and `error` / `degraded` /+ `reason: all_feeds_failed` when no feed answered live;+ `intel_news_clusters` and `intel_trending_keywords` pass the marker+ through, so `intel trending` prints an error instead of an empty+ keyword table.+- RSS outage behind a warm cache read as healthy news: a feed whose fetch+ failed came back as its expired cached copy (the fetcher's stale+ fallback, which marks only dict payloads), so in a running deployment+ an outage counted every feed as fine until the expired copies were+ evicted (the collector evicts about hourly; a server running without+ the collector keeps them until `intel sync`). Such feeds are now listed+ in `feeds_stale`, never counted in `feeds_ok`, and kept out of+ situation and attention change figures.+ Verified live 2026-10-17: with an expired copy seeded for DW Europe+ (its feed answers 404), the europe category reported+ `feeds_stale: ["DW Europe"]`.+- Cluster `sources` was always empty: the clusterer read `source_name` /+ `source`, but RSS items name their outlet `feed_name` (measured live+ 2026-10-17: 23 of 23 clusters had `sources: []`, which also emptied+ `intel_world_brief` top-story sources).+- RSS `published` times were shifted by the host's UTC offset:+ `_parse_published` read feedparser's UTC struct with `time.mktime`+ (local time) instead of `calendar.timegm`. The struct carries+ `tm_isdst=0`, so the shift is the zone's standard offset: on mac-studio+ (US Eastern) an item published 14:43:52 UTC came out `19:43:52Z`, five+ hours ahead (measured 2026-10-17). The amount depends on the host zone+ (none on a UTC host). It skewed every RSS-based time window and any+ ordering against non-RSS times. The regression test sets its own zone,+ so it fails on the old code on a UTC CI runner too.+- Country dossier news was always empty, with no marker (ROADMAP Phase+ 24.5), for three reasons: it asked `fetch_news_feed` for+ `category="all"`, which is not a category (the feed answered with an+ error dict); it read `articles` and `source`, while the feed emits+ `items` and `feed_name`; and it checked only its own `_error`, never the+ feed's `error`. It now reads every feed, passes a feed error or outage+ through as `error` / `degraded` / `reason` with `mention_count: null`+ and a `data_gaps` entry, and names failed or stale feeds. A fourth+ quiet zero: 28 of the 50 accepted country codes (GB, DE, JP and others)+ have no headline keywords, so the search could never match; the section+ now says "mentions not searched" instead of reporting zero.+ `intel dossier` prints `News: not measured` and the gaps in that case.++### Fixed: vessel snapshot waterway matching+- `intel_vessel_snapshot` counted every NGA warning at all nine waterways,+ so three naval-keyword warnings anywhere on Earth marked Panama and+ Hormuz critical alike. On the live feed of 2026-10-17 the old code marked+ all nine `critical` from 8 such warnings, none within 300 km of any of+ them. A warning now counts only at waterways within 300 km of a position+ it states (degrees-minutes or degrees-minutes-seconds). A warning that+ states no position counts by NAVAREA only when its area code names a+ single NAVAREA (4 is NAVAREA IV, 12 is NAVAREA XII, which of the nine+ contain only the Panama Canal). HYDROLANT, HYDROPAC and HYDROARC each+ span several NAVAREAs, so a positionless naval warning in those series,+ or one whose only stated position is malformed, is listed in+ `unplaced_naval_warnings` and named in `data_gaps`. The response states+ the rule in `matching_rule`.+- Each waterway emits `total_nearby` (warnings of any topic credited to+ it, which the old code computed and dropped), split by how they matched+ in `nearby_by_match` and `naval_by_match`; `warning_details` entries+ carry `match`, `distance_km` and `issue_date`.+- With NGA down every waterway read `clear`. It now reads `unknown`, and+ the response carries `error`, `degraded` and `reason`.++### Fixed: navigational warnings+- An NGA outage returned `warnings: []` with no marker, the same shape as a+ sea with no active warnings. It now carries `error`, `degraded`,+ `reason` (`nga_msi_fetch_failed`) and `data_gaps`. A payload with no+ warnings list is `nga_msi_unexpected_payload`; a stale cache serve is+ degraded and says how old the copy is.+- The NGA MSI API holds no warning issued after 10 May 2024 (measured+ 2026-10-17: `msgYear=2025` with `status=all` and `msgYear=2026` return+ none, `msgYear=2024` with `status=all` ends on 10 May, and+ `/current-warnings` and `/inforce` list the same 2024 state), yet+ responses read as current. `intel_nav_warnings` now reports+ `newest_issue_date` and `newest_issue_age_days`; past `stale_after_days`+ (14, twice the slowest series' longest gap between issues in 2024) the+ response is degraded with the age in `data_gaps`. The vessel snapshot and+ fleet report pass this on.+- `area_codes` maps the codes the API sends in `navArea` (4, 12, A, P, C;+ never the Roman numerals) to the NAVAREAs, with each code's source in+ `sources/maritime.py`.++### Fixed: fleet report+- `intel_fleet_report` turned a failed component into `{}`, so with all+ three down it read `LOW_ACTIVITY` with no marker. A component that raises+ or reports an error is now named in `unavailable_components` and+ `data_gaps` and the report is degraded; with all three down it also+ carries `error` and `reason` (`fleet_components_unavailable`). Component+ `data_gaps` are passed on.++### Tests+- Failing-first regression tests for all three, built on live NGA records+ captured 2026-10-17.++### Added: AOI escalation news and convergence components+- `intel_aoi_escalation` now scores the news and convergence components it+ used to report as null (ROADMAP Phase 23).+- News: the rise in the area's share of all GDELT coverage over the last 7+ days against the 7 days before, for the reverse-geocoded settlement and+ county (the query the AOI brief already uses, sent as `timelinevolraw`).+ Expected articles = prior share x current GDELT volume; change_pct =+ 100 x (current - expected) / max(expected, 20); component =+ min(20, 0.2 x max(0, change_pct)). Shares rather than raw counts because+ GDELT's own intake has multi-day outages (measured 2026-10-17 for+ Pittsburgh: no data for 16 of 85 days), which raw counts would read as a+ surge on recovery; a comparison where one week monitored under half the+ other's volume is refused as a data gap. An area that cannot be+ geocoded is not scored, rather than searched by the AOI's name.+- Convergence: `analysis/convergence.py`, unmodified, over the+ earthquakes, military flights, ACLED events and wildfires inside the+ AOI's exact shape (circle, polygon or corridor, through the same+ `filter_by_aoi` scoping as the brief). With an input missing, a+ convergent cell is reported as a lower bound; no cell at all is null,+ because quiet cannot be told from missing.+- New response keys; existing keys keep their meaning. `computed_from`+ names the components the score was computed from, and+ `zero_filled_components` the ones among them that are a 0 only because+ the military or ACLED fetch failed (`score_hotspot` takes no null for+ those, unchanged); `news_signal` (query, both windows' counts and+ shares, change), `news_scoping` and `convergence_signal` (cells, events+ per domain, inputs used, failed or partial) carry the working. A failed+ news or convergence input makes that component null in `components`,+ listed in `unavailable_components` and explained in `data_gaps`, never+ a 0.++### Changed+- The escalation also fetches earthquakes and wildfires (convergence+ inputs) and one GDELT timeline, in parallel with ACLED and military+ flights; their failures are named in `data_gaps`. The brief, the change+ sweep and the escalation now share one AOI scoping helper.+- `test_aoi.py` stubs every network-bound source by default: its older+ escalation tests stub only ACLED and military flights and would+ otherwise reach Nominatim, GDELT, USGS and FIRMS live.++### Added: border crossings (flows)+- `intel_us_border_encounters`: U.S. CBP encounters per calendar month+ (Border Patrol Title 8 apprehensions, Field Operations Title 8+ inadmissibles, Title 42 expulsions), read from the newest CSV on CBP's+ public dataset page, which spans four fiscal years (October 2022 to+ August 2026 when written). Nationwide or one land border region, all+ components or USBP / OFO, optionally one citizenship as CBP names it;+ with the latest month against the same month a year earlier, fiscal-year+ totals (the year in progress compared with the same months of the prior+ year, only when every one is published), breakdowns by component,+ encounter type and demographic, and the top citizenships with CBP's+ OTHER bucket reported apart and never ranked. CBP's fiscal months are+ mapped to calendar months (FY2026 October is October 2025).+- `intel_uk_small_boat_arrivals`: Home Office daily and weekly counts of+ migrants and boats detected crossing the English Channel in small boats,+ with uncontrolled landings and the weekly migrants and events prevented+ by French authorities; month and year sums of the daily rows, and the+ year to date against the same span a year earlier. Read through the+ GOV.UK Content API and the published ODS time series, parsed with the+ standard library (zipfile + ElementTree, no new dependency). The+ publisher's numbered notes are quoted from the file on every refresh.+- Both are flows (events per period), stated in every response with units,+ date semantics and the publisher's caveats, and kept apart from the+ UNHCR and World Bank year-end stocks. Neither file has a person+ identifier, so neither counts unique people (said in each response as a+ tool note, not as the publisher's words).+- An outage is a degraded error with no figures; a failed refresh serves+ the last good copy marked `stale` with its age. A '-' in the UK file is+ null, never 0; a CBP month with no rows inside the file's coverage is 0,+ because CBP lists only non-zero cells, and months outside it are never+ invented. Weekly UK totals are checked against their seven days and any+ mismatch is named in `data_gaps`.+- Requests use an identifying User-Agent, two per refresh (the listing,+ then the file), cached 12 h (CBP) and 3 h (UK). Paths that robots.txt+ disallows are never requested; a newer-looking CBP file at such a path+ is named in `data_gaps` instead.+- Frontex is not built: its only data file is an XLSX under `/assets/`,+ which its robots.txt disallows (measured 2026-10-17, see ROADMAP Phase 28).+- Tools 139 -> 141.++ ### Added: Kalshi and cross-venue prediction markets+ - `intel_kalshi_markets`: Kalshi open markets from its public market-data+ API (no account, no key), ranked by 24h then lifetime volume. Prices are+ YES implied probabilities (bid/ask midpoint when the book is two-sided,+ else the last trade, with the basis named); Kalshi's raw dollar quotes+ are kept. Filter by category (the category's highest-volume series) or+ series ticker. The response names the events it scanned and whether the+ scan was complete: Kalshi lists more than 8,000 open events, furthest+ close date first.+ - `intel_prediction_compare`: the same event on Kalshi and Polymarket side+ by side. Matching is deterministic: quantities (with their direction,+ so "more than 25 bps" is not "25 bps"), years, end dates, negation and+ the outcome side must all agree, and each pair carries a+ `match_confidence` and its reasons. Below the threshold (default 0.6) a+ pair is not a match. Returns the price gap per pair, the closest+ rejected pairs with the reason, and unmatched counts per venue.+ - `intel_prediction_settled`: recently settled markets on both venues with+ the outcome and the YES price at fixed offsets before close (default 24h+ and 168h) from each venue's price-history endpoint, and a Brier score per+ venue and offset with sample size, distinct events, selection and+ exclusions stated. A venue whose price history cannot be read is not+ scored. The two samples are different markets, and the response says so.+ - Every number these three tools take has a stated range in its input+ schema: at most 25 Kalshi series or pages per scan, 2,000 Polymarket+ markets, 500 results, 100 settled markets per venue, and 10 offsets of+ at most 8,760 hours, so one call cannot fan out into an unbounded number+ of upstream requests. The MCP server refuses a value outside its range;+ the source functions clamp counts again for the CLI and other callers,+ and refuse a value that is not a number before any request.+ - CLI: `intel kalshi`, `intel prediction-compare`, `intel prediction-settled`.+ - Collector: `kalshi_markets` and `prediction_compare` (Economics+ category) join the `prediction` domain. Sources 55 -> 57. Tools 139 -> 142.++ ### Fixed: prediction markets outage read as "no markets"+ - `intel_prediction_markets` returned `{"markets": [], "count": 0}` with no+ marker when Polymarket was down, the same shape as a quiet market. It now+ adds `error` and `degraded: true` on an outage or an unexpected response,+ and `stale: true` when the list came from an expired cache entry. Keys,+ parameters and the tool name are unchanged.+## 0.11.0 - 2026-10-12Cross-border migration (MCP tools, CLI, collector and a dashboarddiff --cc README.mdindex 8b673c4,fe62ecf..37fae1f--- a/README.md+++ b/README.md@@@ -6,7 -6,7 +6,7 @@@[](https://python.org)[](LICENSE)- Real-time global intelligence across **30+ domains** with **154 MCP tools**, a live ops-center dashboard, a CLI, and a **Qdrant vector store** for enterprise-grade semantic search across accumulated intelligence. All data comes from free, public APIs: no paid subscriptions required.-Real-time global intelligence across **30+ domains** with **142 MCP tools**, a live ops-center dashboard, a CLI, and a **Qdrant vector store** for enterprise-grade semantic search across accumulated intelligence. All data comes from free, public APIs: no paid subscriptions required.++Real-time global intelligence across **30+ domains** with **157 MCP tools**, a live ops-center dashboard, a CLI, and a **Qdrant vector store** for enterprise-grade semantic search across accumulated intelligence. All data comes from free, public APIs: no paid subscriptions required.Built for AI agents that need world awareness: market conditions, geopolitical risk, military posture, aircraft-cohort early warning, refugee and migration flows, supply chain disruptions, cyber threats, and more — all queryable via the Model Context Protocol. The vector store enables natural language queries like *"military activity near Taiwan"* or *"cyber threats targeting healthcare"* across all historical data.@@@ -48,9 -45,9 +48,9 @@@| **Space Weather** | 1 | NOAA SWPC (Kp index, solar flares, alerts) || **Social & Sanctions** | 3 | Reddit velocity, OFAC SDN list, nuclear test site monitoring || **Country Intelligence** | 3 | Country brief, country stocks, financial centers |- | **Prediction Markets** | 1 | Polymarket event contracts |+ | **Prediction Markets** | 4 | Polymarket and Kalshi event contracts, the same event on both venues side by side with a stated match confidence, and settled markets scored against their earlier prices (Brier) || **Elections** | 1 | Global election calendar with risk scoring |-| **Displacement and Migration** | 5 | UNHCR refugee/IDP data, origin -> destination corridors since 1951, year-over-year surge detection; World Bank net migration and migrant stock |+| **Displacement and Migration** | 7 | UNHCR refugee/IDP data, origin -> destination corridors since 1951, year-over-year surge detection; World Bank net migration and migrant stock; border crossings as flows (CBP monthly encounters, UK small-boat arrivals), never mixed with the year-end stocks || **Shipping** | 1 | Dry bulk shipping stress index || **Government** | 1 | USAspending.gov federal contracts || **Traffic** | 2 | Road traffic flow, real-time incidents |@@@ -64,11 -61,10 +64,11 @@@| **Severe Weather** | 2 | NWS active CAP alerts (US), Meteoalarm (39 EU countries) || **Space Launches** | 1 | Launch Library 2 upcoming launches || **Volcanoes** | 1 | Smithsonian GVP weekly activity report |-| **Tropical Cyclones** | 2 | NHC (Atlantic, E/C Pacific) + JTWC (NW Pacific, N Indian, S Hemisphere) |+| **Tropical Cyclones** | 2 | NHC (Atlantic, E/C Pacific) + JTWC (NW Pacific, N Indian, S Hemisphere), with opt-in forecast tracks: positions, UTC valid times and intensities, plus NHC's cone of uncertainty || **Situation Brief** | 1 | Cited situational awareness brief over MCP: bounded server-side overview synthesized via local Ollama, with a mechanically-cited fallback |+| **Collection History** | 4 | Collector run log (per-source health, overdue and failing sources), saved captures with change detection and replay, dated observation series, revisions |- **Total: 154 tools** across 30+ intelligence domains.-**Total: 142 tools** across 30+ intelligence domains.++**Total: 157 tools** across 30+ intelligence domains.---@@@ -133,15 -129,10 +133,18 @@@ intel markets # stock indiintel earthquakes --min-mag 5.0intel migration-surges # year-over-year displacement jumps (UNHCR)intel migration-flows -o Sudan+intel liquidity # Fed balance sheet, TGA, RRP, net liquidity, US M2, euro area M1-M3+intel net-liquidity -n 0 # full weekly history, components and RRP date per week+intel news-reaction -c finance # same-session moves of companies in the news+intel hostility Iran Israel --days 7 # daily hostile coverage (GDELT)+intel situations --sort change # ranked situations (RSS)+intel top-stories -m 4 # stories carried by 4+ outlets+ intel kalshi -c Economics # Kalshi open markets by volume+ intel prediction-compare -c Economics # same event on Kalshi and Polymarket+ intel prediction-settled # Brier scores on settled marketsintel status # cache + circuit breaker health+intel guide # the research guide (also served as intel://guide)+intel history health # per-source collection health from the collector's run log```---diff --cc ROADMAP.mdindex c831b06,30b5c3b..3816cf5--- a/ROADMAP.md+++ b/ROADMAP.md@@@ -2,7 -2,7 +2,7 @@@**Benchmark**: [koala73/worldmonitor](https://github.com/koala73/worldmonitor)**Updated**: 2026-10-12 (0.11.0: aircraft-cohort early warning, cross-border migration)- **Current tools**: 154 (153 intel + 1 status)-**Current tools**: 139 (138 intel + 1 status)++**Current tools**: 157 (156 intel + 1 status)---@@@ -587,15 -571,15 +587,15 @@@ dashboard| Wave | Feature | What it means here | Status ||------|---------|--------------------|--------|-| 1 | Observation history store | Every collector capture saved with `observed_at` (period the data describe), `published_at` (publisher release, when known) and `collected_at` (when we saved it); unchanged payloads stored once; bounded retention; backfill for sources that serve history (FRED CSV) | :red_circle: |-| 1 | Capture history and revisions | Earlier saved copies of a source, and values a later copy revised | :red_circle: |-| 1 | Collection health | Per-source expected cadence; overdue / failing / never-run per source, measured from the run log, not inferred from cache freshness. Says what it cannot prove | :red_circle: |-| 1 | Research guide over MCP | MCP resources (guide generated from the live registry and source health, measures glossary, "what this server will not do") and MCP prompts (worked research questions, each naming the tools it needs and the limit to respect). Server exposed no prompts or resources before | :red_circle: |-| 1 | Hostility timeline | Per country pair or country, daily counts of threat / sanction / force / criticism coverage plus tone; sortable by most covered, most hostile, biggest change | :red_circle: |-| 1 | Story breadth | News clusters carry a distinct-outlet count; a top-stories view ranks by how many outlets carry a story | :red_circle: |-| 1 | Liquidity and flows | Fed balance sheet, Treasury General Account, reverse repo and net liquidity (FRED keyless CSV), money supply (US M2, euro area M1/M2/M3, never summed), ECB, ICI fund flows and ETF net issuance, FINRA margin statistics, BLS series; amounts kept separate from flows | :red_circle: |+| 1 | Observation history store | Every collector capture saved with `observed_at` (period the data describe), `published_at` (publisher release, when known) and `collected_at` (when we saved it); unchanged payloads stored once; bounded retention; backfill for sources that serve history (FRED CSV) | :yellow_circle: Unreleased: store, three dates, dedupe, retention and `register_extractor()` done (`history.py`; extractors for Kp, USGS magnitudes, FRED central bank rates, Yahoo quotes); backfill not done |+| 1 | Capture history and revisions | Earlier saved copies of a source, and values a later copy revised | :white_check_mark: Unreleased (`intel_capture_history` with payload replay, `intel_revisions`) |+| 1 | Collection health | Per-source expected cadence; overdue / failing / never-run per source, measured from the run log, not inferred from cache freshness. Says what it cannot prove | :white_check_mark: Unreleased (`intel_collection_health`, `intel history health`) |+| 1 | Research guide over MCP | MCP resources (guide generated from the live registry and source health, measures glossary, "what this server will not do") and MCP prompts (worked research questions, each naming the tools it needs and the limit to respect). Server exposed no prompts or resources before | :white_check_mark: Built 2026-10-17, unreleased: 3 resources (`intel://guide`, `intel://guide/source-health`, `intel://guide/measures`), 29 prompts, `intel guide`; verified over a live stdio session |+| 1 | Hostility timeline | Per country pair or country, daily counts of threat / sanction / force / criticism coverage plus tone; sortable by most covered, most hostile, biggest change | :white_check_mark: Built 2026-10-17, unreleased: `intel_hostility_timeline` (GDELT DOC 2.0 `timelinevolraw` + `timelinetone`, one call per category, failed calls and missing days null) and `intel_situations` (RSS headlines, ranked by covered / hostile / change, change defined over feeds whose history spans both windows). Measured 2026-10-17: timeline modes answer (HTTP 200, `date_resolution` `hour` for `timespan=7d` and `15m` for `3d`, explicit zero buckets, `norm` = all monitored articles), but a `timespan=7d` request returned 54 hours (2026-10-15T10Z onward), and about half of calls drew 429 even 30 s apart (later probes, 16:51 to 16:53Z, 4 of 4 drew 429, so the resolution for 14 days and coverage before 2026-10-15T10Z are unmeasured; 30 days was not probed; a live MCP run at 17:00Z got 4 of 6 columns after the retry pass, one at 17:20Z got 1 of 6, consistent with the server's breaker opening after 3 failed calls, which also skips the retry pass). The fetcher now spaces every live GDELT call at least 5 s apart, per process. Artlist was not used for daily counts: 250 records sorted by date covered 15 minutes. Situations see only the 22-country entity table |+| 1 | Story breadth | News clusters carry a distinct-outlet count; a top-stories view ranks by how many outlets carry a story | :white_check_mark: Built 2026-10-17, unreleased: clusters gain `outlets` / `outlet_count` (sister feeds of one publisher count once); `intel_top_stories` ranks by outlet count with an attention list (countries and organizations by mention growth). Found on the way: cluster `sources` was empty in every live cluster (key mismatch, `feed_name` vs `source_name`) and RSS times were shifted by the host UTC offset; both fixed. Concurrent RSS reads now share one request per feed (a live collector news-group cycle: 119 requests for 119 feeds) |+| 1 | Liquidity and flows | Fed balance sheet, Treasury General Account, reverse repo and net liquidity (FRED keyless CSV), money supply (US M2, euro area M1/M2/M3, never summed), ECB, ICI fund flows and ETF net issuance, FINRA margin statistics, BLS series; amounts kept separate from flows | :yellow_circle: Built, unreleased: 5 tools (`intel_liquidity_board`, `intel_net_liquidity`, `intel_money_supply`, `intel_fed_liquidity_series`, `intel_ecb_series`), 5 CLI commands, 2 collector sources. FRED graph CSV and ECB Data Portal live-verified 2026-10-17. The TGA term is WDTGAL (Wednesday level, USD millions): WTREGEN is a week average; the net liquidity `method` block states each term's units, conversion and how RRPONTSYD (daily, USD billions) is aligned to the Wednesday. Blocked, measured 2026-10-17, and listed in the board's `blocked` field; no proxy is substituted, so fund flows and ETF net issuance have no source: ICI (money market fund assets at /research/stats/mmf, ETF net issuance at /research/stats/etf) answers 403 Akamai "Access Denied" on every path, robots.txt included; FINRA margin statistics XLSX answers 200, but the finra.org Terms of Use (Restrictions d and e) forbid building a database from the site and data mining, scraping or harvesting tools, robots included, and the page says data feeds are not available; BLS public API v1 answers 200 without a key (CPI-U, payrolls), but api.bls.gov robots.txt is `Disallow: /` and the terms page on www.bls.gov answers 403 to this server's User-Agent, so it is not used |- | 1 | Kalshi + cross-venue markets | Kalshi public market data next to Polymarket; same-event comparison with an explicit match confidence; settled markets scored against pre-settlement prices (Brier) | :red_circle: |+ | 1 | Kalshi + cross-venue markets | Kalshi public market data next to Polymarket; same-event comparison with an explicit match confidence; settled markets scored against pre-settlement prices (Brier) | :white_check_mark: Unreleased: `intel_kalshi_markets`, `intel_prediction_compare`, `intel_prediction_settled` (`sources/kalshi.py`, `sources/prediction_cross.py`, `analysis/prediction_matching.py`), CLI and 2 collector sources. Kalshi endpoints measured 2026-10-17, all HTTP 200 without an account: `/events` (nested markets), `/series` (`include_volume`), `/markets?status=settled`, `/markets/candlesticks` (batch, capped at 10,000 candles per call), `/historical/cutoff`. The `/events` `category` parameter is ignored by the API, so categories resolve through `/series?category=`, whose filter is loose too (7 of the 869 series it returned for Economics were other categories), so series are matched exactly; an unknown category answers `{"series": null}` and is reported as a gap, not an outage. The exchange-wide settled listing is intraday sports (1,000 rows covered about 40 minutes; none open 24h), so settled samples default to the Economics category's top series. Polymarket Gamma caps a page at 100 rows. Matching is deliberately conservative: live 2026-10-17 it matched the Fed 25 bps hike/cut pairs for October and December and rejected 25 vs 50+ bps, 2026 vs 2027, and the Fed-hold pair ("no change" vs "Hike 0bps": a known false negative). Team and person aliases are not resolved, so most sports pairs stay unmatched. Kalshi requests are spaced 0.2 s apart in-process: the two collector sources scanning the same series at once drew HTTP 429, and at 0.1 s a 26-request category scan still drew one (none at 0.2 s in one live run). Settled samples are the most recently settled markets and cluster in time (one football match supplied 11 of 25 Polymarket markets in a live run), so a Brier score describes its sample, not a venue's skill. Every number a caller passes has a range stated in the input schema (at most 25 Kalshi series or pages per scan), so one call cannot fan out into unbounded upstream requests |-| 1 | News vs market reaction | Companies and countries named in story clusters mapped to tickers / country indices; same-day move against a benchmark | :red_circle: |+| 1 | News vs market reaction | Companies and countries named in story clusters mapped to tickers / country indices; same-day move against a benchmark | :yellow_circle: Built 2026-10-17, unreleased; 7 test expectations await correction at merge: `intel_news_market_reaction` and `intel news-reaction`. Company rows: stock, benchmark (SPY, or the exchange country's index) and excess return on the story's session; country rows: index return with a trailing z-score. Session rule in the exchange's timezone (after close = next session; weekends and holidays read from the listing's own bars); a last bar Yahoo has not finalized is pending. Open: `^TASI` and `^TA125` (Saudi and Israel in the country-index table) return 404 on Yahoo, so those benchmarks are data gaps; story times inherit `sources/news.py`'s RSS timestamp offset until that is fixed || 2 | Connections with timing offsets | Correlation between retained series over a shared sample, tested at leads and lags, with minimum sample size and false-discovery control; states that it does not prove causation | :red_circle: || 2 | Day timeline | What every retained source recorded for a given day, by observation date or collection date | :red_circle: || 3 | Dashboard views | Liquidity board, situations, top stories, collection health panels | :red_circle: |@@@ -650,11 -634,10 +650,11 @@@ fail-quietly bugs below were fixed in t| UNHCR outage returned all-zero global totals with no error/degraded key ("zero refugees worldwide") | `sources/displacement.py` | fail-reads-as-success | :white_check_mark: Fixed (#22) || A climate zone whose fetch failed was silently omitted; full outage yielded `{"zones": {}}` with no marker | `sources/climate.py` | silent degradation | :white_check_mark: Fixed (#23) || "Resolved: Major outage" classified as an active critical incident; a dead provider feed still listed as checked | `sources/service_status.py` | misclassification | :white_check_mark: Fixed (#24) |-| Naval warnings apply to all 9 waterways identically (no proximity/NAVAREA filter); `total_nearby` computed but never emitted | `sources/intelligence.py` vessel snapshot | precision | :red_circle: |+| Naval warnings apply to all 9 waterways identically (no proximity/NAVAREA filter); `total_nearby` computed but never emitted | `sources/intelligence.py` vessel snapshot | precision | :white_check_mark: Fixed (Unreleased): a warning counts only at waterways within 300 km of a position it states, or, when it states none, by single-NAVAREA area code (4, 12); the rule is in `matching_rule`, naval warnings no rule can place are in `unplaced_naval_warnings`; `total_nearby` emitted; an NGA outage reads `unknown`, not `clear` || Country/company/leader entity matching was substring-based ("usa" inside "thousand", "hamas" inside "Bahamas") | `analysis/entities.py` | false positives | :white_check_mark: Fixed in 0.5.0 (word-boundary alternations, measured faster) || Category keywords matched substrings ("airstrike" bumped severity via "strike"; "denied" fired "ied") | `analysis/classifier.py` | false positives | :white_check_mark: Fixed in 0.5.0 (boundary-anchored stems, per-keyword overrides) |- | Silent-empty degradation without a marker on RSS/API failure | `sources/prediction.py` (documented as intended), `sources/maritime.py`, `sources/news.py` RSS path, `sources/fleet.py` `_safe` wrapper | silent degradation | :yellow_circle: `sources/news.py` RSS path fixed 2026-10-17 (every call reports `feeds_attempted` / `feeds_ok` / `feeds_failed` / `feeds_stale`; no feed answering live is `error` + `degraded` + `reason: all_feeds_failed`, including the warm-cache case where failed feeds came back as expired copies and counted as healthy; failing-first regression tests). `maritime.py` and `fleet.py` fixed (Unreleased): outages carry `error`/`degraded`/`reason` and `data_gaps`, failed fleet components are named in `unavailable_components`, and nav warnings flag a feed whose newest warning is over 14 days old (NGA's API holds nothing issued after 10 May 2024, measured 2026-10-17). `prediction.py` still open. The fetcher's stale fallback marks only dict payloads, so other text and XML sources can serve expired copies unmarked |-| Silent-empty degradation without a marker on RSS/API failure | `sources/prediction.py` (documented as intended), `sources/maritime.py`, `sources/news.py` RSS path, `sources/fleet.py` `_safe` wrapper | silent degradation | :yellow_circle: `sources/prediction.py` fixed, unreleased: an outage or unexpected response adds `error` + `degraded`, an expired-cache serve adds `stale`; keys unchanged; regression tests written failing-first (3 failed on the old module). `maritime.py`, `news.py` RSS path and `fleet.py` `_safe` still open |++| Silent-empty degradation without a marker on RSS/API failure | `sources/prediction.py` (documented as intended), `sources/maritime.py`, `sources/news.py` RSS path, `sources/fleet.py` `_safe` wrapper | silent degradation | :yellow_circle: `sources/news.py` RSS path fixed 2026-10-17 (every call reports `feeds_attempted` / `feeds_ok` / `feeds_failed` / `feeds_stale`; no feed answering live is `error` + `degraded` + `reason: all_feeds_failed`, including the warm-cache case where failed feeds came back as expired copies and counted as healthy; failing-first regression tests). `maritime.py` and `fleet.py` fixed (Unreleased): outages carry `error`/`degraded`/`reason` and `data_gaps`, failed fleet components are named in `unavailable_components`, and nav warnings flag a feed whose newest warning is over 14 days old (NGA's API holds nothing issued after 10 May 2024, measured 2026-10-17). `sources/prediction.py` fixed, unreleased: an outage or unexpected response adds `error` + `degraded`, an expired-cache serve adds `stale`; keys unchanged; regression tests written failing-first (3 failed on the old module). The fetcher's stale fallback marks only dict payloads, so other text and XML sources can serve expired copies unmarked |+| Country dossier news was always empty with no marker, for every country: it asked the feed for `category="all"` (not a category, so `fetch_news_feed` answered with an error dict), read `articles` / `source` while the feed emits `items` / `feed_name`, and checked only its own `_error`, never the feed's `error`. Also, 28 of the 50 accepted codes have no headline keywords, so their search could never match | `analysis/dossier.py` news section | fail-reads-as-success | :white_check_mark: Fixed 2026-10-17, unreleased (reads every feed; a feed error or outage passes through as `error` / `degraded` / `reason` with `mention_count: null` and a data gap; failed and stale feeds named; keywordless countries report "mentions not searched"; `intel dossier` prints `News: not measured`; failing-first tests drive the real `fetch_news_feed` output) || 33 CLI commands rendered upstream errors as healthy empty states | `cli.py` | fail-reads-as-success | :white_check_mark: Fixed in 0.6.0 (shared bail-on-error path; 43 failing-first tests) || Rich markup swallowed lowercase bracketed values and let remote titles inject markup | `cli.py` | output corruption | :white_check_mark: Fixed in 0.6.0 (per-site escaping; injection test) || Remote data inside Rich TABLE cells was not markup-escaped | `cli.py` | output corruption | :white_check_mark: Fixed in 0.6.0 (`_cell` Text-wrapping convention, 11 injection tests; error styles unified across all 53 commands) |@@@ -688,8 -671,8 +688,8 @@@ suite, and a live MCP stdio session| Category | Current | Notes ||----------|---------|-------|- | Total MCP tools | 154 | 153 intelligence tools + `intel_status` |- | Tool parity | 154 / 154 | `TOOLS` and handlers are aligned at import time; README's per-tool reference is pinned to the registry by `test_readme_documents_every_registered_tool` |-| Total MCP tools | 139 | 138 intelligence tools + `intel_status` |-| Tool parity | 139 / 139 | `TOOLS` and handlers are aligned at import time; README's per-tool reference is pinned to the registry by `test_readme_documents_every_registered_tool` |++| Total MCP tools | 157 | 156 intelligence tools + `intel_status` |++| Tool parity | 157 / 157 | `TOOLS` and handlers are aligned at import time; README's per-tool reference is pinned to the registry by `test_readme_documents_every_registered_tool` || Static datasets | 18 | Bases, ports, pipelines, nuclear, cables, datacenters, spaceports, minerals, exchanges, trade routes, cloud regions, financial centers || RSS feeds | 119 | 24 categories || Tests in repo | 991 | 973 non-smoke tests + 18 live smoke tests (measured 2026-10-12: `pytest -m 'not smoke'` -> 973 passed, 18 deselected); full suite requires `.[dev]` |diff --cc src/world_intel_mcp/cli.pyindex 124b2d4,b57d7c2..20237ae--- a/src/world_intel_mcp/cli.py+++ b/src/world_intel_mcp/cli.py@@@ -68,7 -68,8 +68,9 @@@ from .sources.github_trending import fefrom .sources.arxiv_papers import fetch_arxiv_papersfrom .sources.usa_spending import fetch_usa_spendingfrom .sources import geospatial+from .sources import liquidity+ from .sources import kalshi as kalshi_src+ from .sources import prediction_crossconsole = Console()diff --cc src/world_intel_mcp/collector.pyindex adf7d16,983f3cc..58978ef--- a/src/world_intel_mcp/collector.py+++ b/src/world_intel_mcp/collector.py@@@ -90,16 -76,15 +90,20 @@@ SOURCES =("nav_warnings", "sources.maritime", "fetch_nav_warnings", {}),# Climate (1)("climate_anomalies", "sources.climate", "fetch_climate_anomalies", {}),- # News (2)+ # News (4)("news_feed", "sources.news", "fetch_news_feed", {}),("trending_keywords", "sources.news", "fetch_trending_keywords", {}),+ # Ranked situations and outlet-breadth stories over the same RSS read:+ # fetch_news_feed shares one in-flight read among concurrent callers,+ # so these four request each feed once per cycle.+ ("situations", "analysis.news_signals", "fetch_situations", {}),+ ("top_stories", "analysis.news_signals", "fetch_top_stories", {}),- # Prediction (1)+ # Prediction (3)("prediction_markets", "sources.prediction", "fetch_prediction_markets", {}),+ # Kalshi: the Economics category's top series (Fed, CPI, gas prices);+ # the unfiltered scan reads 4 MB pages of far-dated events instead.+ ("kalshi_markets", "sources.kalshi", "fetch_kalshi_markets", {"category": "Economics", "limit": 50}),+ ("prediction_compare", "sources.prediction_cross", "fetch_prediction_compare", {"category": "Economics"}),# Aviation (4)("airport_delays", "sources.aviation", "fetch_airport_delays", {}),("domestic_flights", "sources.aviation", "fetch_domestic_flights", {}),@@@ -181,8 -165,8 +185,8 @@@ DOMAIN_GROUPS ="infrastructure": ["internet_outages", "cable_health", "service_status"],"maritime": ["nav_warnings"],"climate": ["climate_anomalies"],- "news": ["news_feed", "trending_keywords"],+ "news": ["news_feed", "trending_keywords", "situations", "top_stories"],- "prediction": ["prediction_markets"],+ "prediction": ["prediction_markets", "kalshi_markets", "prediction_compare"],"aviation": ["airport_delays", "domestic_flights", "bizjet_cohort", "military_cohort"],"cyber": ["cyber_threats"],"space": ["space_weather", "launch_schedule"],diff --cc src/world_intel_mcp/tools/__init__.pyindex fc0bb4d,51cedaa..3054582--- a/src/world_intel_mcp/tools/__init__.py+++ b/src/world_intel_mcp/tools/__init__.py@@@ -28,13 -28,10 +28,14 @@@ from . import ( # noqa: E40finance,geospatial,hazards,+ history,infrastructure,intelligence,+ liquidity,markets,+ news_market,+ news_signals,+ prediction_markets,society,synthesis,system,