Home / MCP registry index / ai.betslipdoctor/mcp
BetSlip Doctor
ai.betslipdoctor/mcp in the official MCP registry.
Endpoint https://api.betslipdoctor.ai/api/mcp. Source: github.com/opspot-ai/betslipdoctor-mcp.
The registry describes it as: Your agent grades every slip A+ to F-, links your books and tracks your record. No wager placement.
We read its 76 tools on 2026-10-21. 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
get_tracked_slips track_slip get_todays_board grade_slip get_saved_reports get_history_summary price_shop_slip doctor_conversation tail_read tail_post grade_pickem_entry quote_grade start_grade cancel_grade list_grade_jobs get_grade_job get_grade_progress get_grade_report get_grade_evidence open_doctor_conversation list_doctor_conversations get_doctor_conversation get_doctor_quota get_bettor_profile get_doctor_memory remember_doctor_note forget_doctor_note quote_doctor_reply start_doctor_reply get_doctor_job get_doctor_events cancel_doctor_reply get_doctor_parlays get_league_order get_doctor_picks get_tail_feed add_doctor_parlay_to_slip tail_react share_graded_ticket_to_tail tail_my_posts set_synced_record_consent set_show_my_record tail_hot get_tail_post preview_tail_post publish_tail_post create_tracked_slip revise_tracked_slip onboarding_preferences fade_post view_tail_analysis grade_settings set_profile_links list_sportsbooks connect_sportsbook refresh_sportsbook disconnect_sportsbook get_betting_leaks list_api_keys create_api_key and 16 more
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/ai-betslipdoctor-mcp)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.