Home / MCP registry index / app.pixly/pixly
Pixly
app.pixly/pixly in the official MCP registry.
Endpoint https://pixly.app/api/mcp.
The registry describes it as: Every visual AI tool for property listings — staging, enhancement, decluttering, cinematic video.
We read its 35 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
virtual_staging edit_staged_photo cinematic_motion photo_to_video before_after_reel flythrough_video before_after_image watermark_photos blur_faces_plates straighten_photo draw_floor_plan enhance_photo declutter_photo remove_furniture day_to_night replace_sky replace_lawn restyle_room reset_season makeover_exterior render_floor_plan touch_up_exterior upscale_hd plot_sign upload_image_from_url create_upload_ticket get_job list_library view_pixly_photo get_credit_balance list_listings create_listing update_listing plan_photos get_checkout_link
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-pixly-pixly)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.