Home / MCP registry index / com.create-web-page/create-web-page
Create Web Page
com.create-web-page/create-web-page in the official MCP registry.
Endpoint https://create-web-page.com/mcp. Source: github.com/daniel-lopez-puig/landings.
The registry describes it as: Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.
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
account_whoami page_intake_start page_onboarding_start page_onboarding_update source_import page_create page_create_from_brief block_add layouts_list presets_list page_get media_upload media_upload_link_create media_attach media_delete page_claim account_pages_list account_page_manage page_header_update page_theme_update page_meta_update page_preview page_publish page_unpublish block_update block_delete block_reorder
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-create-web-page-create-web-page)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.