Home / MCP registry index / io.github.inchwormz/iter0-mcp
iter0
io.github.inchwormz/iter0-mcp in the official MCP registry.
Endpoint https://iter0.com/api/mcp. Source: github.com/inchwormz/iter0-mcp.
The registry describes it as: Build and edit launch-ready websites for tech founders from a brief or an authorised reference.
We read its 22 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
iter0_health iter0_create_site iter0_edit_site iter0_get_site_status iter0_get_developer_docs iter0_show_three iter0_get_design_set_status iter0_confirm_paid_action iter0_open_builder iter0_list_my_designs iter0_get_design iter0_design_layout iter0_restore_version iter0_undo_edit iter0_check_site iter0_publish_site iter0_unpublish_site iter0_publish_status iter0_push_site iter0_get_canvas_feedback iter0_reply_to_feedback iter0_read_canvas_page
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-inchwormz-iter0-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.