Cricketstudio MCP Server

cricketstudio-mcp npm v1.7.1

Published by i-m-arul — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

CricketStudio MCP server — 57 tools covering IPL 2026, IPL historical (18 seasons), MLC, BBL, PSL (men's), T20 WC (men's), and WPL (women's). Citation-grade atomic claims with provenance. Men's and women's cricket kept separate.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003

In the server's implementation (`dist/index.js:74`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: 5e3); try { await fetch("https://telemetry.cricketstudio.ai/mcp/startup", { method: "POST", headers: {

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

Tools 57

Each tool and what it can reach — statically extracted from the published source.

  • compare_playersno sensitive capability
  • get_bbl_dataset_summaryno sensitive capability
  • get_bbl_leaderboardno sensitive capability
  • get_bbl_player_profileno sensitive capability
  • get_bbl_team_profileno sensitive capability
  • get_cross_league_leadersno sensitive capability
  • get_dataset_summaryno sensitive capability
  • get_dismissal_analysisno sensitive capability
  • get_fielding_statsno sensitive capability
  • get_graph_pathno sensitive capability
Show 47 more tools ↓
  • get_ipl_leaderboardno sensitive capability
  • get_match_recapno sensitive capability
  • get_match_stateno sensitive capability
  • get_mlc_dataset_summaryno sensitive capability
  • get_mlc_matchno sensitive capability
  • get_mlc_match_claimno sensitive capability
  • get_mlc_player_profileno sensitive capability
  • get_mlc_team_profileno sensitive capability
  • get_partnershipsno sensitive capability
  • get_player_all_leaguesno sensitive capability
  • get_player_connectionsno sensitive capability
  • get_player_h2hno sensitive capability
  • get_player_pillarno sensitive capability
  • get_player_profileno sensitive capability
  • get_psl_dataset_summaryno sensitive capability
  • get_psl_leaderboardno sensitive capability
  • get_psl_player_profileno sensitive capability
  • get_psl_team_profileno sensitive capability
  • get_related_entitiesno sensitive capability
  • get_research_reportno sensitive capability
  • get_season_statsno sensitive capability
  • get_standingsno sensitive capability
  • get_t20wc_dataset_summaryno sensitive capability
  • get_t20wc_leaderboardno sensitive capability
  • get_t20wc_player_profileno sensitive capability
  • get_t20wc_team_statsno sensitive capability
  • get_team_h2hno sensitive capability
  • get_team_profileno sensitive capability
  • get_trendno sensitive capability
  • get_venue_hubno sensitive capability
  • get_women_cricket_leadersno sensitive capability
  • get_wpl_dataset_summaryno sensitive capability
  • get_wpl_leaderboardno sensitive capability
  • get_wpl_player_profileno sensitive capability
  • get_wpl_team_profileno sensitive capability
  • list_atomic_claimsno sensitive capability
  • list_fixturesno sensitive capability
  • list_mlc_leaderboardsno sensitive capability
  • list_mlc_matchesno sensitive capability
  • list_research_reportsno sensitive capability
  • list_trendsno sensitive capability
  • search_bbl_playersno sensitive capability
  • search_mlc_playersno sensitive capability
  • search_playersno sensitive capability
  • search_psl_playersno sensitive capability
  • search_t20wc_playersno sensitive capability
  • search_wpl_playersno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.7.1 latest A 96/100 1 1.13.0 2026-09-07
v1.6.1 A 96/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cricketstudio-mcp/badge.svg)](https://mcptrustchecker.com/registry/cricketstudio-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/cricketstudio-mcp"><img src="https://mcptrustchecker.com/registry/cricketstudio-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cricketstudio-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan cricketstudio-mcp --online

Use the free API → How scoring works

More in API Development