io.github.AswaniSahoo/climate-ipcc-rag
IPCC AR6 Climate Retrieval
Is the IPCC AR6 Climate Retrieval MCP server down? Yes. It has given no valid answer since 2026-11-01: not found.
Search IPCC AR6 WG1 and answer with page-level citations, or refuse when unsupported.
not found down since 2026-11-01 · probed 2026-11-15 · unchanged since 2026-11-08
Error response from daemon: error from registry: unauthorized unauthorized
- Run it
- docker run -i --rm ghcr.io/aswanisahoo/climate-ipcc-rag-mcp:0.1.0 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/AswaniSahoo/climate-risk-agent
- Registry
- active, updated 2026-08-10 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Flutter MCP Toolkit io.github.Arenukvern/flutter-mcp-toolkit · alive
- Skill Steward MCP io.github.Arenukvern/steward-mcp · alive
- lastwords io.github.Arvo-AI/lastwords · alive
- supragnosis io.github.Ashon/supragnosis · alive
- Glasir io.github.Attackwave/glasir · crashed on start
- Cejel io.github.BargLabs/cejel · alive
- io.github.Beever-AI/beever-atlas · alive
- Cartographer io.github.BeppeTemp/cartographer · crashed on start
Servers that mention climate.
- CodePostalPro com.codepostalpro/postal-codes · alive
- Criora climate risk com.criora/criora · alive
- com.fininfostation/tw-finance · alive
- Kyrodata — Brazil Trade, Crop & Commodity Data com.kyrodata/kyrodata · alive
- Loxone AI com.loxoneai/loxone-ai · needs auth
- Nomad Forecast com.nomadforecast/mcp · needs auth
- NOAA Climate Data com.olyport/noaa-climate · alive
- PixelGust Environmental Data com.pixelgust/mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-01, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.