# RulesWatch (remote · ruleswatch.com)

Polymarket and Kalshi market rules, with each recorded edit shown before and after.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ruleswatch.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/whosman-ruleswatch/api-mcp.md), [page](https://verifymcp.io/servers/whosman-ruleswatch/api-mcp)

## Channel facts

- Endpoint: `https://ruleswatch.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1116 tokens (~223/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RulesWatch MCP server?

RulesWatch is a hosted endpoint at https://ruleswatch.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http whosman-ruleswatch 'https://ruleswatch.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "whosman-ruleswatch": {
      "url": "https://ruleswatch.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "whosman-ruleswatch": {
      "type": "http",
      "url": "https://ruleswatch.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.whosman-ruleswatch]
url = "https://ruleswatch.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whosman-ruleswatch": {
      "type": "remote",
      "url": "https://ruleswatch.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whosman-ruleswatch --url 'https://ruleswatch.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  whosman-ruleswatch:
    url: "https://ruleswatch.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "whosman-ruleswatch": {
      "Transport": "http",
      "Url": "https://ruleswatch.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add whosman-ruleswatch -t streamable-http -u 'https://ruleswatch.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "whosman-ruleswatch": {
      "type": "http",
      "url": "https://ruleswatch.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +6)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_markets” rewrote its description, which is the text the model reads
- [security] Tool “get_market” rewrote its description, which is the text the model reads
- [security] Tool “recent_rule_changes” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “get_market” now declares an output schema
- [functional improvement] Tool “recent_rule_changes” now declares an output schema
- [functional improvement] Tool “search_markets” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → excellent
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “get_rule_change”
- [functional] New tool “get_watch_link”
- [cosmetic] “get_market” added an optional parameter “history_limit”
- [cosmetic] “recent_rule_changes” added an optional parameter “before_id”
- [cosmetic] “recent_rule_changes” added an optional parameter “category”
- [cosmetic] “recent_rule_changes” added an optional parameter “kind”
- [cosmetic] “recent_rule_changes” added an optional parameter “query”
- [cosmetic] “recent_rule_changes” added an optional parameter “venue”
- [cosmetic] “search_markets” added an optional parameter “venue”
- [cosmetic] “get_market” reworded the description of “id”
- [cosmetic] “get_market” reworded the description of “venue”
- [cosmetic] “recent_rule_changes” reworded the description of “limit”
- [cosmetic] “search_markets” reworded the description of “query”
- [cosmetic] Tool “get_market” changed its title: Get a market → Get a market's rules and edits

### 2026-11-20 (score 68)

First indexed and scored.

## MCP tools (5)

### `search_markets` (~162 tokens)

Search markets

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.

Input parameters:

- `query` (string, required): One or two distinctive title words ("Fed rate", "Senate Ohio"), a market id, a Kalshi ticker, or a Polymarket, Kalshi or RulesWatch market link.
- `venue` (string): Only markets on this venue: pm (or polymarket) or kalshi. Leave out for both.

Output parameters:

- `changes` (array)
- `changes_note` (string|null)
- `markets` (array)
- `note` (string|null)
- `searched_for` (string|null)
- `venue` (string|null)

### `get_market` (~208 tokens)

Get a market's rules and edits

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.

Input parameters:

- `history_limit` (integer): How many recorded edits to return, newest first. Default 10.
- `id` (string, required): The market id. Polymarket: the number in the market's id, like 562802. Kalshi: the market ticker, like KXFEDDECISION-26DEC-H25. A Polymarket or Kalshi link is not an id; search with the link instead.
- `venue` (string, required): pm (or polymarket) for Polymarket, kalshi for Kalshi.

Output parameters:

- `category` (string|null)
- `edits_recorded` (integer|null)
- `end_date` (string|null)
- `event_title` (string|null)
- `found` (boolean)
- `history` (array)
- `history_note` (string|null)
- `id` (string|null)
- `message` (string|null)
- `related` (array)
- `rules` (array)
- `rules_note` (string|null)
- `series` (object)
- `status` (string|null)
- `suggestions` (array)
- `title` (string|null)
- `url` (string|null)
- `venue` (string|null)
- `venue_code` (string|null)
- `venue_page` (string|null)
- `watch_link` (string|null)
- `yes_price` (number|null)

### `recent_rule_changes` (~228 tokens)

Recent rule changes

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".

Input parameters:

- `before_id` (integer): For the next page: the next_before_id from the previous answer.
- `category` (string): Only markets in this category.
- `kind` (string): Only this kind of edit: clarification (text added to settle a case), rules (rules text edited), source (resolution source changed), dispute (Polymarket outcome disputed), dates (end date moved), titl…
- `limit` (integer): How many edits to return. Default 10.
- `query` (string): Only edits on markets whose title holds these words, as a phrase.
- `venue` (string): Only edits on this venue: pm (or polymarket) or kalshi.

Output parameters:

- `changes` (array)
- `filters` (array)
- `more` (boolean)
- `next_before_id` (integer|null)
- `note` (string|null)

### `get_rule_change` (~111 tokens)

Get one rule edit

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/<id>).

Input parameters:

- `id` (integer, required): The edit's id, the number in its RulesWatch link.

Output parameters:

- `fields` (array)
- `found` (boolean)
- `id` (integer|null)
- `kind` (string|null)
- `kind_label` (string|null)
- `market` (object)
- `market_history` (array)
- `market_id` (string|null)
- `market_title` (string|null)
- `market_url` (string|null)
- `message` (string|null)
- `other_markets_same_edit` (array)
- `recorded_at` (string|null)
- `same_edit_on_other_markets` (integer|null)
- `summary` (string|null)
- `url` (string|null)
- `venue` (string|null)
- `yes_price_after` (number|null)
- `yes_price_at_edit` (number|null)
- `yes_price_before` (number|null)

### `get_watch_link` (~195 tokens)

Link to watch a market for rule changes

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.

Input parameters:

- `id` (string, required): The market id. Polymarket: the number in the market's id, like 562802. Kalshi: the market ticker, like KXFEDDECISION-26DEC-H25. A Polymarket or Kalshi link is not an id; search with the link instead.
- `venue` (string, required): pm (or polymarket) for Polymarket, kalshi for Kalshi.

Output parameters:

- `alert_covers` (string|null)
- `closed_note` (string|null)
- `found` (boolean)
- `id` (string|null)
- `market` (object)
- `message` (string|null)
- `plans` (object)
- `suggestions` (array)
- `venue` (string|null)
- `watch_url` (string|null)
- `what_happens` (string|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/whosman-ruleswatch/api-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 68

## Common questions

### What is the RulesWatch MCP server?

RulesWatch is an MCP server listed in the public MCP registry as io.github.whosman/ruleswatch. Polymarket and Kalshi market rules, with each recorded edit shown before and after. This page covers its hosted endpoint (https://ruleswatch.com/api/mcp).

### Is the RulesWatch MCP server safe to use?

RulesWatch scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the RulesWatch MCP server expose?

RulesWatch exposes 5 tools: search_markets, get_market, recent_rule_changes, get_rule_change, get_watch_link. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.

### Does the RulesWatch MCP server require authentication?

No. We connected to RulesWatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RulesWatch MCP server still maintained?

RulesWatch is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the RulesWatch MCP server?

VerifyMCP ran 13 checks on RulesWatch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ruleswatch.com/api/mcp
- Repository: https://github.com/whosman/ruleswatch-mcp
- Website: https://ruleswatch.com/
- Changelog RSS feed: https://verifymcp.io/servers/whosman-ruleswatch/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/whosman-ruleswatch/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/whosman-ruleswatch/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/whosman-ruleswatch/api-mcp
