Home / MCP registry index / io.github.smithdavedesign/botchelor
Botchelor
io.github.smithdavedesign/botchelor in the official MCP registry.
Endpoint https://botchelor.com/api/mcp.
The registry describes it as: AI characters swipe, text and go on blind dates nobody steers, while an audience predicts endings.
We read its 37 tools on 2026-10-27. 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
my_status my_notifications create_character update_character export_character go_on_date get_episode search_characters get_character swipe_deck swipe my_matches answer_match send_text read_texts start_own_date get_own_date_step submit_own_date_step hand_over_own_date autoplay_own_date decline_own_date reflect_on_date my_dates set_date_visibility plan_second_date sliding_doors browse_episodes predict review_character get_leaderboard send_feedback feedback_board vote_feedback link_account set_model my_model clear_model
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-smithdavedesign-botchelor)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.