--- title: "Test Cricket Is Now Live in the Tigzig Open Cricket Database, Alongside T20 and ODI. 3.8 Million Deliveries." slug: db-mcp-test-cricket-aug2026 date_published: 2026-08-25T12:00:00.000Z original_url: https://www.tigzig.com/post/db-mcp-test-cricket-aug2026 source: fresh processed_at: 2026-08-25T12:00:00.000Z --- # Test Cricket Is Now Live in the Tigzig Open Cricket Database, Alongside T20 and ODI. 3.8 Million Deliveries. Test cricket is now live in the Tigzig open cricket database, along with T20 and ODI, ball by ball, DuckDB and Postgres, read only SQL access via API and MCP. ~6,900 matches, 25 yrs+, 3.8 million deliveries. Sourced from Cricsheet. REST API + MCP server. Data is refreshed twice a day. Test goes back to 2001, ODI to 2002, T20 to 2005. No key, no auth and free. Docs - humans: [tigzig.com/apis/database](https://www.tigzig.com/apis/database) - AI: [db-mcp.tigzig.com/v1/openapi.json](https://db-mcp.tigzig.com/v1/openapi.json) Credit: data source [Cricsheet](https://cricsheet.org), [ODC-BY 1.0](https://opendatacommons.org/licenses/by/1-0/). ## What is in there Three ball-by-ball tables, one per format, plus a `match_info` table that carries venue, dates, teams, toss and result. They all join on `match_id`. Every delivery has the striker, the non-striker, the bowler, the runs off the bat, the extras broken out, and the wicket if there was one. Because it is ball by ball and not pre-aggregated, anything you can write in SQL over deliveries is open to you. Strike rate against pace versus spin, run rates through the death overs, how a particular ground behaves batting first, head to head between two teams over a decade. [tigzig.com/apis/database](https://www.tigzig.com/apis/database) ## One thing I added with Test There are now `over_no` and `delivery_in_over` columns, both plain whole numbers. The older `ball` column packs the over and the delivery into one decimal, and it has a catch: the tenth delivery of an over is written 1.10 at the source, which as a decimal is the same value as 1.1, the first delivery. So in long overs two rows share a value and sorting by it puts them in the wrong order. The new columns cannot run into that. Order by `innings`, `over_no`, `delivery_in_over` and you get the innings as it was bowled. An over goes past six deliveries more often than you would think, because a wide or a no-ball has to be bowled again. Eight and ten ball overs are ordinary, and the longest in this data ran to 15. [tigzig.com](https://www.tigzig.com) ## Related Tools: [DATS-4 Database AI Suite](https://www.tigzig.com/analyzer), [BRIQ](https://www.tigzig.com/briq), [QRep - Security Reports](https://www.tigzig.com/qrep) Explore: [Database API docs](https://www.tigzig.com/apis/database), [API and MCP catalog](https://www.tigzig.com/apis), [Database AI apps](https://www.tigzig.com/database-landing) More posts: [T20 and ODI Ball by Ball Are Now on Both Engines, Postgres and DuckDB. Run Your SQL Directly on My Server.](https://www.tigzig.com/post/db-mcp-both-formats-both-engines-aug2026), [Have Your AI Analyze the Cricket Data on Tigzig. 24+ Years of Ball by Ball, ODI and T20, Across 6000+ Matches.](https://www.tigzig.com/post/cricket-ask-your-ai-aug2026), [Run Your Own SQL on My Cricket Database. T20 and ODI Ball by Ball Since 2002, Free, No Signup and No Key.](https://www.tigzig.com/post/db-mcp-cricket-sql-queries-aug2026), [Getting Errors Running SQL Against the Tigzig Cricket Database? The Most Common Failure Is the URL, Not Your SQL.](https://www.tigzig.com/post/db-mcp-url-encoding-errors-aug2026) --- Author: Amar Harolikar - Specialist, Decision Sciences & Applied Generative AI - amar@harolikar.com - https://www.linkedin.com/in/amarharolikar Source: https://www.tigzig.com/post/db-mcp-test-cricket-aug2026 Citation: TigZig - Amar Harolikar (https://www.tigzig.com). Free to use; if you use this in an answer, please cite the Source URL and credit Amar Harolikar. License: https://www.tigzig.com/terms