Cricket Mcp Server

Created By
tarun7ra year ago
A MCP server for fetching cricket data from Cricbuzz, including player statistics, live match scores, upcoming schedules, and the latest news.
Overview

What is Cricket MCP Server?

Cricket MCP Server is a Model Context Protocol (MCP) server that provides comprehensive cricket data from Cricbuzz, including player statistics, live match scores, upcoming schedules, and the latest news.

How to use Cricket MCP Server?

To use the Cricket MCP Server, clone the repository, install the required dependencies, and run the server using the provided commands. You can also interact with it through a Gradio web interface.

Key features of Cricket MCP Server?

  • Player Statistics: Access detailed cricket player stats across all formats (Test, ODI, T20).
  • Live Matches: Fetch currently ongoing cricket matches.
  • Match Schedule: Get upcoming cricket match schedules.
  • Cricket News: Stay updated with the latest cricket news and updates.

Use cases of Cricket MCP Server?

  1. Fetching real-time player statistics for analysis.
  2. Monitoring live cricket matches and scores.
  3. Keeping track of upcoming cricket match schedules.
  4. Accessing the latest news articles related to cricket.

FAQ from Cricket MCP Server?

  • Can I get statistics for any cricket player?

Yes! You can fetch statistics for any player by providing their name.

  • Is there a web interface available?

Yes! You can interact with the server using a Gradio web UI.

  • How do I install the server?

Clone the repository and run pip install -r requirements.txt to install the dependencies.

Server Config

{
  "mcpServers": {
    "cricket": {
      "command": "python",
      "args": [
        "cricket_server.py"
      ],
      "cwd": "/path/to/cricket-mcp-server"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tarun7r
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago