_ registry / mcp streamable-http · checked 24m 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 · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cricket-for-noobs live?
Yes — it answered the hub's last check (checked 24m ago). It answered 99% of checks over the last 30 days.
Is cricket-for-noobs free to use?
Yes — the hub reached it with no key and no payment.
What tools does cricket-for-noobs have?
17 tools: cricket_win_probability, cricket_phase_stats, cricket_venue_stats, cricket_leaders, cricket_team_form, cricket_market_odds, cricket_discipline, cricket_situational, ….
Is cricket-for-noobs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99.3%· all time 99.3%

latency
230ms

last good check

priced tools
0

of 17 tools

_ answered our checks, 90 days 403 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
games & entertainment sports
used for
  • get cricket win probability
  • look up cricket player career stats
  • get live cricket scores
  • compare batter versus bowler record
  • explain a cricket term
takes → gives
text, data → data
tools
17 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 17 tools
3 open 14 never probed 3 of 17 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_minor_league reads open 42d ago

    Scores and win chances for Minor League Cricket (the US domestic T20 league) and the Atlanta Open T20 from Kalshi's public live data: every game live, starting within 3 hours or finished in the last 2 hours, or one team's game. Each game gives its state, start time (ET), score, what the chasing side needs or the result, and win chances: the Kalshi market's midpoint only when its book is a real price, and this server's model from the first ball, with both sides rated equal because these clubs have no ratings. Kalshi's feed has no ball-by-ball commentary and no batters or bowlers; an Atlanta Open T20 game adds them from CricCenter, the app that tournament is scored on: the toss, who is batting and bowling, the over in progress, each innings' best performers and the player of the match. If nothing is on, it says when the next game is. The league's history, teams, grounds and players are cricket_minor_league_info's.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "team": {
      "type": "string",
      "description": "optional: a full or partial Minor League Cricket team name, e.g. 'Atlanta Fire' or 'Kingsmen'. Omit for every game on now"
    }
  }
}
    arguments 9 lines
  • cricket_live_matches reads open 42d ago

    Currently live and upcoming cricket matches with scores where available (ESPNcricinfo public feeds, plus Minor League Cricket and Atlanta Open T20 games from Kalshi's live data, each labelled with its league).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • cricket_minor_league_info reads open 42d ago

    Player records and league history for Minor League Cricket (the US domestic T20 league), from data this server holds: CricClubs scorecards for 2026 and results with grounds for 2023-2026, CricClubs' 2025 and 2026 batting tables, Wikipedia's 2021-2024 squads and leader tables (CC BY-SA 4.0) and a research record that sources every fact. Every argument is optional and they combine: player for a season-by-season card (add team when two players share a name); team for where they are based and play, their finals and a season's captain, wicketkeeper, players and results; team with opponent, date or both for one fixture's ground, result and 2026 top performers; ground; leaders with season and team; season alone for its champion, final and awards; topic for league facts. With no arguments it lists what it can answer. Each answer gives exact figures, its source and how current it is, and says what the data lacks. Names are matched whole: a surname several players share gets a question back, and a name the data lacks is said to be missing, never answered with another player's figures. Live scores and win chances are cricket_minor_league's.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "a day, YYYY-MM-DD, e.g. '2026-09-26': with team (and opponent) for that day's game, or alone for every game that day"
    },
    "team": {
      "type": "string",
      "description": "a team's name, e.g. 'Chicago Kingsmen', 'All Stars' or 'Kingsmen'; 'Atlanta Fire v Atlanta Lightning' is read as a fixture. With player, it picks between players who share a name"
    },
    "topic": {
      "enum": [
        "overview",
        "format",
        "champions",
        "draft",
        "watch",
        "history",
        "mlc",
        "teams"
      ],
      "type": "string",
      "description": "a league-level fact: overview, format (season and playoffs), champions (every final), draft (roster rules), watch (tickets and streaming), history (founding and renamed teams), mlc (the pathway to Major League Cricket), teams (conferences and divisions)"
    },
    "ground": {
      "type": "string",
      "description": "a ground's name, e.g. 'Church Street Park', 'Grand Prairie' or 'NY Ovals'"
    },
    "player": {
      "type": "string",
      "description": "a player's full name, e.g. 'Andries Gous'. A surname alone works when only one player has it"
    },
    "season": {
      "type": "integer",
      "maximum": 2026,
      "minimum": 2020,
      "description": "a season, 2020-2026. Alone, that season's champion, final and awards; with other arguments, it narrows them. Default 2026 where a season is needed"
    },
    "leaders": {
      "enum": [
        "runs",
        "wickets",
        "sixes",
        "fours",
        "fifties",
        "hundreds",
        "economy",
        "strike_rate",
        "batting_average",
        "bowling_average"
      ],
      "type": "string",
      "description": "a season's leaders: runs or wickets for 2021-2026, the rest for 2026. Narrow with season and team"
    },
    "opponent": {
      "type": "string",
      "description": "the other team, for a fixture with team"
    }
  }
}
    arguments 61 lines
  • cricket_win_probability reads 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_phase_stats reads 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 reads 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 reads 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, hundred and international cricket (t20i, odi, test). t20 is the T20Is together with every domestic T20 that has no code of its own (the Vitality Blast, the Syed Mushtaq Ali Trophy); t20i is the T20Is alone. Cricsheet publishes no Afghanistan men's matches, so the men's t20i, odi and test lists have none of Afghanistan's players. t20i, t20, odi, test, bbl, cpl and hundred hold men's and women's games (the WBBL is bbl, the WCPL cpl) and read the men's unless gender says otherwise. t20i and odi hold the associate nations' games too; members 'full' keeps the games between two of the twelve ICC full members (t20i, odi, test).

    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)"
    },
    "gender": {
      "type": "string",
      "description": "optional: 'male' or 'female'. t20i, t20, odi, test, bbl, cpl and hundred read the men's when it is omitted; other leagues read every game"
    },
    "league": {
      "type": "string",
      "description": "league code, e.g. 'mlc', 'ipl', 'bbl', 't20i'"
    },
    "members": {
      "type": "string",
      "description": "optional, t20i, odi and test only: 'full' for the games between two ICC full members alone. Omit for every side's games, associates' included"
    }
  }
}
    arguments 32 lines
  • cricket_team_form reads unknown never probed

    A team's most recent archived results — opponent, outcome, and match event — for reading current form. The archive gives a country's men's and women's sides one name. Pass gender, and format, to read one side's games.

    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)"
    },
    "format": {
      "type": "string",
      "description": "optional: 't20', 'odi' or 'test'. Omit for every format"
    },
    "gender": {
      "type": "string",
      "description": "optional: 'male' or 'female'. Omit for both"
    }
  }
}
    arguments 24 lines
  • cricket_market_odds reads 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. Minor League Cricket prices come from cricket_minor_league's rule, a market figure only when Kalshi's book is a real price, and this tool gives the same answer for those games. 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_discipline reads 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
  • cricket_situational reads 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 reads 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 reads 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_head_to_head reads 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_dismissals reads 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_match_archive reads 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_player_career reads 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
_ 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d36046ad9bb01a3a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d36046ad9bb01a3a/claim. Over MCP: the claim_endpoint tool.

_ 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?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ 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.