_ registry / mcp streamable-http · checked 1h ago

cricket-for-noobs

https://cricketfornoobs.com

Registry code: d36046ad9bb01a3a

api record

Cricket win probability from a model fitted on 17,907 matches, plus archive stats and live scores.

from a public catalogue that lists it, not from the operator

endpoint
https://cricketfornoobs.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
232ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 15 tools
1 open 14 never probed 1 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • cricket_live_matches open 6h ago

    Currently live and upcoming cricket matches with scores where available (ESPNcricinfo public feeds).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • cricket_situational unknown never probed

    A batter's record batting first versus chasing, in limited-overs cricket: runs, balls, average and strike rate for each. Multi-day cricket is excluded rather than guessed at, since there the fourth innings is the chase and the first three are not comparable.

    mcp-tool

    {
  "type": "object",
  "required": [
    "player"
  ],
  "properties": {
    "player": {
      "type": "string",
      "description": "player name, e.g. 'V Kohli'"
    },
    "total_overs": {
      "type": "integer",
      "description": "restrict to one format: 20 for T20, 50 for ODI. Omit for all"
    }
  }
}
    arguments 16 lines
  • cricket_partnerships unknown never probed

    A batter's most productive partnerships: runs added while the two were at the crease together, how many stands, and their best. Stands are reconstructed by segmenting each innings at the wickets that fall, since the archive records the striker but not the non-striker.

    mcp-tool

    {
  "type": "object",
  "required": [
    "player"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "how many partners (default 8)"
    },
    "player": {
      "type": "string",
      "description": "player name, e.g. 'RG Sharma'"
    }
  }
}
    arguments 16 lines
  • cricket_explain_term unknown never probed

    Explain a cricket term in plain English with its closest baseball equivalent (wicket, yorker, googly, powerplay, DLS, and ~60 more).

    mcp-tool

    {
  "type": "object",
  "required": [
    "term"
  ],
  "properties": {
    "term": {
      "type": "string",
      "description": "cricket term, e.g. 'googly'"
    }
  }
}
    arguments 12 lines
  • cricket_win_probability unknown never probed

    Win probability for a limited-overs match, live or hypothetical, from a logistic model fitted on 8,000+ archived matches (per format and innings, with pre-match Elo). Pass a state for an in-play number, or just two team names for a fixture that has not started. Returns each side's probability and who is favored. Use for 'who is winning', 'what are the odds at X/Y', or 'who is favoured tomorrow'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "runs",
    "wickets",
    "overs",
    "total_overs",
    "innings"
  ],
  "properties": {
    "runs": {
      "type": "integer",
      "description": "runs scored so far by the batting side"
    },
    "overs": {
      "type": "number",
      "description": "overs bowled in cricket notation, e.g. 15.3 = 15 overs 3 balls"
    },
    "target": {
      "type": "integer",
      "description": "runs needed to win (second innings only)"
    },
    "innings": {
      "type": "integer",
      "description": "1 for the side setting a target, 2 for the chase"
    },
    "wickets": {
      "type": "integer",
      "description": "wickets lost so far (0-10)"
    },
    "total_overs": {
      "type": "integer",
      "description": "overs per side: 20 for T20 and The Hundred, 50 for ODI"
    },
    "batting_team": {
      "type": "string",
      "description": "team name; improves a live estimate via Elo, and with bowling_team alone prices a fixture that has not started"
    },
    "bowling_team": {
      "type": "string",
      "description": "optional team name, improves the estimate via Elo"
    },
    "balls_per_over": {
      "type": "integer",
      "description": "balls per over: 6 unless The Hundred, which bowls 5-ball sets — pass 5 there or every rate is a fifth off"
    }
  }
}
    arguments 48 lines
  • cricket_head_to_head unknown never probed

    Career batter-vs-bowler record from ball-by-ball archives: balls faced, runs scored, dismissals, strike rate. Cricket tracks these like baseball's batter-vs-pitcher splits.

    mcp-tool

    {
  "type": "object",
  "required": [
    "batter",
    "bowler"
  ],
  "properties": {
    "batter": {
      "type": "string",
      "description": "batter name, e.g. 'Virat Kohli' or 'V Kohli'"
    },
    "bowler": {
      "type": "string",
      "description": "bowler name, e.g. 'Jasprit Bumrah'"
    },
    "format": {
      "type": "string",
      "description": "'t20' or 'odi'; omit to try T20 then ODI"
    }
  }
}
    arguments 21 lines
  • cricket_player_career unknown never probed

    Career aggregate statistics for a player (men's and women's cricket) from Cricsheet ball-by-ball archives: innings, runs, strike rate, average, high score, wickets, economy — per format.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "player name, e.g. 'Rachin Ravindra'"
    }
  }
}
    arguments 12 lines
  • cricket_match_archive unknown never probed

    Look up an archived limited-overs match and return its scorecard: innings totals, top scorers, leading wicket-takers. Search by team names, league (mlc, ipl, bbl, psl, cpl), and/or year.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "free text, e.g. 'the 2025 IPL final' or 'Washington Freedom vs San Francisco Unicorns 2026'"
    }
  }
}
    arguments 12 lines
  • cricket_phase_stats unknown never probed

    How a player performs by phase of the innings — powerplay, middle overs, and the death — for batting and bowling. This is the split that separates a strike-rate merchant from a genuine finisher, computed from ball-by-ball archives.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "player name, e.g. 'Nicholas Pooran'"
    },
    "total_overs": {
      "type": "integer",
      "description": "20 for T20 (default), 50 for ODI/List-A"
    }
  }
}
    arguments 16 lines
  • cricket_venue_stats unknown never probed

    How a ground plays: matches recorded, average first-innings score, highest first-innings total, and how often the chasing side wins there. Useful for toss decisions and pre-match reads.

    mcp-tool

    {
  "type": "object",
  "required": [
    "venue"
  ],
  "properties": {
    "venue": {
      "type": "string",
      "description": "ground name or fragment, e.g. 'Grand Prairie' or 'Eden Gardens'"
    },
    "total_overs": {
      "type": "integer",
      "description": "20 for T20 (default), 50 for ODI/List-A"
    }
  }
}
    arguments 16 lines
  • cricket_leaders unknown never probed

    Leaderboards for a league and optional season: most runs or most wickets, from ball-by-ball archives. Leagues include mlc, ipl, bbl, psl, cpl and international cricket.

    mcp-tool

    {
  "type": "object",
  "required": [
    "league"
  ],
  "properties": {
    "kind": {
      "type": "string",
      "description": "'batting' (default) or 'bowling'"
    },
    "year": {
      "type": "string",
      "description": "optional season year, e.g. '2026'"
    },
    "limit": {
      "type": "integer",
      "description": "how many players to return (default 10)"
    },
    "league": {
      "type": "string",
      "description": "league code, e.g. 'mlc', 'ipl', 'bbl'"
    }
  }
}
    arguments 24 lines
  • cricket_team_form unknown never probed

    A team's most recent archived results — opponent, outcome, and match event — for reading current form.

    mcp-tool

    {
  "type": "object",
  "required": [
    "team"
  ],
  "properties": {
    "team": {
      "type": "string",
      "description": "team name, e.g. 'San Francisco Unicorns'"
    },
    "limit": {
      "type": "integer",
      "description": "how many recent matches (default 8)"
    }
  }
}
    arguments 16 lines
  • cricket_market_odds unknown never probed

    Live prediction-market prices for a cricket match from Kalshi (a CFTC-regulated US exchange), shown beside this server's own win probability so the two can be compared. Prices are cents that equal implied probability: 42 means the market prices a 42% chance. Informational only — not betting advice, and event contracts are legal only in some jurisdictions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "team_a",
    "team_b"
  ],
  "properties": {
    "team_a": {
      "type": "string",
      "description": "one team, e.g. 'San Francisco Unicorns'"
    },
    "team_b": {
      "type": "string",
      "description": "the other team, e.g. 'Guyana Amazon Warriors'"
    }
  }
}
    arguments 17 lines
  • cricket_dismissals unknown never probed

    How a batter gets out, or how a bowler takes wickets, across the ball-by-ball archive: bowled, caught, lbw, stumped, run out and the rest, with counts and shares. Run outs are excluded from the bowling view because they are not credited to the bowler.

    mcp-tool

    {
  "type": "object",
  "required": [
    "player"
  ],
  "properties": {
    "player": {
      "type": "string",
      "description": "player name, e.g. 'V Kohli'"
    },
    "perspective": {
      "type": "string",
      "description": "'batting' (default) for how they get out, 'bowling' for how they take wickets"
    }
  }
}
    arguments 16 lines
  • cricket_discipline unknown never probed

    Dot-ball percentage, boundary percentage and economy for a bowler, or the same rates faced by a batter. These are the numbers that decide limited-overs games well before the wickets column does, and no scorecard shows them.

    mcp-tool

    {
  "type": "object",
  "required": [
    "player"
  ],
  "properties": {
    "player": {
      "type": "string",
      "description": "player name, e.g. 'JJ Bumrah'"
    },
    "perspective": {
      "type": "string",
      "description": "'bowling' (default) or 'batting'"
    },
    "total_overs": {
      "type": "integer",
      "description": "restrict to one format: 20 for T20, 50 for ODI. Omit for all"
    }
  }
}
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d36046ad9bb01a3a/badge.svg)](https://brick.blue/agent/d36046ad9bb01a3a)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.