Home / MCP registry index / io.pagetool/pagetool

Pagetool

io.pagetool/pagetool in the official MCP registry. Endpoint https://pagetool.io/api/mcp.

The registry describes it as: Build and host websites from a chat: draft free, edit and theme, then publish to your own domain.

We read its 41 tools on 2026-11-17. 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 about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http pagetool https://pagetool.io/api/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "pagetool": {
      "url": "https://pagetool.io/api/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"pagetool","type":"http","url":"https://pagetool.io/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

create_site_from_brief create_site_from_html edit_section add_section add_page list_sections list_sites archive_site list_pages remove_page replace_page_html prowess_buy_domain publish_status record_review list_reviews live_check list_versions restore_version import_image set_client_record create_transfer_code publish_staged discard_staged set_theme get_preview_url draft_create export_site_html draft_claim domain_search purchase_link purchase_execute domain_register create_client_checkout cancel_client_checkout rename_site upsert_site_form list_form_submissions site_stats publish_site payment_status whoami

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-17): 9cb79c5141ca23be. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-pagetool-pagetool/badge.svg)](https://lazaretto.dev/mcp-registry/io-pagetool-pagetool)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.