Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "sports-rules": {
      "type": "http",
      "url": "https://sports-rules.gumballtools.com/api/mcp"
    }
  }
}

claude mcp add --transport http sports-rules https://sports-rules.gumballtools.com/api/mcp

[mcp_servers.sports-rules]
url = "https://sports-rules.gumballtools.com/api/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sports-rules": {
      "type": "remote",
      "url": "https://sports-rules.gumballtools.com/api/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "sports-rules": {
      "type": "http",
      "url": "https://sports-rules.gumballtools.com/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=sports-rules&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vc3BvcnRzLXJ1bGVzLmd1bWJhbGx0b29scy5jb20vYXBpL21jcCJ9"
}

{
  "servers": {
    "sports-rules": {
      "type": "http",
      "url": "https://sports-rules.gumballtools.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "sports-rules": {
      "httpUrl": "https://sports-rules.gumballtools.com/api/mcp"
    }
  }
}

extensions:
  "sports-rules":
    enabled: true
    name: "sports-rules"
    type: streamable_http
    uri: "https://sports-rules.gumballtools.com/api/mcp"
    timeout: 300

Quality 86 / 100good

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene79 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations2 of 2 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: offside (destructiveHint, idempotentHint); offside_rule_contrast (destructiveHint, idempotentHint)
pass
tools.token_costabout 1,614 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

2 tools, about 1,614 tokens to load them all · tool set d034a6895843 · checked 2026-10-20 20:14 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 89 / 100

duplicate-repo

provenance85

liveness100

freshness85

hygiene80

+repository +dns-namespace +website +reachable +uptime-100% ~updated-45d-ago -duplicate-repo(16 names)

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://sports-rules.gumballtools.com/api/mcp` streamable-http	none	yes	100%	924 ms	2026-07-28	2026-10-20

Tools (2)

offsideread-only 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`, `situation` (zone-entry or tag-up), and `stick`. Returns: a verdict of offside, onside, or no-offside-offence — three outcomes, not two, because "in an offside position but no offence" is a real and common answer — plus every step with the decisive one flagged, warnings, and a disclaimer. THIS IS NOT AN OFFICIAL RULING. Relay the steps, not just the verdict: in a real call the procedure is the easy half and the inputs are the argument. Do not quote IFAB or NHL rule text; it is copyrighted and this tool does not reproduce it.

offside_rule_contrastread-only 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.

Schemas: list_tools.

Also listed as

15 other active names share this repository (showing 10): com.crontoenglish/cron-translator, com.gumballtools/amortize, com.gumballtools/body-metrics, com.gumballtools/check-digit, com.gumballtools/color-companion, com.gumballtools/due-date, com.gumballtools/equation-steps, com.gumballtools/iso-week, com.gumballtools/json-to-types, com.gumballtools/payload-validator

Similar MCP servers

More from com.gumballtools

And 8 more from this publisher.

Official server.json

{
  "name": "com.gumballtools/sports-rules",
  "title": "Sports Rules",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://sports-rules.gumballtools.com/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/bwalvoord/gumball",
    "source": "github"
  },
  "websiteUrl": "https://sports-rules.gumballtools.com",
  "description": "Work an offside call through IFAB Law 11 or NHL Rule 83, step by step."
}