Home / MCP registry index / com.blazesportsintel/college-baseball
com.blazesportsintel/college-baseball
com.blazesportsintel/college-baseball in the official MCP registry.
Endpoint https://sabermetrics.blazesportsintel.com/mcp. Source: github.com/ahump20/BSI.
The registry describes it as: Live NCAA DI college baseball scores, standings, schedules, rankings, and sabermetrics.
We read its 7 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
bsi_get_scoreboard bsi_get_standings bsi_get_rankings bsi_get_player_stats bsi_get_team_schedule bsi_get_match_detail bsi_search_intel
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-blazesportsintel-college-baseball)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.