polybridge_searchLABSCO SUMMARY
The question does not need a market that already exists.
Search reaches across four relations — direct, upstream, downstream and correlated — so a question nobody has listed a market for still lands on markets that bear on it, and Forecast turns those into probabilities with the sources named rather than a number on its own. Two distinctions worth holding onto: search scores are relevance rankings and not probabilities, and the RVOL responses are curated backend JSON rather than trading analysis. Search and Forecast answer without a key at anonymous limits, so the sensible first move is putting a real question to it before deciding whether to ask for one.
What it is
A read-only bridge to prediction-market data for Claude Desktop. Search retrieves markets relevant to a question even when no exact market exists, Forecast synthesises them into probabilities with the source-market metadata attached, and a separate group of tools reads PolyBridge's realized-volatility models. It does not trade, place orders, hold custody or write anything.
What you get
- polybridge_search returns ranked prediction markets for a topic or question — the scores are relevance rankings, not probabilities
- When you do not name them, search covers all four dimensions: direct, upstream, downstream and correlated
- polybridge_forecast synthesises the evidence into a forecast with probabilities and the source-market metadata behind them
- The realized-volatility group reads model metadata and covered assets with polybridge_rvol_models and polybridge_rvol_assets, current forecasts and their history with polybridge_rvol_latest and polybridge_rvol_history, the actuals to compare against with polybridge_rvol_actuals, and feature snapshot metadata with polybridge_rvol_features_latest
- Every tool reads: none places a trade, submits an order, handles custody or performs a write action
Requirements
Distributed as an .mcpb package from GitHub Releases: download it, import it into Claude Desktop and enable the extension. Search and Forecast work with no key at anonymous limits, and POLYBRIDGE_API_KEY raises those limits — a single search_forecast key powers both. The RVOL tools require a key carrying rvol:read and have no anonymous path; an unapproved key means asking PolyBridge for access.
Setup effort
Follow the published steps — Download the latest .mcpb package from GitHub Releases.
USE CASES
01
Putting a probability on something nobody has listed
Find the markets that bear on the question across direct and correlated relations, then get a forecast built from them with the source markets shown.
02
Checking what the market already thinks
Retrieve the ranked prediction markets for a topic and read them yourself — the scores rank relevance, so the probabilities come from the markets rather than the ranking.
03
Reading a volatility forecast and what it was built on
The models available, the assets they cover, the current forecast and the feature snapshot behind it — with an approved key.
04
Judging whether a model has been right
Pull the forecast history alongside the recorded actuals and compare them, instead of taking the latest number on its own.
8 tools
Listed in project docs. Your client may show a different list.
polybridge_forecastpolybridge_rvol_modelspolybridge_rvol_assetspolybridge_rvol_latestpolybridge_rvol_historypolybridge_rvol_actualspolybridge_rvol_features_latestBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation. polybridge_search and polybridge_forecast work anonymously at lower limits. The six polybridge_rvol_* tools need a POLYBRIDGE_API_KEY with rvol:read scope plus PolyBridge approval, and an invalid key fails rather than falling back to anonymous.
INSTALLATION
Connect your client
Server setup
Download the latest .mcpb package from GitHub Releases.
Open or import the file in Claude Desktop.
Enable the extension.
Search and Forecast can run without an API key at anonymous limits. Configure POLYBRIDGE_API_KEY for higher Search/Forecast usage or approved RVOL access.
