Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RulesWatch

REMOTE · RULESWATCH.COM

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

Available components

74 Trust /100

Last scanned (14 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +6
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “get_market” now declares an output schema ▲ functional
    • Tool “recent_rule_changes” now declares an output schema ▲ functional
    • 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” functional
    • “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 cosmetic
  • 20 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://ruleswatch.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ruleswatch.com CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 982d23a5d75138df0e6bbe6f4388459a
SANs: ruleswatch.com, www.ruleswatch.com, *.www.ruleswatch.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of ruleswatch.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
ruleswatch.com. DS published 2371 13 Verified
ruleswatch.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ruleswatch.com/api/mcp Verified 200
http (plaintext) http://ruleswatch.com/api/mcp HTTPS enforced 301 https://ruleswatch.com/api/mcp
MCP tools · 5 exposed · ~904 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_market ~208

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.

NameTypeReqDescription
history_limitinteger–How many recorded edits to return, newest first. Default 10.
idstringyesThe 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.
venuestringyespm (or polymarket) for Polymarket, kalshi for Kalshi.
NameTypeReqDescription
categorystring|null––
edits_recordedinteger|null––
end_datestring|null––
event_titlestring|null––
foundboolean––
historyarray––
history_notestring|null––
idstring|null––
messagestring|null––
relatedarray––
rulesarray––
rules_notestring|null––
seriesobject––
statusstring|null––
suggestionsarray––
titlestring|null––
urlstring|null––
venuestring|null––
venue_codestring|null––
venue_pagestring|null––
watch_linkstring|null––
yes_pricenumber|null––

No examples provided.

get_rule_change ~111

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

NameTypeReqDescription
idintegeryesThe edit's id, the number in its RulesWatch link.
NameTypeReqDescription
fieldsarray––
foundboolean––
idinteger|null––
kindstring|null––
kind_labelstring|null––
marketobject––
market_historyarray––
market_idstring|null––
market_titlestring|null––
market_urlstring|null––
messagestring|null––
other_markets_same_editarray––
recorded_atstring|null––
same_edit_on_other_marketsinteger|null––
summarystring|null––
urlstring|null––
venuestring|null––
yes_price_afternumber|null––
yes_price_at_editnumber|null––
yes_price_beforenumber|null––

No examples provided.

get_watch_link ~195

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.

NameTypeReqDescription
idstringyesThe 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.
venuestringyespm (or polymarket) for Polymarket, kalshi for Kalshi.
NameTypeReqDescription
alert_coversstring|null––
closed_notestring|null––
foundboolean––
idstring|null––
marketobject––
messagestring|null––
plansobject––
suggestionsarray––
venuestring|null––
watch_urlstring|null––
what_happensstring|null––

No examples provided.

recent_rule_changes ~228

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

NameTypeReqDescription
before_idinteger–For the next page: the next_before_id from the previous answer.
categorystring–Only markets in this category.
kindstring–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…
limitinteger–How many edits to return. Default 10.
querystring–Only edits on markets whose title holds these words, as a phrase.
venuestring–Only edits on this venue: pm (or polymarket) or kalshi.
NameTypeReqDescription
changesarray––
filtersarray––
moreboolean––
next_before_idinteger|null––
notestring|null––

No examples provided.

search_markets ~162

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.

NameTypeReqDescription
querystringyesOne or two distinctive title words ("Fed rate", "Senate Ohio"), a market id, a Kalshi ticker, or a Polymarket, Kalshi or RulesWatch market link.
venuestring–Only markets on this venue: pm (or polymarket) or kalshi. Leave out for both.
NameTypeReqDescription
changesarray––
changes_notestring|null––
marketsarray––
notestring|null––
searched_forstring|null––
venuestring|null––

No examples provided.

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.

remote · ruleswatch.com

# add to Claude Code
claude mcp add --transport http whosman-ruleswatch 'https://ruleswatch.com/api/mcp'
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.