Home / MCP registry index / io.github.resemble-ai/resemble-mcp
Resemble AI
io.github.resemble-ai/resemble-mcp in the official MCP registry.
Endpoint https://mcp.resemble.ai/mcp. Source: github.com/resemble-ai/resemble-mcp.
The registry describes it as: Resemble AI: deepfake detection, media intelligence, and watermarking actions, plus docs tools.
We read its 18 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
detect_deepfake get_detection detect_ai_text get_text_detection analyze_media ask_about_detection detect_watermark apply_watermark trace_audio_source list_detect_agents run_detect_agent_investigation get_detect_agent_run agent_detection_list_sites agent_detection_create_site agent_detection_update_site agent_detection_get_analytics agent_detection_list_sessions agent_detection_get_session
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-resemble-ai-resemble-mcp)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.