MCP for AI agents
Model Context Protocol endpoint for Cursor, Claude Desktop, and custom agents — contests, verifiable draws, RankFuel leaderboards and RF Signals market technicals. MCP is a thin adapter over the same core services as the REST API — business logic lives in one place.
Related: Developer hub · REST API · Webhooks
What you get on paid plans
- AI contest assistant — chat-based builder in the dashboard
- MCP server — list contests, stats, CSV exports via standard MCP clients
- RF Signals tools — multi-timeframe trend, levels, ratios and scans for your agent (details)
- REST API + webhooks — same account keys for Make.com and Zapier
Free accounts can run unlimited contests; upgrade for the AI contest assistant, MCP, and integrations. Compare plans.
Setup
- Sign in to the dashboard and subscribe to any paid plan.
- Open Account → API keys & integrations and generate a key.
- Add the MCP server to your agent (Cursor example below).
Endpoints
| URL | Auth | Purpose |
|---|---|---|
https://app.rewardsfuel.com/api/mcp | Bearer rf_live_… | Full MCP server (paid tools) |
https://app.rewardsfuel.com/api/mcp/public | None | Free RFWIN tools (draw_winners, get_draw, verify_draw), RankFuel leaderboard tools (below) + RF Signals teaser (list_signal_tickers, daily-only get_signal, delayed one trading day) |
https://app.rewardsfuel.com/api/mcp/signals | None | RF Signals server (details): only list_signal_tickers and daily-only get_signal, delayed one trading day. Listed on the MCP Registry as com.rewardsfuel/signals |
https://app.rewardsfuel.com/api/mcp/leaderboards | None | RankFuel Leaderboards server (details): create_leaderboard, add_points, get_leaderboard, close_leaderboard. Listed on the MCP Registry as com.rewardsfuel/rankfuel |
API key needs mcp scope (included on new keys). Write tools also need write scope.
Cursor example
{
"mcpServers": {
"rewards-fuel": {
"url": "https://app.rewardsfuel.com/api/mcp",
"headers": {
"Authorization": "Bearer rf_live_YOUR_KEY"
}
}
}
}
Sample tools/list (what agents see)
Agents discover these tools via the standard MCP initialize + tools/list flow.
list_contests — no args get_contest — requires contestId argument get_contest_stats, export_contestants_csv, export_entries_csv - Write tools (with write scope): create/update/sync contest, entry methods, prizes
draw_winners, get_draw, verify_draw (free on /mcp/public too) - RankFuel leaderboards:
create_leaderboard, add_points, get_leaderboard, close_leaderboard (free on /mcp/public too) - RF Signals:
list_signal_tickers, get_signal, get_levels, compare_ratio, scan_signals
Sample tools/call (draw_winners, free)
POST https://app.rewardsfuel.com/api/mcp/public
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "draw_winners",
"arguments": {
"title": "Demo draw",
"contestants": ["alice@example.com", "bob@example.com"],
"prizes": [{ "name": "Gift card", "quantity": 1 }]
}
}
}
Paid tools — read
list_contests — accessible contests (owned + shared) with entry counts get_contest — details and entry methods get_contest_stats — totals and top contestants export_contestants_csv — unique contestants as CSV text export_entries_csv — all entry rows as CSV text
Paid tools — write (write scope)
create_contest — blank or full draft create update_contest — patch fields or status sync_contest — full draft reconcile create_entry_method / update_entry_method / delete_entry_method create_prize / update_prize / delete_prize
Free RFWIN tools
get_draw — who won an RFWIN draw. Argument draw: the proof link (https://rfwin.uk/d/<id>) or id. Returns title, organiser (station/show), date, entry count, prizes, masked winners and ordered backup winners, the fairness verdict and a ready-to-quote answer. verify_draw — was it fair. Recomputes the seed commitment, entry-list hash, drand beacon round (cross-checked with the drand network), draw digest, every win hash and every winner. Returns verdict (verified, verified_hash_level, partially_verified, mismatch, not_drawn_yet), each check, what the check does and doesn't prove, the hashes and a recipe. REST: GET https://rfwin.uk/api/draws/<id>/verify; every proof page also has a JSON twin at https://rfwin.uk/d/<id>.json. draw_winners — verifiable random draw with a public proof page on rfwin.uk (all accounts; also on /api/mcp/public). Free tier: up to 10,000 contestants per draw; optional alternates, station, show for radio-style giveaways, and visibility: public (default, indexable) or private (unlisted: works and verifies for anyone with the link, including get_draw and verify_draw, but sent with noindex, no JSON-LD, never listed). Returns visibility and a one-time manageToken for PATCH https://rfwin.uk/api/draws/<id>/visibility.
Ask your AI who won. Entrants and listeners can paste an RFWIN proof link into ChatGPT, Claude, Gemini, Perplexity or Grok and ask who won and whether it was fair: proof pages state the winners and a fresh fairness verdict in plain text and JSON-LD, and MCP clients can call verify_draw. Discovery: rfwin.uk/.well-known/mcp.json · rfwin.uk/openapi.json.
RankFuel leaderboards (free, no key)
Live leaderboards for radio stations and contests are a RankFuel product with their own MCP server:
add https://app.rewardsfuel.com/api/mcp/leaderboards to your MCP client (streamable HTTP, no auth). It is named RankFuel Leaderboards
(com.rewardsfuel/rankfuel on the official MCP Registry). The same four tools are also on https://app.rewardsfuel.com/api/mcp/public and the paid server.
Boards are shown at https://rfwin.uk/lb/<id> for now. Discovery card: https://app.rewardsfuel.com/api/mcp/leaderboards/server-card.json.
{
"mcpServers": {
"rankfuel-leaderboards": { "type": "http", "url": "https://app.rewardsfuel.com/api/mcp/leaderboards" }
}
}
Leaderboard tools
create_leaderboard — a free RankFuel points board for an on-air contest, no account. Arguments: station, contest, optional color (hex) and logoUrl (https). Returns boardId, publicUrl (https://rfwin.uk/lb/<id>), studioUrl (?mode=studio, for studio screens and OBS), embedUrl / embedHtml, and a secret block with the manageToken and manageUrl. The token is shown once and only its hash is stored: keep it private and never post it. Limits: 5 new boards per 10 minutes and 20 per day per connection; 500 listeners per board. add_points — boardId (id or board link), manageToken, listener, points (±1000, not 0), optional town and reason (call-in, trivia, check-in…). A new name is added to the board. Returns the listener's total and rank and the top 10. get_leaderboard — public standings, no token: boardId, optional top (1–100, default 10; ties at the cut-off kept). Returns ranked names, towns, points, open/closed and a ready-to-quote answer. close_leaderboard — boardId, manageToken, optional reopen: true. A closed board shows final standings.
Listener privacy. Names on a board are public: send a first name plus last initial or a nickname. The server shortens full names ("Jane Smith" → "Jane S.") and rejects anything that looks like a phone number or email. Leaderboard calls are limited to 30 a minute per IP (on /api/mcp/public that limit is shared with the RF Signals teaser). REST equivalents: POST https://rfwin.uk/api/lb, POST /api/lb/<id>/points, GET /api/lb/<id>?top=N, POST /api/lb/<id>/close (see rfwin.uk/openapi.json).
POST https://app.rewardsfuel.com/api/mcp/leaderboards
Content-Type: application/json
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": { "name": "create_leaderboard", "arguments": { "station": "CFAX 1070", "contest": "Summer Trivia" } } }
{ "jsonrpc": "2.0", "id": 2, "method": "tools/call",
"params": { "name": "add_points", "arguments": {
"boardId": "<boardId>", "manageToken": "<secret manageToken>",
"listener": "Jane S.", "town": "Langford", "points": 5, "reason": "call-in" } } }
{ "jsonrpc": "2.0", "id": 3, "method": "tools/call",
"params": { "name": "get_leaderboard", "arguments": { "boardId": "<boardId>", "top": 5 } } }
RF Signals tools (market technicals for agents)
Give your agent the same multi-timeframe read as the RF Signals dashboard:
trend on daily, weekly and monthly bars, whether the timeframes agree, key support/resistance, relative-strength ratios,
and 9/13 exhaustion counts. Computed from end-of-day data for the supported tickers
(currently AAPL, AMZN, GOOGL, META, MSFT, NVDA, QQQ, SPY, TSLA — call list_signal_tickers for the live list).
Tool Arguments Returns Tier list_signal_tickers— Supported tickers + latest bar date All (free included) get_signaltickerPrice, SMA 50/200, RSI(14), MACD(12,26,9), per-timeframe trend, alignment verdict, exhaustion setup (9) / countdown (13) Scout (free): daily only · Analyst+: daily, weekly, monthly get_levelstickerSupport/resistance levels + nearest above/below price Analyst+ compare_ratiotickerA, tickerBRatio A/B with the same indicators, trends and alignment Analyst+ scan_signalstickers? (max 25)One summary row per ticker Analyst+
Tiers
- Scout — Free plan:
list_signal_tickers and daily-only get_signal. - Analyst — Marketing Master and Promoter: adds weekly/monthly timeframes and alignment,
get_levels, compare_ratio, scan_signals. - Strategist — Promoter Pro: everything in Analyst.
- No key —
https://app.rewardsfuel.com/api/mcp/public or the Signals-only https://app.rewardsfuel.com/api/mcp/signals: list_signal_tickers + daily-only get_signal, delayed one trading day.
Your tier comes from the plan on the account that owns the API key — never from tool arguments. A tool above your tier returns tier_required with an upgrade link. Compare plans.
Every response includes data_as_of (last bar date) and "disclaimer": "Educational only, not investment advice." Unknown tickers return unknown_ticker with the supported list.
RF Signals MCP server (free, no key)
Want only the market tools? Add https://app.rewardsfuel.com/api/mcp/signals to your MCP client (streamable HTTP, no auth).
It is a separate server named RF Signals (com.rewardsfuel/signals on the official MCP Registry)
with two tools: list_signal_tickers and get_signal (daily timeframe, delayed one trading day, 30 calls/minute per IP).
Every result carries a fullAccess pointer to this paid server, where an rf_live_ key unlocks current data,
weekly/monthly timeframes, get_levels, compare_ratio and scan_signals.
Discovery card: https://app.rewardsfuel.com/api/mcp/signals/server-card.json.
{
"mcpServers": {
"rf-signals": { "type": "http", "url": "https://app.rewardsfuel.com/api/mcp/signals" }
}
}
Try it now (no key)
POST https://app.rewardsfuel.com/api/mcp/public
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "get_signal", "arguments": { "ticker": "NVDA" } }
}
Example result (Analyst tier, trimmed)
{
"ticker": "NVDA",
"tier": "analyst",
"data_as_of": "2026-11-12",
"price": 166.19,
"timeframes": {
"daily": { "sma50": 215.96, "sma200": 204.34, "rsi14": 25.99,
"macd": { "macd": -13.24, "signal": -9.08, "histogram": -4.16, "cross": null },
"trend": "down", "trendStrength": "weak",
"exhaustion": { "setup": { "direction": "buy", "count": 1 },
"countdown": { "direction": "buy", "count": 10, "completed": false } } },
"weekly": { "trend": "...", ... },
"monthly": { "trend": "...", ... }
},
"alignment": { "verdict": "mixed", "summary": "Mixed: ..." },
"disclaimer": "Educational only, not investment advice."
}
Relative strength: NVDA vs QQQ
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": { "name": "compare_ratio", "arguments": { "tickerA": "NVDA", "tickerB": "QQQ" } }
}
Prefer HTTP? The same data is on the REST API under /api/v1/signals.
RF Signals provides educational tools for technical analysis. Not investment advice. Past performance is not indicative of future results.
Protocol
JSON-RPC 2.0 over HTTP (POST). Supported methods:
initialize tools/list tools/call ping
GET /api/mcp returns server metadata (no auth required for discovery).
Security
- Token-scoped authz: account scope comes from your API key, never from tool arguments. Agents cannot pass
accountId to access another tenant. - Least privilege: use
read + hooks for export-only agents; add write only when agents must configure contests. - Rate limit: 60 tool calls/minute per API key. Public RF Signals calls: 30/minute per IP.
- Audit: MCP calls are logged server-side by account and key.
REST vs MCP vs webhooks
Integration Best for Webhooks Make/Zapier real-time triggers (new entrant, winner picked) REST v1 Scheduled exports, polling, custom backends, HTTP mutations with write MCP Cursor, Claude, and other AI agents (contests + RF Signals)
Questions? Contact us.