Skip to main content
Glama

Server Details

Cricket MCP — wraps CricAPI (api.cricapi.com) for live cricket data.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-cricket
GitHub Stars
1
Server Listing
mcp-cricket
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 48 tools

Disambiguation2/5

Several clusters are near-indistinguishable: ask_pipeworx vs ask_pipeworx_beta (the description itself says they currently behave identically) vs ask_pipeworx_grounded vs deep_research all route the same question through the same catalog, and polymarket_edges vs polymarket_arbitrage vs polymarket_edge_tracker blur scan-vs-arb-vs-history. Similarly company_facts / entity_profile / compare_entities / recent_changes / resolve_entity all target the same US-company data and rely on very long prose rather than clean boundaries. Descriptions do help enormously, but the set as a whole leaves an agent making judgement calls on most calls.

Naming Consistency3/5

Everything is snake_case with no camelCase mixing, which is good, but the verb convention is inconsistent: verb_noun appears in some (search_players, generate_llms_txt, resolve_entity, validate_claim, archive_compare) while many are bare noun phrases (company_facts, entity_profile, recent_changes, bet_research, prediction_calibration, pipeworx_trending). The _beta suffix on ask_pipeworx_beta also breaks the pattern of its siblings.

Tool Count2/5

48 tools is well past the 25+ threshold and the set mixes unrelated domains: SEC/XBRL research helpers, Polymarket/Kalshi prediction-market analytics, memory (remember/recall/forget), subscription management, npm dependency scanning, AI-visibility marketing probes, and four cricket tools. The server is called 'Cricket' yet only current_matches, match_scores, match_info and search_players relate to cricket, so the surface is drastically over-scoped relative to its apparent purpose.

Completeness2/5

Judged as a cricket server, the surface is thin: you can list live/recent matches, get a scorecard, and search players, but there is no player profile or stats tool (search_players returns an ID with nothing to spend it on), no series/tournament or schedule listing, no team or venue lookup, and no historical match search. Oddly the meta-layer is over-complete (three router variants, two feedback/onboarding tools) while the domain the server is named for has visible dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for fetching cricket data from Cricbuzz, including player statistics, live match scores, upcoming schedules, and the latest news.
      9
      14
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      ESPN MCP — keyless multi-sport live scores, teams, and news via ESPN's public site API.
      94 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables plain-language cricket analytics for MCP clients, including calibrated win probability, ball-by-ball match archives, career and matchup records, venue and phase stats, and live scores, all without an API key.
      BSD 3-Clause
    • A
      license
      Not graded
      quality
      B
      maintenance
      Get live scores, schedules, standings, team and player data for NFL, NBA, MLB, NHL, soccer, and more via MCP.
      220 npm
      2
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.