Ext Ops Panel
Open dashboard
Comparison

Collatio Media Prediction vs FutureSearch MCP Server

Collatio Media Prediction is an MCP server published by collatiomedia.com. Marketplaces we read that list it: 1 (Official MCP Registry). FutureSearch MCP Server is an MCP server published by futuresearch. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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

Where each is published
MarketplaceCollatio Media PredictionFutureSearch MCP Server
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.27.0
Downloads/month (PyPI): 2 206
Downloads/week (PyPI): 818
Forks (GitHub): 9
Stars (GitHub): 57
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.27.0
Downloads/month (PyPI): 2 206
Downloads/week (PyPI): 818
Forks (GitHub): 9
Stars (GitHub): 57
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

Collatio Media Prediction vs FutureSearch MCP Server
FactCollatio Media PredictionFutureSearch MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub57
Forks (GitHub) (differs)No figure on GitHub9
Last releaseNot publishedNot published
Where it runs (differs)Remote server (collatiomedia.com/api/prediction/mcp)On your machine (futuresearch-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/futuresearch/futuresearch-python
Changes in the last 7 days00
First seen (differs)2026-10-162026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno remote endpoint we check

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

Collatio Media Prediction

In its own words, on Official MCP Registry:

Sports match probabilities and short explanations. Free API key required.

FutureSearch MCP Server

In its own words, on Official MCP Registry:

Forecast questions about the future, including the outcome under each option.

How to run each

Collatio Media Prediction As a remote MCP server

Claude Code
claude mcp add --transport http prediction https://collatiomedia.com/api/prediction/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

FutureSearch MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "FUTURESEARCH_API_KEY=<YOUR_FUTURESEARCH_API_KEY>" --transport stdio futuresearch-mcp -- uvx futuresearch-mcp

Requires: FUTURESEARCH_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Collatio Media Prediction has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Collatio Media Prediction publish no settings it asks for, so we do not compare settings.

What it can do: Collatio Media Prediction · What it can do: FutureSearch MCP Server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built