Receipts #009 — BROKEN: open-meteo-mcp (Receipts #009)
- Package: open-meteo-mcp, version 0.2.0 (PyPI), run as its README instructs:
python -m open_meteo_mcp. Tested 2026-10-29, clean venvs. - Task: current weather for New York City.
- Expected (ground truth): the Open-Meteo API fetched directly in the same minute (21:37–21:38 UTC), with tolerances set before grading: temperature ±1.5 °C, wind ±5 km/h, humidity ±5, pressure ±1.5 hPa, weather code exact.
- Observed: as installed per its README the server never answers initialize — it crashes at import:
ImportError: cannot import name 'McpError' from 'mcp' … Did you mean: 'MCPError'?
Pinning the SDK to the package's own declared floor (mcp==1.12.0) fails one import later inside FastMCP against today's pydantic; only TWO undocumented pins (mcp==1.12.0 AND pydantic==2.11.7) make it start. Cause: open-ended dependency ranges met two fatal upstream renames after 0.2.0 shipped. Even then, its "current" weather text reproduces the NEXT hour's forecast bucket digit-for-digit (gusts off by 7.6 km/h vs the API's actual current block, outside tolerance), and its two weather tools disagree with each other in the same minute.
- Verdict: Broken — a user installing this package today gets a traceback, not a weather server.
- Evidence refs: record 009; write-up tests/009-weather-server.md; transcripts tests/009-weather-transcript.txt (failed probe + both tracebacks) and tests/009-weather-transcript-pinned.txt.
Corrections and retest requests: open an issue on the Lantern Works repo naming the record id. Paid re-tests are accepted under the Receipts firewall: money can buy being measured sooner, never a changed verdict.
Need GPU prices in your own agent? Try a free, cited comparison. Back to the Receipts index.