foresight-engine vs Criora climate risk
foresight-engine is a plugin bundle for AI coding tools published by isanthoshgandhi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Criora climate risk is an MCP server published by criora.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  foresight-engine |   Criora climate risk |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.2.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | foresight-engine | Criora climate risk |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (criora.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/isanthoshgandhi/foresight-engine | github.com/thothbot/criora-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
foresight-engine
Strategic intelligence plugin for Claude Code. Give it any real-world forecasting question and it produces a structured four-scenario analysis (Probable, Plausible, Possible, Preferable) backed by live web signals, historical analogues, and deterministic probability scoring. Built on IFTF foresight methodology: STEEEP framework, Futures Cone, Cross-Impact Analysis, and Backcasting. Two-layer architecture: Python handles all deterministic arithmetic; Claude handles web search, reasoning, and scenario writing.
Criora climate risk
Climate and disaster risk for any place: warnings, floods, heat, storms, quakes, countries, map
How to run each
foresight-engine As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install foresight-engine@claude-communityCriora climate risk As a remote MCP server
claude mcp add --transport http criora https://criora.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Criora climate risk has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of foresight-engine nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: foresight-engine · What it can do: Criora climate risk · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.