The remote MCP endpoint is /mcp using Streamable HTTP. It is an invite beta and requires either an OAuth bearer grant or a new csd_sk_ service secret. Browser csd_pub_, legacy csd_, and widget credentials are never accepted.
ask_cricket: a finished answer from the existing query agent (query:run).lookup_player, discover_cricket_data, explore_values (tools:lookup).player_stats, head_to_head, leaderboard (tools:analyze).cricket_sql: secret credentials only, separately invited with sql:read, and only when the raw-SQL rollout is active.Raw SQL is limited to explicit columns in standard tables. Advanced tables, filesystem/network functions, catalogs, multiple statements, cross joins, and raw advanced SQL are unavailable.
Every call shares platform admission and durable minute/daily quotas. Results have row, byte, timeout, and concurrency bounds. Errors have stable codes and a request ID; they never include SQL, prompts, secrets, or internal exception text. Owners can inspect /api/mcp/usage, /api/mcp/quotas, and /api/mcp/errors, and revoke secrets through DELETE /api/mcp/credentials/{id}.
Standard descriptive data is derived from Cricsheet and returned with ODbL attribution. Use discover_cricket_data for the exact deployed coverage watermark and metric definitions. CricBit-derived answers retain CricBit attribution; restricted advanced data is not exposed through MCP.
Protected-resource metadata is available at /.well-known/oauth-protected-resource/mcp. OAuth scopes are necessary but do not replace local invitation entitlements or source policy.