Home / MCP registry index / com.googleapis.stitch/mcp
com.googleapis.stitch/mcp
com.googleapis.stitch/mcp in the official MCP registry.
Endpoint https://stitch.googleapis.com/mcp.
The registry describes it as: Interact with the Stitch API using natural language commands.
We read its 16 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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
create_project get_project delete_project list_projects list_screens get_screen download_file generate_screen_from_text edit_screens generate_variants upload_design_md create_design_system create_design_system_from_design_md update_design_system list_design_systems apply_design_system
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-googleapis-stitch-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.