get_consensusLABSCO SUMMARY
The market's number, not a pundit's.
One question returns the aggregated probability across several regulated prediction markets, plus the places where those markets currently disagree with each other.
What it is
A Python server serving Meridian Edge's aggregated prediction-market data. Consensus probabilities, divergence between venues, recent moves and settled outcomes come from multiple regulated prediction markets, updated every 10 minutes.
What you get
- get_consensus returns aggregated consensus probabilities for sports and politics events
- get_opportunities surfaces events where the markets show notable divergence from each other
- get_signals reports recent directional market moves
- get_markets lists the markets currently being tracked
- get_settlements returns recently settled events with verified outcomes
Requirements
Python. uvx meridian-edge-mcp runs it without an install step, or pip install meridian-edge-mcp. It runs on a built-in demo key with limited data; a free Meridian Edge API key in MERIDIAN_EDGE_API_KEY, 100 calls a day, gives full access.
Setup effort
One command — pip install meridian-edge-mcp
USE CASES
01
Getting a live probability for tonight's game
The consensus across venues comes back as a number, refreshed on a ten-minute cycle rather than remembered from training data.
02
Finding where the markets disagree
Divergence between venues is the signal worth looking at, and it is surfaced directly rather than reconstructed by hand.
03
Seeing what moved today
Recent directional moves say which way money went, which is often the news before the news.
04
Checking how an event actually resolved
Settled events come back with verified outcomes, so a claim about what happened can be checked rather than asserted.
05
Seeing what is being tracked at all
The list of active markets sets the boundary of what any of the other questions can answer.
5 tools
Listed in project docs. Your client may show a different list.
get_opportunitiesget_signalsget_marketsget_settlementsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
uvx on PATH
Optional
MERIDIAN_EDGE_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install meridian-edge-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"meridian-edge": {
"command": "uvx",
"args": [
"meridian-edge-mcp"
],
"env": {
"MERIDIAN_EDGE_API_KEY": "<YOUR_MERIDIAN_EDGE_API_KEY>"
}
}
}
}Cursor, Windsurf
JSON
{
"mcpServers": {
"meridian-edge": {
"command": "uvx",
"args": [
"meridian-edge-mcp"
]
}
}
}
