
oyapicks-mcp
io.github.topdawgyq/oyapicks-mcp
Prediction-market data as MCP tools, paid per call in USDC on Algorand or Base via x402.
Documentation
oyapicks-mcp
Prediction-market data as MCP tools. Pay per call in USDC on Algorand or Base. No API key, no account, no signup.
Read-only tools covering live market prices, keyword lookup, probability history, volume spikes, cross-venue price gaps, resolutions, and (on Algorand) the complete Alpha Arcade catalog. The data comes from Polymarket and Alpha Arcade. Prices run from $0.01 to $0.25 per call.
Today: 11 products, 21 paid endpoints. Ten products run on both rails and Alpha Book runs on Algorand only, so you get 11 tools on Algorand and 10 on Base. The live count is always at https://oyapicks.app/api/catalog.
Setup
Use a wallet with a little USDC. Treat it as petty cash, not your main wallet.
Pay on Algorand
The wallet needs USDC (opted in to ASA 31566704) and enough ALGO for its minimum balance.
The network fee on each payment is covered by the GoPlausible facilitator.
{
"mcpServers": {
"oyapicks": {
"command": "npx",
"args": ["-y", "oyapicks-mcp"],
"env": {
"OYAPICKS_ALGO_MNEMONIC": "your twenty five words"
}
}
}
}
Pay on Base
{
"mcpServers": {
"oyapicks": {
"command": "npx",
"args": ["-y", "oyapicks-mcp"],
"env": {
"OYAPICKS_WALLET_PRIVATE_KEY": "0xyourkey"
}
}
}
}
Set one wallet. If both are set, add "OYAPICKS_RAIL": "algorand" or "OYAPICKS_RAIL": "base".
- Claude Desktop:
claude_desktop_config.json - Cursor:
~/.cursor/mcp.json - Windsurf: MCP settings
What this can and cannot do with your key
Your key stays on your machine. It is never sent anywhere.
Before signing any payment, this server checks these and refuses if any fail:
- The recipient is the OyaPicks address for that network, hardcoded in
index.js. Nothing else. - The amount is at or under $0.30.
- The network is Algorand mainnet or Base mainnet, matching the wallet you configured.
- On Algorand, the asset is USDC (ASA
31566704).
The addresses are constants in the source, not read from the server's response, so a redirected
or spoofed endpoint cannot point payments somewhere else. Read index.js and check for yourself;
it is one file.
Tools
| Tool | What it returns | Price | Algorand | Base |
|---|---|---|---|---|
oyapicks_single_market | The single highest-volume live market for a keyword | $0.01 | yes | yes |
oyapicks_search | Live markets matching a keyword | $0.02 | yes | yes |
oyapicks_closing_soon | Markets resolving within 48 hours | $0.02 | yes | yes |
oyapicks_movers | The biggest probability swings since the last snapshot | $0.03 | yes | yes |
oyapicks_volume_spikes | The largest 24h volume jumps | $0.03 | yes | yes |
oyapicks_new_markets | Markets newly listed since the last snapshot | $0.03 | yes | yes |
oyapicks_probability_history | One market's YES price over time, by keyword | $0.03 | yes | yes |
oyapicks_resolutions | Recently resolved markets and the winning outcome | $0.03 | yes | yes |
oyapicks_arbitrage | The same outcome priced differently on the two venues | $0.05 | yes | yes |
oyapicks_analyze | The top three markets by 24h volume | $0.25 | yes | yes |
oyapicks_alpha_book | The entire live Alpha Arcade catalog in one call | $0.03 | yes | no |
That is the list on sale on 2026-11-18. Since v0.3.0 the tool list is not written into this package. The server reads https://oyapicks.app/api/catalog when it starts, and again every five minutes, and registers exactly the products that are on sale. When OyaPicks lists a new data product it appears in your client without you reinstalling anything, and a product that is withdrawn disappears the same way.
To see the current list and prices before installing, open https://oyapicks.app/api/catalog (free, no payment) or https://oyapicks.app/products.
Some products run on one rail only, so the number of tools differs between Algorand and Base. The server prints the count on startup.
If the catalogue cannot be reached, the server falls back to the prediction-market products above, which are always on sale (11 tools on Algorand, 10 on Base), and says so on stderr. The fallback can only offer fewer tools than the truth, never more.
On Algorand, a call that fails on the server side is never settled, so it costs nothing.
Changes
- 0.3.1: the Algorand rail works from a fresh install. 0.3.0 did not list the Algorand
payment libraries (
algosdk,@x402-avm/fetch,@x402-avm/avm) as dependencies, sonpx oyapicks-mcpwithOYAPICKS_ALGO_MNEMONICset stopped at startup with "Cannot find package 'algosdk'". Base was not affected. Nothing about payment changed. - 0.3.0: the tool list is read from the live catalogue instead of being written into the package.
License
MIT
oyapicks-mcpnpm install oyapicks-mcp