Baseline Mcp

io.github.elninyo-ops由 GitHub 帳號 elninyo-ops 發布v0.1.9更新於 Oct 24, 2026

Statistically rigorous weather and climate context: forecast plus 35-year historical ranking.

已驗證STDIO僅桌面位置與生活資料與分析

概覽

AI 產生的概覽

本機 MCP 伺服器,讓助理取得任意地點依 35 年紀錄排序的天氣與氣候背景,並附上測站交叉核對與明確的可信度說明

可以做什麼
以自然語言提問,取得預報加上 35 年排序的氣候背景;也可依精確經緯度查詢,或查看某地自水文年起算的降水與氣溫在 35 年中的排名。比較某地近期天氣相對於常年有多異常。在 2 至 10 個地點或某個精選類別之間,依水文年、季節、月份或滑雪季對降水、氣溫或降雪進行排名。每則回覆都帶有評估欄位,說明提供者自身的信心程度,包括接近並列、測站不一致,以及未能進行交叉核對的情況。
適用情境
當問題需要歷史氣候排名而非單一數字時適用,例如某月是否異常偏暖或偏濕、某季節是否接近常年,或數個地點在一個季節或水文年內的比較。也適合需要測站交叉核對與誠實信心說明的爭議或規劃情境。
執行需求
以 Python 套件(pip 或 uvx)形式透過 stdio 在本機執行,或作為可串流 HTTP 伺服器執行於 127.0.0.1。需要環境變數 BASELINE_API_URL 與金鑰 BASELINE_API_KEY;金鑰未開放自助申請,須以電子郵件索取。需要連線至 Baseline API 的網路存取。
安裝前請注意
必須提供 BASELINE_API_KEY,每次呼叫都計入該金鑰的配額;HTTP 模式下每個請求都須在 X-Api-Key 或 Authorization 標頭中攜帶呼叫方的金鑰,無有效金鑰的請求會回傳 401。查詢內容與座標會傳送給第三方 Baseline API。測站交叉核對僅涵蓋美國,季節展望僅提供降水。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Baseline Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Baseline Climate

Stop your agent inventing climate context. Ranked 35-year records for any point on Earth, cross-checked against real stations, with an explicit reliability note to relay instead of guess.


Ask it something, and this is what comes back.

A ranking — with the near-tie disclosed, and a station agreeing:

August 2026: Mean temperature was 75°F, +2.8°F from normal, ranking as the 8th warmest since 1991 — though the 7th warmest through 9th warmest years are within 0.7°F of each other. A nearby station (CASPER-NATRONA COUNTY AP, 8.4 mi) agrees: +2.1°F from its own normal, against the reanalysis's +2.8°F.

A station that does not agree — the gauge a mile away read half the grid's total:

March 2026: Precipitation totaled 2.30 in — near average for this period historically. A nearby station (BOZEMAN MONTANA STATE UNIVERSITY, 1.3 mi) measured 1.12 in, against the reanalysis's 2.30 in.

A wind ranking that says plainly it is modeled, not measured:

March 2026: Modeled peak gust: 60 mph, ranking as the 3rd gustiest since 1991 — though it's within 1 mph of the 6th gustiest year. A station (Saratoga, 32.1 mi) measured a peak gust of 59 mph. The reanalysis figure is a modeled estimate, not a direct reading.

A seasonal outlook carrying its own skill label:

Leaning wetter than normal for Sep–Nov in Nairobi, on odds we haven't been able to verify here — below normal 5%, near normal 19%, above normal 76%. Forecasts here do track wetter and drier seasons, so the direction is the part worth using; whether the percentages themselves beat a climatological guess has not been shown.

Four things worth noticing. It gives you the rank, not just the number. It tells you when the rank is a near-tie, so you don't over-read it. It goes and asks a real weather station whether the gridded record is right — and when the station disagrees, it says so rather than papering over it. And when it can't vouch for its own forecast, it tells you that too.

The data isn't new. Asking it a question is.

ERA5 has been sitting in public archives for years. Interrogating it meant knowing which dataset, writing the code, and having an afternoon. That cost is what collapsed — and the interesting consequence is that people now ask things they'd never have thought worth the trouble.

The Bozeman example above isn't a weather lookup. It's a construction schedule dispute, where the question was whether rain actually stopped work — and the gridded record said one thing while the gauge a mile away said another. The wind example is a trucking corridor. Neither would have been worth opening a climate dataset for. Both take a sentence now.

That's the claim: not that historical weather data exists, but that the cost of asking it a real question has fallen far enough that weather becomes one ordinary input into questions that aren't about weather.

What it won't claim

Most tools hand you a number. This one hands you the number and its standing.

  • Near-ties are disclosed. "8th warmest — though the 7th through 9th are within 0.7°F" stops a model reporting a rank as though it were a meaningful gap.
  • Station disagreement moves confidence, and says which way. A gauge reading 1.12 in against a grid's 2.30 in is reported, not averaged away.
  • When no cross-check ran, it says why — no nearby station, outside the covered region, source didn't respond. The gap is named rather than left for the model to fill.
  • Seasonal outlooks carry an honest skill label. Calibrated from ECMWF SEAS5 against 35 years of observations, then labelled by what testing actually showed: that the odds beat a climatological guess here, or that only the direction is worth using, or — where a simple warming trend predicted the season better than the model did — that the model isn't the thing to go on. We publish the cases where our own forecast isn't the best available answer.

Every response carries an assessment field with Baseline Climate's own confidence statement, and the tool descriptions instruct the model to relay it rather than compose its own. That exists because the failure mode is real: given a bare number, models invent records that weren't broken, assert a dataset is unreliable somewhere it isn't, and recycle one station disagreement across unrelated answers.

What it's made of

Global daily recordERA5-Land reanalysis, 0.1°, 1991–present, land-only
Station cross-checkACIS (NOAA RCC). United States only — outside the US, answers say plainly that no station check ran
Seasonal outlookECMWF SEAS5, calibrated per region. Precipitation only — temperature has not yet cleared our skill test, and we don't issue one until it does
ForecastOpen-Meteo

Rankings use the full 1991–present record; "normal" means the WMO 1991–2020 reference period. See METHODOLOGY.md for how rankings, percentiles and water years are computed, and where the limits are.

Tools

  • get_climate_context — a natural-language question; forecast plus 35-year ranked context.
  • get_context_for_coordinates — the same for an exact lat/lon.
  • get_water_year_status — precipitation and temperature since the start of the water year, ranked against 35 years.
  • compare_to_normal — how unusual near-term conditions are at one location.
  • compare_locations — rank precipitation, temperature or snowfall across 2–10 locations, or a curated category, over a water year, season, month or ski season.

Install

Requires an API key. Self-serve signup isn't available yet — email Chad McNutt ([email protected]) during this early period.

bash
pip install baseline-mcp     # or: uvx baseline-mcp

Claude Code

bash
claude mcp add baseline \  --env BASELINE_API_URL=https://api.baselinecontext.com \  --env BASELINE_API_KEY=your-key-here \  -- uvx baseline-mcp

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "baseline": {      "command": "uvx",      "args": ["baseline-mcp"],      "env": {        "BASELINE_API_URL": "https://api.baselinecontext.com",        "BASELINE_API_KEY": "your-key-here"      }    }  }}

Cursor — .cursor/mcp.json, same shape as above.

As an HTTP server (streamable HTTP, for hosting behind a reverse proxy):

bash
BASELINE_API_URL=https://api.baselinecontext.com baseline-mcp --transport http --port 8765

It serves /mcp on 127.0.0.1 and holds no key of its own: every request must carry the caller's key in an X-Api-Key (or Authorization: Bearer) header, and each tool call is made with that key, so it counts against that key's own quota. A request without a valid key gets a 401. The default, --transport stdio, is the local server shown above.

Contributing

This package is a thin translation layer: no climate logic lives here, and every tool call is an HTTP request to the Baseline Climate API. See CONTRIBUTING.md in the repository for local development setup.

MIT licensed.

來源:README.md,提交 379d7cc

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

3
  1. v0.1.9最新Sep 26, 2026
  2. v0.1.8Sep 22, 2026
  3. v0.1.1Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分