Cricsheet
NPM · @PIPEWORX/MCP-CRICSHEET · 2 COMPONENTS
cricsheet -- ball-by-ball cricket data collapsed to match / player / team questions (fleet #2975).
Available components
Last scanned (15 hours ago)
Scores higher than 62% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cricsheet). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1354 tokens (~270/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 64
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-cricsheet@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-cricsheet |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-cricsheet/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612296580 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:552dfe30c4752cc9f31273a2886a1fba257b1819312bf3331efb22c648893179f3504ad95904602efc8a6c1d13899bfa055d315d40149c1fa242b8914 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cricsheet_chase_search ~487
Compound cricket match search on the second innings (the chase): filter limited-overs matches (ODI, T20I, IPL) by whether the side batting second won or lost, wickets remaining and balls remaining at the end of the chase, date range, season, tournament/event, team, gender and format. Each hit returns target, chase score, wickets lost, balls used, wickets_remaining (10 minus wickets lost) and balls_remaining (scheduled overs minus legal balls bowled; null for rain-affected matches decided by a method such as DLS). Example: T20I chases won with 5+ wickets and 10+ balls to spare since 2024. Source: Cricsheet match data (ODC-BY). Tests are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Earliest match date, YYYY-MM-DD. |
| date_to | string | – | Latest match date, YYYY-MM-DD. |
| event | string | – | Tournament/event name or fragment, e.g. "World Cup" or "Indian Premier League". |
| format | string | – | Match format: "ODI", "T20I" or "IPL". Omit for all three. |
| gender | string | – | Men's or women's cricket. |
| limit | number | – | Max matches to return, 1-200. Default 25. |
| max_balls_remaining | number | – | At most this many legal balls unused (0 = chase went to the last ball). |
| max_wickets_remaining | number | – | Chasing side had at most this many wickets in hand at the end (0-10). |
| min_balls_remaining | number | – | At least this many legal balls unused at the end of the chase (assumes full scheduled overs; 120 in T20, 300 in ODI). |
| min_wickets_remaining | number | – | Chasing side had at least this many wickets in hand at the end (0-10). |
| offset | number | – | Pagination offset. Default 0. |
| season | string | – | Season label, e.g. "2024" or "2023/24". |
| second_innings_result | string | – | Did the side batting second win? Default "won" (a successful chase). |
| team | string | – | Chasing team name as Cricsheet uses it, e.g. "India". |
No output schema declared.
No examples provided.
cricsheet_find_matches ~266
Search Cricsheet's Test/ODI/T20I/IPL match index by team, format, season, venue and/or player, returning match_id plus date/teams/venue/result for each hit -- use this to discover match_ids for cricsheet_match. With no filters, returns the most recent matches across every format. Provide at least one filter to narrow a specific search.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Match format: "Test", "ODI", "T20I" (international T20), or "IPL". Omit to search across every format this pack holds. |
| limit | number | – | Max matches to return, 1-200. Default 50. |
| offset | number | – | Pagination offset. Default 0. |
| player | string | – | Exact player name as Cricsheet stores it (see cricsheet_player_stats to resolve a partial name first). |
| season | string | – | Season label as Cricsheet records it, e.g. "2023" or "2007/08". |
| team | string | – | Team name, e.g. "England" or "Chennai Super Kings" (IPL). |
| venue | string | – | Venue name or partial venue name, e.g. "Lord's". |
No output schema declared.
No examples provided.
cricsheet_head_to_head ~208
Head-to-head record between two cricket teams from Cricsheet's Test/ODI/T20I/IPL match data: total matches, each team's wins, ties/no-results, and the most recent matches with their results. Pass team names as Cricsheet uses them, e.g. "India", "Australia", "Mumbai Indians" (IPL). Optionally scope to one format with `format`.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Match format: "Test", "ODI", "T20I" (international T20), or "IPL". Omit to search across every format this pack holds. |
| limit | number | – | Max recent matches to list, 1-100. Default 10. |
| offset | number | – | Pagination offset into the recent-matches list. Default 0. |
| team_a | string | yes | First team name, e.g. "India". |
| team_b | string | yes | Second team name, e.g. "Australia". |
No output schema declared.
No examples provided.
cricsheet_match ~138
Full result and scorecard for one cricket match: teams, venue, date, toss, result, and for every innings the batting card (each batter's runs/balls/4s/6s/how out) and bowling card (each bowler's overs/runs/wickets). Covers Test, ODI and T20 International cricket plus the IPL (Cricsheet, ODC-BY). Use cricsheet_find_matches first to get a match_id if you don't already have one.
| Name | Type | Req | Description |
|---|---|---|---|
| match_id | number | yes | Cricsheet match id, e.g. 1082591. Get one from cricsheet_find_matches. |
No output schema declared.
No examples provided.
cricsheet_player_stats ~201
A cricketer's career batting and bowling aggregates (matches, runs, average, strike rate, 100s/50s; wickets, bowling average, economy) from Cricsheet's Test/ODI/T20I/IPL match data. Pass a name or partial name ("Kohli", "V Kohli") -- Cricsheet stores short-form names, so this matches case-insensitively and returns a candidate list if the name is ambiguous. Optionally scope to one format with `format`. Covers only matches Cricsheet has scored ball-by-ball, not a player's entire career.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Match format: "Test", "ODI", "T20I" (international T20), or "IPL". Omit to search across every format this pack holds. |
| player | string | yes | Player name or partial name, e.g. "Kohli" or "V Kohli". |
No output schema declared.
No examples provided.
How do I install the Cricsheet MCP server?
Cricsheet runs locally as an npm package, launched with npx -y @pipeworx/mcp-cricsheet. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-cricsheet
claude mcp add pipeworx-io-cricsheet -- npx -y @pipeworx/mcp-cricsheet
What is the Cricsheet MCP server?
Cricsheet is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cricsheet. cricsheet -- ball-by-ball cricket data collapsed to match / player / team questions (fleet #2975). This page covers its npm package (@pipeworx/mcp-cricsheet).
Is the Cricsheet MCP server safe to use?
Cricsheet scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Cricsheet MCP server expose?
Cricsheet exposes 5 tools: cricsheet_match, cricsheet_player_stats, cricsheet_head_to_head, cricsheet_find_matches, cricsheet_chase_search. Their descriptions and schemas cost roughly 1,300 tokens of context every time the server is loaded.
Is the Cricsheet MCP server still maintained?
Cricsheet is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Cricsheet MCP server under?
Cricsheet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Cricsheet MCP server?
VerifyMCP ran 15 checks on Cricsheet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Cricsheet: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.