crickey

crickey is an MCP server that answers cricket statistics questions from Cricinfo Statsguru with proof links.

crickey is for personal use at the user's own risk, Cricinfo's terms ban data-extraction tools, and crickey isn't affiliated with Cricinfo, ESPNcricinfo or ESPN.

Start it

Docker image: ghcr.io/syedhassaanahmed/crickey, tagged as a version (0.1.0), a minor version (0.1) and latest. The commands use 0.1, which gets its patch releases.

docker run -d --rm --read-only --name crickey -p 127.0.0.1:8765:8765 ghcr.io/syedhassaanahmed/crickey:0.1

Keep that container running before MCP clients connect; after a reboot, run it again. Check it: open http://127.0.0.1:8765/health in a browser; it shows {"status":"ok"}.

Stop it:

docker stop crickey

Update: pull the latest patch release, then stop the container and run it again.

docker pull ghcr.io/syedhassaanahmed/crickey:0.1

Pass a setting with -e:

docker run -d --rm --read-only --name crickey -p 127.0.0.1:8765:8765 -e CRICKEY_MIN_INTERVAL=15s ghcr.io/syedhassaanahmed/crickey:0.1

Related MCP server: cricket-mcp

Connect a client

Use this URL in your MCP client: http://127.0.0.1:8765/mcp. It isn't a web page, so a browser shows a "Missing session ID" error. If your client has a tool timeout, set it to 5 minutes.

{
  "mcpServers": {
    "crickey": {
      "type": "http",
      "url": "http://127.0.0.1:8765/mcp"
    }
  }
}

Copilot CLI:

copilot mcp add --transport http --timeout 300000 crickey http://127.0.0.1:8765/mcp

Settings

Requests are slow because crickey waits 15 seconds between Cricinfo requests by default. The cache is only in memory, so it resets when the container stops. Run one container for all your clients so they share the cache, request spacing and block pause.

Debug stdio:

docker run -i --rm --read-only ghcr.io/syedhassaanahmed/crickey:0.1 stdio

Contributors: see AGENTS.md.