Home / MCP registry index / com.usetyton/tyton
Tyton
com.usetyton/tyton in the official MCP registry.
Endpoint https://mcp.usetyton.com/mcp. Source: github.com/usetyton/tyton-mcp.
The registry describes it as: Audit and set up Meta Pixel and the Conversions API from your AI agent.
We read its 27 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
start_signup get_signup_status delete_connected_project save_capi_token save_audit_to_project get_setup_progress check_live_setup get_sdk_installation approve_conversion_plan approve_and_start_conversion_plan read_conversion_installation stage_conversion_installation read_conversion_plan propose_conversion_plan begin_audit read_audit record_audit_context record_audit_runtime connect audit_site setup_tracking setup_server setup_status verify_install tracking_status submit_findings read_docs
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-usetyton-tyton)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.