Home / MCP registry index / fans.ugc/studio
UGC Fans Studio
fans.ugc/studio in the official MCP registry.
Endpoint https://mcp.ugc.fans/studio. Source: github.com/ugcfans/claude-plugin.
The registry describes it as: Turn a website into a launch film; trim, caption and reformat your own clips
We read its 20 tools on 2026-10-26. 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
ugcfans_search_templates ugcfans_get_account ugcfans_find_business ugcfans_read_business ugcfans_get_business ugcfans_save_business ugcfans_capture_website ugcfans_get_capture ugcfans_make_launch_film ugcfans_make_site_sting ugcfans_ad_to_film ugcfans_set_film_words ugcfans_export_film ugcfans_finish_clip ugcfans_transcribe ugcfans_list_files ugcfans_share_file ugcfans_get_job ugcfans_wait_job ugcfans_cancel_job
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/fans-ugc-studio)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.