RulesWatch
Server Details
Polymarket and Kalshi market rules, with each recorded edit shown before and after.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- whosman/ruleswatch-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool has a distinct primary target: one market (get_market), one edit by id (get_rule_change), a list of new edits (recent_rule_changes), market lookup (search_markets), and watch-link generation (get_watch_link). The main soft overlap is between search_markets and get_market when a user names a market, but the descriptions clarify that search finds venue+id while get_market returns full rules and edit history, and get_market degrades gracefully with suggestions.
Four of five names follow a verb_noun pattern (get_market, get_rule_change, get_watch_link, search_markets), and the outlier recent_rule_changes is still readable and clearly a listing tool. Minor deviation in convention, not a source of confusion.
Five tools is well-scoped for a narrow read-only domain of prediction-market rule tracking. Each tool maps to a distinct user intent (find, inspect, list, drill into a change, subscribe via link), with no filler.
The read-only lifecycle is covered: discovery, market detail with edit history, individual change records, a recent-changes feed with filters, and a path to watching via link. Gaps are minor: no tool to enumerate or manage existing watches (deliberate, since watch creation happens in the browser), and no cross-market comparison, but core workflows have no dead ends.
Available Tools
5 toolsget_marketGet a market's rules and editsARead-onlyIdempotentInspect
One Polymarket or Kalshi market: the rules in force now, the resolution source, end date, open or closed status, Yes price, and every recorded edit to its rules, source, end date or title, newest first, with the removed and added words. Use it when the user asks what a market's rules say or whether they changed. An unknown id returns suggestions; a Kalshi series or event ticker returns the markets under it.
Inputs: id (required), venue (required), history_limit. Returns: id, url, found, rules, +18 more
get_rule_changeGet one rule editARead-onlyIdempotentInspect
One recorded rule edit by its id: the full text before and after on each changed field, the removed and added words, when it was recorded, the Yes price before, at and after, the other markets the same edit landed on, and the market's other edits. Ids come from a list of recent edits, a market's edit history, or a RulesWatch change link (/change/).
Inputs: id (required). Returns: id, url, kind, found, +16 more
get_watch_linkLink to watch a market for rule changesARead-onlyIdempotentInspect
Use when the user wants to be told, alerted or notified when a Polymarket or Kalshi market's rules, resolution source, end date or title change, or wants to watch, follow or track a market for rule edits. Returns a RulesWatch link that opens with that market ready to watch, what an alert covers, and the plan limits. It does not create a watch or change anything: the user opens the link and presses Watch. Needs the market's venue and id.
Inputs: id (required), venue (required). Returns: id, found, plans, venue, +7 more
recent_rule_changesRecent rule changesARead-onlyIdempotentInspect
The newest recorded edits to Polymarket and Kalshi market rules, newest first, each with the removed and added words, the Yes price at the edit and a link. Filter by venue, kind of edit, category or title words. Use it for questions like "what rules changed this week" or "any new Kalshi clarifications".
Inputs: kind, limit, query, venue, +2 more. Returns: more, note, changes, filters, +1 more
search_marketsSearch marketsARead-onlyIdempotentInspect
Find Polymarket and Kalshi markets by words in the title, an exact market id, a Kalshi series, event or market ticker, or a market link. Returns each market's venue, id, title, open or closed status, Yes price and RulesWatch link, and a few recent rule edits on matching titles. Use it to find a market's venue and id from its name or link.
Inputs: query (required), venue. Returns: note, venue, changes, markets, +2 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Polymarket resolution-rule research for approved customers; public discovery is separate.
Cross-venue Polymarket+Kalshi arbitrage: resolution mismatch, void risk & settlement divergence.
Polymarket vs Kalshi vs DraftKings, FanDuel and Pinnacle: prices, gaps, edge, alerts and history.
Calibrated probabilities for Kalshi markets, a news wire and Polymarket outliers (Pro).
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceReference data layer for prediction markets: resolution-clarity grades (A/B/C), named resolution sources with provenance, cross-venue linking, and per-contract eligibility screens across Kalshi and Polymarket. Open,read-only, no key required.3MIT
- AlicenseAqualityBmaintenance24/7 autonomous monitoring and edge detection for prediction markets (Kalshi & Polymarket). Features causal tree analysis, orderbook depth tracking, cross-venue comparison, and real-time alerts.16196 npm12MIT
- AlicenseNot gradedqualityFmaintenanceUnified access to prediction market data from Kalshi and Polymarket, enabling natural language queries for real-time odds, orderbooks, and trade history.13 npm11MIT
- AlicenseBqualityBmaintenanceForesea connects AI agents to prediction-market research: probability forecasts with cited evidence; Polymarket and Kalshi market scans, quotes, orderbooks and price history; weather and crypto analysis; and model-vs-market comparisons. Available through a hosted Streamable HTTP endpoint or a locally installed Python MCP server.28MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.