Home / MCP registry index / com.talktoaleksandra/consultations
com.talktoaleksandra/consultations
com.talktoaleksandra/consultations in the official MCP registry.
Endpoint https://talktoaleksandra.com/mcp. Source: github.com/FotoRent/monorepo.
The registry describes it as: Published consultation details, live availability and booking handoff for Russian-language sessions.
We read its 10 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
get_practice_overview get_services_and_pricing get_faq get_inquiry_topics get_contact_options get_available_slots get_consultation_details prepare_booking_handoff search_resources get_preparation_checklist
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-talktoaleksandra-consultations)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.