Sports Rules
REMOTE · SPORTS-RULES.GUMBALLTOOLS.COM
Work an offside call through IFAB Law 11 or NHL Rule 83, step by step.
Available components
Last scanned (17 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 Security80
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1251 tokens (~625/item across 2 items; 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 5 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://sports-rules.gumballtools.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=*.gumballtools.com | CN=YR2,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | 579c7ba8490d1aad98ff68ba87896d83cdf |
| SANs: *.gumballtools.com, gumballtools.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sports-rules.gumballtools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| gumballtools.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sports-rules.gumballtools.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://sports-rules.gumballtools.com/api/mcp | HTTPS enforced | 308 | https://sports-rules.gumballtools.com/api/mcp |
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 →
offside Work an offside call through IFAB Law 11 or NHL Rule 83 ~1,134
Work an offside call through the published decision procedure — association football under IFAB Law 11, or ice hockey under NHL Rule 83 — and return every step, not just the verdict. Use this for any "was that offside" question in either sport. The two rules are structurally OPPOSITE and are routinely conflated, and there are four specific things that get answered wrong: SOCCER: 1. HANDS AND ARMS DO NOT COUNT, for anyone including goalkeepers. Only parts that could legally score are measured, and the boundary is the bottom of the armpit. This tool REFUSES to compute from an arm position rather than guessing where the shoulder was. 2. AN OFFSIDE POSITION IS NOT AN OFFENCE. It becomes one only with involvement in active play. Do not report "he was offside" when the answer is that he was in an offside position and uninvolved. `involvement` is REQUIRED once the geometry makes it decisive — the tool errors rather than assuming, so ask the user what the player actually did, and pass "none" if the answer is nothing. 3. No offside offence direct from a throw-in, goal kick, or corner. Absolute. 4. A DELIBERATE play by an opponent resets it; a deflection or a save does NOT. This is the distinction most arguments turn on. HOCKEY: 5. SKATES decide it. Not the stick, not the body. 6. Since 2021 a skate in the AIR above the blue line is still onside — the line is a plane, and ice contact is irrelevant. BUT this does not apply to tagging up on a delayed offside, where the skate must contact the line. Do not generalise the 2021 change to tag-ups. Input for soccer: positions along the attacking axis in metres, larger being nearer the opponents’ goal line — `attacker`, `ball`, `secondLastDefender`. Any consistent scale works; only the order matters. Optionally `restart`, `foremostPart`, `inOwnHalf`, `involvement`, `lastTouch`. Input for hockey: `rearSkate` in centimetres relative to the LEADING EDGE of the blue line, negative being the neutral-zone side. Optionally `skateOnIce`…
| Name | Type | Req | Description |
|---|---|---|---|
| attacker | number | – | SOCCER. Position of the attacker along the attacking axis, larger being nearer the opponents’ goal line. Any consistent scale; only the order matters. |
| ball | number | – | SOCCER. Position of the ball, same scale. |
| deliberatePlayCriteriaMet | array | – | SOCCER. Which of IFAB’s five deliberate-play criteria are met. Reported, not scored — there is no pass mark. |
| foremostPart | string | – | SOCCER. Which part the attacker position describes. Passing an arm or hand is REFUSED with an explanation: only parts that could legally score count, and the boundary is the bottom of the armpit. |
| inOwnHalf | boolean | – | SOCCER. A player in their own half cannot be in an offside position. |
| involvement | string | – | SOCCER. REQUIRED once the player is in an offside position — the call errors without it rather than assuming. An offside POSITION is not an offence; this is what turns it into one, and "none" is a co… |
| lastTouch | string | – | SOCCER. A DELIBERATE play by an opponent resets offside. A deflection, a save, or a rebound off the frame does NOT. |
| rearSkate | number | – | HOCKEY. The trailing skate in centimetres relative to the LEADING EDGE of the blue line — the edge nearer the attacking zone. Negative is the neutral-zone side; positive means it has broken the plane. |
| restart | string | – | SOCCER. There is NO offside offence direct from a throw-in, goal kick, or corner. Always ask which restart it was before answering. |
| secondLastDefender | number | – | SOCCER. Position of the SECOND-last opponent, same scale. Usually the last outfield defender, since the goalkeeper is normally the last. |
| situation | string | – | HOCKEY. zone-entry (default), or tag-up for clearing a delayed offside. The same skate position can give opposite answers. |
| skateOnIce | boolean | – | HOCKEY. Since 2021 this does NOT affect a zone entry — a skate above the plane is onside. It is decisive when tagging up, where the skate must contact the line. |
| sport | string | yes | Which rule book. The two are structurally opposite — do not mix them up. |
| stick | number | – | HOCKEY. Ignored, and reported as ignored. Skates decide it. |
No output schema declared.
No examples provided.
offside_rule_contrast How soccer offside and hockey offside differ ~117
Return the structural differences between soccer offside and hockey offside, dimension by dimension. Use this when someone asks how the two compare, or when you are about to reason about one sport using an intuition from the other — which is the commonest way to get either wrong. They differ on what part of the player is measured, when the picture freezes, whether position alone is an offence, what happens at exactly level, what resets the situation, and which restarts are exempt. Takes no arguments. Returns the comparison table.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Sports Rules MCP server?
Sports Rules is a hosted endpoint at https://sports-rules.gumballtools.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 · sports-rules.gumballtools.com
claude mcp add --transport http com-gumballtools-sports-rules 'https://sports-rules.gumballtools.com/api/mcp'
What is the Sports Rules MCP server?
Sports Rules is an MCP server listed in the public MCP registry as com.gumballtools/sports-rules. Work an offside call through IFAB Law 11 or NHL Rule 83, step by step. This page covers its hosted endpoint (https://sports-rules.gumballtools.com/api/mcp).
Is the Sports Rules MCP server safe to use?
Sports Rules scores 84 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 Sports Rules MCP server expose?
Sports Rules exposes 2 tools: offside, offside_rule_contrast. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.
Does the Sports Rules MCP server require authentication?
No. We connected to Sports Rules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sports Rules MCP server still maintained?
Sports Rules 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 Sports Rules MCP server?
VerifyMCP ran 13 checks on Sports Rules, 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.