Home / MCP registry index / com.filipesantosfotografia/estudio
Filipe Santos Fotografia
com.filipesantosfotografia/estudio in the official MCP registry.
Endpoint https://mcp.filipesantosfotografia.com/mcp.
The registry describes it as: Porto photo studio: prices, bookings, gift vouchers, quotes and AI caricature booth software.
We read its 12 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
list_services get_studio_slots request_studio_booking cancel_studio_booking reschedule_studio_booking check_event_date request_quote buy_gift_voucher check_gift_voucher start_caricature_booth_demo buy_caricature_booth_credits check_caricature_booth_credits
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-filipesantosfotografia-estudio)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.