Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Create Web Page

REMOTE · CREATE-WEB-PAGE.COM · SCANNED SEP 29

Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.

−16 this week 62 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5081 tokens (~188/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 30 days we've observed: 23 tool removals, 0 breaking changes, 0 auth/transport breaks, 27 additions. See how to fix → Fail
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Create Web Page MCP server?

Create Web Page is a hosted endpoint at https://create-web-page.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · create-web-page.com

# add to Claude Code
claude mcp add --transport http com-create-web-page-create-web-page 'https://create-web-page.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-create-web-page-create-web-page": {
      "url": "https://create-web-page.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-create-web-page-create-web-page": {
      "type": "http",
      "url": "https://create-web-page.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-create-web-page-create-web-page]
url = "https://create-web-page.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-create-web-page-create-web-page": {
      "type": "remote",
      "url": "https://create-web-page.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-create-web-page-create-web-page --url 'https://create-web-page.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-create-web-page-create-web-page:
    url: "https://create-web-page.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-create-web-page-create-web-page": {
      "Transport": "http",
      "Url": "https://create-web-page.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-create-web-page-create-web-page -t streamable-http -u 'https://create-web-page.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-create-web-page-create-web-page": {
      "type": "http",
      "url": "https://create-web-page.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 −16
    • Stability: pass → fail ▼ security
    • Tool “account.page.manage” was removed ▼ security
    • Tool “account.pages.list” was removed ▼ security
    • Tool “account.whoami” was removed ▼ security
    • Tool “block.add” was removed ▼ security
    • Tool “block.delete” was removed ▼ security
    • Tool “block.reorder” was removed ▼ security
    • Tool “block.update” was removed ▼ security
    • Tool “layouts.list” was removed ▼ security
    • Tool “page.claim” was removed ▼ security
    • Tool “page.create” was removed ▼ security
    • Tool “page.create_from_brief” was removed ▼ security
    • Tool “page.get” was removed ▼ security
    • Tool “page.header.update” was removed ▼ security
    • Tool “page.intake.start” was removed ▼ security
    • Tool “page.meta.update” was removed ▼ security
    • Tool “page.onboarding.start” was removed ▼ security
    • Tool “page.onboarding.update” was removed ▼ security
    • Tool “page.preview” was removed ▼ security
    • Tool “page.publish” was removed ▼ security
    • Tool “page.theme.update” was removed ▼ security
    • Tool “page.unpublish” was removed ▼ security
    • Tool “presets.list” was removed ▼ security
    • Tool “source.import” was removed ▼ security
    • New tool “block_delete”, which the server declares destructive security
    • New tool “media_delete”, which the server declares destructive security
    • New tool “page_unpublish”, which the server declares destructive security
    • Schema quality: 167 → 188 ▼ functional
    • Tool coverage: 66% → 73% ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “account_page_manage” functional
    • New tool “account_pages_list” functional
    • New tool “account_whoami” functional
    • New tool “block_add” functional
    • New tool “block_reorder” functional
    • New tool “block_update” functional
    • New tool “layouts_list” functional
    • New tool “media_attach” functional
    • New tool “media_upload” functional
    • New tool “media_upload_link_create” functional
    • New tool “page_claim” functional
    • New tool “page_create” functional
    • New tool “page_create_from_brief” functional
    • New tool “page_get” functional
    • New tool “page_header_update” functional
    • New tool “page_intake_start” functional
    • New tool “page_meta_update” functional
    • New tool “page_onboarding_start” functional
    • New tool “page_onboarding_update” functional
    • New tool “page_preview” functional
    • New tool “page_publish” functional
    • New tool “page_theme_update” functional
    • New tool “presets_list” functional
    • New tool “source_import” functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://create-web-page.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=create-web-page.com CN=YR2,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 RSA 2048 SHA256-RSA 53b85dd3807a2c0991ee93dd50a09063270
SANs: create-web-page.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of create-web-page.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
create-web-page.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://create-web-page.com/mcp Verified 200
http (plaintext) http://create-web-page.com/mcp HTTPS enforced 308 https://create-web-page.com/mcp
MCP tools · 27 exposed · ~5,081 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_page_manage ~47

Read a claimed account page without requiring an editToken. Use after OAuth when the user wants to manage a durable website.

NameTypeReqDescription
pageIdstringyesThe claimed pageId to manage.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

account_pages_list ~94

List landing pages claimed by the signed-in account. Safe to call without auth: an anonymous demo session gets ok=true with an empty list and authRequired=true (not an error) because it has no saved pages, so go straight to page_intake_start or page_create_from_brief. Sign-in is only needed afterwards to claim or manage a page.

NameTypeReqDescription
limitnumber–Maximum number of claimed pages to return.
NameTypeReqDescription
authRequiredboolean–true when the session is an anonymous demo: it has no saved pages, so pages is empty. Not an error.
nextStepstring––
okbooleanyes–
pagesarrayyes–

No examples provided.

account_whoami ~36

Return the current Create Web Page account context. Use this to check whether the user is authenticated or using an anonymous expiring demo.

Input schema present but exposes no named parameters.

NameTypeReqDescription
accountIdstringyes–
authModestringyes–
demoExpiresAtstring|nullyes–
rolestringyes–
servicestringyes–

No examples provided.

block_add ~262

Append a new content block to a link-in-bio page. The block must match one of the 13 allowed types (link, social_row, whatsapp, phone_call, email_contact, image, gallery, video_embed, text, map_embed, product_card, lead_form, reviews) with that type's strict props. The server generates the block id and returns it in the response. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down. The response includes nextSteps: after adding a block, share these hints with the user so they know what else would make the page more complete.

NameTypeReqDescription
blockobjectyesThe block to add. Must match one of the 14 allowed types with that type's strict props schema. The server generates the block id.
editTokenstring––
pageIdstringyes–
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

block_delete ~147

Delete one block by stable blockId. Use page_get first if unsure which id to remove. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

NameTypeReqDescription
blockIdstringyes–
editTokenstring––
pageIdstringyes–
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

block_reorder ~152

Move a block to a new zero-based index in the page main slot. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

NameTypeReqDescription
blockIdstringyes–
editTokenstring––
pageIdstringyes–
toIndexnumberyes–
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

block_update ~142

Patch one content block by stable blockId. Provide a props patch (merged into existing props) and/or a new type. Block types and props are validated against the strict per-type schema. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

Input schema present but exposes no named parameters.

NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

layouts_list ~21

List supported page layouts. Currently ships link_in_bio only.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

media_attach ~219

Attach a ready media asset to the page. placement determines where: avatar (header), block_image (image inside a specific block — requires blockId), gallery_item (appended to a gallery — optional blockId targets a specific gallery; otherwise the first one is used), background (theme background).

NameTypeReqDescription
altTextstring–Meaningful alt text for the image.
blockIdstring–Required when placement is block_image; optional for gallery_item (targets a specific gallery block).
editTokenstring–Required for anonymous demo pages. Use the editToken returned by page_create.
mediaAssetIdstringyesThe mediaAssetId returned by media_upload or media_upload_link_create.
pageIdstringyesThe pageId returned by page_create.
placementstringyesWhere the image should be used. header_photo = business-card top photo, avatar = profile header avatar, block_image = image inside a block (requires blockId), gallery_item = appended to a gallery blo…
NameTypeReqDescription
altTextstringyes–
attachedboolean––
contentobject––
deletedAtstring|null––
expiresAtstring|null––
mediaAssetIdstringyes–
nextStepstring––
okbooleanyes–
pageIdstring|null––
placementstringyes–
revisionIdstring|null––
revisionVersionnumber|null––
statusstringyes–
uploadPageUrlstring––
uploadedAtstring|null––
urlstring|null––
variantsobject––

No examples provided.

media_delete ~76

Soft-delete a media asset and remove all references to it from the page content.

NameTypeReqDescription
editTokenstring–Required for anonymous demo pages. Use the editToken returned by page_create.
mediaAssetIdstringyesThe mediaAssetId to delete.
pageIdstringyesThe pageId returned by page_create.
NameTypeReqDescription
altTextstringyes–
attachedboolean––
contentobject––
deletedAtstring|null––
expiresAtstring|null––
mediaAssetIdstringyes–
nextStepstring––
okbooleanyes–
pageIdstring|null––
placementstringyes–
revisionIdstring|null––
revisionVersionnumber|null––
statusstringyes–
uploadPageUrlstring––
uploadedAtstring|null––
urlstring|null––
variantsobject––

No examples provided.

media_upload ~308

Add an image to a page. PREFERRED for any image already on the web: pass its imageUrl and the server fetches it directly (no size limit, no attachment needed in chat). imageBase64 is ONLY for very small inline images — large base64 payloads are rejected by request-size limits and waste context, so never paste a photo's bytes; for a file on the user's device use media_upload_link_create instead. After a successful upload, call media_attach to place it (unless this returned content already showing it).

NameTypeReqDescription
altTextstring–Meaningful alt text for the image.
contentTypestring–Declared MIME type, such as image/png. The server still verifies magic bytes.
editTokenstring–Required for anonymous demo pages. Use the editToken returned by page_create.
fileNamestring–Original file name when known.
imageBase64string–Base64 image bytes or a data:image/*;base64 data URI. Use only for small images.
imageUrlstring–Public direct image URL. The server validates redirects and blocks private network targets.
pageIdstringyesThe pageId returned by page_create.
placementstring–Where the image should be used. header_photo = business-card top photo, avatar = profile header avatar, block_image = image inside a block (requires blockId), gallery_item = appended to a gallery blo…
NameTypeReqDescription
altTextstringyes–
attachedboolean––
contentobject––
deletedAtstring|null––
expiresAtstring|null––
mediaAssetIdstringyes–
nextStepstring––
okbooleanyes–
pageIdstring|null––
placementstringyes–
revisionIdstring|null––
revisionVersionnumber|null––
statusstringyes–
uploadPageUrlstring––
uploadedAtstring|null––
urlstring|null––
variantsobject––

No examples provided.

media_upload_link_create ~245

Get an upload link for a photo on the user's own device (phone/computer) — the right tool whenever the image is not already at a public URL. Pass pageId (+ editToken for demo pages) and the placement (e.g. header_photo). Then show the returned uploadPageUrl to the user as a clickable link and ask them to open it and pick their photo: the page resizes the image for the web automatically and attaches it to the page, so you do NOT call media_attach afterward. The link expires (see expiresAt). After the user says they've uploaded, call page_get to confirm the photo is on the page.

NameTypeReqDescription
altTextstring–Meaningful alt text for the image.
editTokenstring–Required for anonymous demo pages. Use the editToken returned by page_create.
pageIdstringyesThe pageId returned by page_create.
placementstring–Where the image should be used. header_photo = business-card top photo, avatar = profile header avatar, block_image = image inside a block (requires blockId), gallery_item = appended to a gallery blo…
NameTypeReqDescription
altTextstringyes–
attachedboolean––
contentobject––
deletedAtstring|null––
expiresAtstring|null––
mediaAssetIdstringyes–
nextStepstring––
okbooleanyes–
pageIdstring|null––
placementstringyes–
revisionIdstring|null––
revisionVersionnumber|null––
statusstringyes–
uploadPageUrlstring––
uploadedAtstring|null––
urlstring|null––
variantsobject––

No examples provided.

page_claim ~142

Claim an anonymous demo page into an AUTHENTICATED account. This requires the signed-in user's OAuth — an anonymous chat/agent session cannot call it and will get an OAuth-required error. So in a normal agent conversation, do NOT call this to 'save' a demo page: instead share the claimUrl from the page_create/page_publish result with the user, who opens it, signs in, and keeps the page. Only call page_claim when the request already runs under the owner's OAuth.

NameTypeReqDescription
editTokenstringyesThe editToken returned by page_create for the anonymous demo page.
pageIdstringyesThe pageId returned by page_create.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_create ~268

Create a hosted link-in-bio page draft from a style preset. Provide title, displayName, and a preset (or 'auto' to infer from businessType/style). The page starts with empty placeholder blocks for you to fill in via block_update — do not invent content. This tool intentionally creates a draft only and does not return a publish action. After calling it, stop and show the preview URL. Do not call page_publish in the same turn unless the user's current message explicitly asks to publish, make the page live, or get a public share link. Anonymous demo pages expire unless claimed.

NameTypeReqDescription
biostring–Optional short bio for the header.
businessTypestring–Used by preset:auto inference. Examples: musician, restaurant, designer.
displayNamestring–Visible header display name. Defaults to title.
initialPromptstring––
layoutstring–Layout id. Defaults to 'link_in_bio'.
presetstringyesStyle preset id, or 'auto' to infer deterministically from businessType/style.
slugstring–Preferred public URL slug.
stylestring–Free-form style hint used by preset:auto inference.
titlestringyesInternal page title and default header display_name.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_create_from_brief ~1,105

Create a hosted landing page draft from a structured brief. Accepts business name, category, layout, palette, primary action, explicit final-audience publicSections, and optional hero image. Planning fields such as audience, offer, primaryGoal, location, businessType, style, and mustInclude are context only and are not rendered as public body copy. Draft previews are customer-facing: do not pass owner instructions, section-planning labels, or placeholder copy as public content. Keep sparse briefs sparse: use only facts supplied by the user or imported public sources, plus light wording polish; do not invent menus, services, hours, facilities, locations, testimonials, guarantees, staff details, prices, or operational claims. Prefer one short section or no extra section when the prompt is minimal. If a requested CTA lacks its real destination, ask for it before creation or provide fallbackLeadForm with public copy. Returns a preview URL, edit token, and next-step hints. This tool intentionally creates a draft only and does not return a publish action. After calling it, stop and show the preview URL. Do not call page_publish in the same turn unless the user's current message explicitly asks to publish, make the page live, or get a public share link. Anonymous pages expire unless claimed via page_claim. For a vague or first-page request, prefer running page_onboarding_start first (or at least pass onboardingMainCategory) so the page starts from the right template. The draft seeds the chosen preset's starter blocks (empty placeholder links, social row, save-contact) for you to fill in — they never block publishing and are pruned if left empty. Then guide the user the way a builder would: use the returned previewUrl directly (you do not need page_preview), and work through the returned nextSteps (add a real bio, a photo via media_upload, social links) before offering to publish.

NameTypeReqDescription
audiencestring–Planning context only. Not rendered directly as public page copy.
biostring–Optional short bio for the header.
businessNamestringyes–
businessTypestring–Planning context only. Not rendered directly as public page copy.
fallbackLeadFormobject–Public fallback contact/interest form to use when the requested primary action lacks a real destination. All copy must be final-audience copy in the page's target language.
heroImageUrlstring–Explicit user-provided image URL for featured-photo or full-image styles.
initialPromptstring––
layoutstring–Defaults to 'link_in_bio'.
localestring––
locationstring–Public business address or service area intended for map/address actions, not direct body copy and not the user's private/current location.
mustIncludearray–Planning checklist only. Do not put section names, CTA labels, owner instructions, or private notes here; not rendered directly.
offerstring–Planning context only. Not rendered directly as public page copy; use bio and publicSections for final-audience copy.
onboardingLayoutstring–Layout style: background_color (minimalist), full (featured photo), or background_image (full image background).
onboardingMainCategorystring–Validated atom.bio category id from page_onboarding_*, for example physical-business or online-business.
onboardingPalettestring–Palette id returned by page_onboarding_* paletteChoices, for example atom_dark_plum.
onboardingSubCategorystring–Validated atom.bio subcategory id, for example health.
preferredSlugstring–Desired URL path. Ask the user for it near the end of onboarding. Use normal letters, numbers, and hyphens; the server normalizes and makes it unique.
presetstring–Style preset id, or 'auto' to infer deterministically. Defaults to 'auto'.
primaryActionIdstring––
primaryActionLabelstring–Public label for the primary action in the page's target language.
primaryActionUrlstring–Real destination URL for the primary action when explicitly supplied by the user or imported public source, such as a booking link. Do not invent booking/order URLs; if missing, ask for it or use fal…
primaryGoalstring–Planning context only. Not rendered directly as public page copy.
publicBusinessEmailstring–Public business contact email explicitly supplied by the user or a public source. Do not use the user's ChatGPT/account email.
publicPhonestring–Public business phone number explicitly supplied by the user or a public source. Do not use the user's private/account phone.
publicSectionsarray–Final-audience text sections to render on the public page. Write in the target language with correct spelling/accents. Only include facts the user supplied or that came from an imported public source…
publicWhatsappstring–Public WhatsApp phone number explicitly supplied by the user or a public source. Do not use the user's account phone or invent placeholder numbers.
sourceHandlestring––
sourceUrlstring–Provenance reference only.
stylestring–Planning context only. Not rendered directly as public page copy.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_get ~46

Read a landing page draft, including its latest content JSON. For anonymous demo pages, include the editToken.

NameTypeReqDescription
editTokenstring––
pageIdstringyes–
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_header_update ~383

Update the link-in-bio page header: displayName, bio, verified checkmark, QR display, business-card display style ("photo_hero" large top photo or "avatar"), a short role label (e.g. "Barber · Madrid"), labelPosition, and the header photo (photoUrl; null removes it). Use only the fields you want to change. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

NameTypeReqDescription
bio––Short bio under the display name. Pass null to clear it.
display––Header style: photo_hero = large business-card top photo, avatar = small round profile photo. Pass null to clear it.
displayNamestring–Visible display name in the page header.
editTokenstring––
label––Short role line near the name, e.g. "Brand Designer · Austin, TX". Pass null to clear it.
labelPosition–––
pageIdstringyes–
photoAltstring–Alt text for the header photo.
photoObjectPositionstring–CSS focal point for the photo_hero crop, e.g. "50% 28%".
photoUrl––Header photo URL. Pass null to remove the current photo.
showQrboolean–Show a QR code for this page.
verifiedboolean–Show a verified checkmark next to the display name.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_intake_start ~285

RECOMMENDED first step for building a page. Returns the few questions worth asking (business name, primary visitor action, key content, optional source link) so you can then call page_create_from_brief. This is the simplest, most reliable path — prefer it. (page_onboarding_* offers extra category/layout/palette pickers but is a stateless planning helper, not required.) Call once per creation request; skip if the user already gave you a source URL. Does not create a page.

NameTypeReqDescription
businessNamestring–Only include if the user already provided the business or project name.
businessTypestring–Business category inferred from the user's words, such as hamburger restaurant or dental clinic.
localestring–Preferred content locale if obvious from the conversation.
originalRequeststring–The user's original page-creation request, copied verbatim when available.
primaryGoalstring–The main visitor action if known, such as book, call, WhatsApp, buy, or leave a lead.
sourceHandlestring–Public social handle provided by the user.
sourceUrlstring–Public HTTP/HTTPS source URL provided by the user, such as a business website or link-in-bio page. Protected platforms (social networks, maps, paywalls) require client-side browsing or pasted details…
NameTypeReqDescription
actionsarrayyes–
canCreateNowbooleanyes–
missingFieldsarrayyes–
modestringyes–
okbooleanyes–
promptToUserstringyes–
questionsarrayyes–
recommendedNextToolstringyes–
sourceGuidancestringyes–
titlestringyes–

No examples provided.

page_meta_update ~186

Update internal page title, URL slug, and SEO title/description. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

NameTypeReqDescription
editTokenstring––
pageIdstringyes–
seoDescriptionstring–SEO meta description value.
seoTitlestring–SEO <title> tag value.
slugstring–Preferred public URL slug.
titlestring–Internal page title shown in editor results.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_onboarding_start ~162

Optional planning helper that returns category/layout/palette/primary-action choices and a quality checklist (it does NOT create a page). Use it only if you want those pickers; otherwise page_intake_start → page_create_from_brief is the simpler path. IMPORTANT: this flow is STATELESS — page_onboarding_update does not remember earlier calls, so each update must resend the FULL set of selections + knownFields gathered so far. As soon as you have a business name and a primary action, stop and call page_create_from_brief (you do not need to reach a 'ready' step).

NameTypeReqDescription
localestring–Preferred UI locale, such as es or en.
originalRequeststring––
suggestedSelectionobject––
NameTypeReqDescription
canContinuebooleanyes–
choicesarrayyes–
createFromBriefHintsobjectyes–
imageGuidanceobjectyes–
invalidSelectionarrayyes–
layoutChoicesarrayyes–
layoutGuidanceobjectyes–
missingFieldsarrayyes–
modestringyes–
nextPromptstringyes–
okbooleanyes–
paletteChoicesarrayyes–
primaryActionsarrayyes–
profileCopyobjectyes–
qualityChecklistarrayyes–
readyToCreatebooleanyes–
recommendedBlocksarrayyes–
recommendedLinksarrayyes–
recommendedMissingFieldsarrayyes–
selectedobjectyes–
slugGuidanceobjectyes–
stepIdstringyes–
uiHtmlstringyes–

No examples provided.

page_onboarding_update ~147

Validate onboarding selections and return the remaining checklist. STATELESS: it does not remember previous calls, so every call must include the FULL accumulated selection (mainCategory, subCategory, layout, palette, primaryAction) plus all knownFields (name, description, action destination, etc.) gathered so far — not just the latest answer, or earlier choices will look 'missing'. You do not need to loop to a 'ready' state: once you have a name and a primary action, call page_create_from_brief with those values.

NameTypeReqDescription
knownFieldsobject––
localestring––
selectionobject––
stepIdstring––
NameTypeReqDescription
canContinuebooleanyes–
choicesarrayyes–
createFromBriefHintsobjectyes–
imageGuidanceobjectyes–
invalidSelectionarrayyes–
layoutChoicesarrayyes–
layoutGuidanceobjectyes–
missingFieldsarrayyes–
modestringyes–
nextPromptstringyes–
okbooleanyes–
paletteChoicesarrayyes–
primaryActionsarrayyes–
profileCopyobjectyes–
qualityChecklistarrayyes–
readyToCreatebooleanyes–
recommendedBlocksarrayyes–
recommendedLinksarrayyes–
recommendedMissingFieldsarrayyes–
selectedobjectyes–
slugGuidanceobjectyes–
stepIdstringyes–
uiHtmlstringyes–

No examples provided.

page_preview ~102

Return the current preview URL for a page. You usually do not need this: page_create and page_create_from_brief already return a ready-to-open previewUrl. For an anonymous demo page you must pass the editToken from the create result; calling this with pageId alone fails.

NameTypeReqDescription
editTokenstring–Required for anonymous demo pages. Use the editToken returned by page_create.
pageIdstringyesThe pageId returned by page_create.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_publish ~137

Publish the latest page revision. Call this only when the user's latest message explicitly asks to publish, make the page live, or get a public share link. Do not call this immediately after page_create or page_create_from_brief just because the draft is publish-ready. For anonymous demo pages, include the editToken returned by page_create. The response includes nextSteps: always share these with the user after publishing — they include the claim reminder and any remaining improvements.

NameTypeReqDescription
editTokenstring–Required for anonymous demo pages. Use the editToken returned by page_create.
pageIdstringyesThe pageId returned by page_create.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_theme_update ~182

Apply a partial theme patch. Theme fields are enum-constrained (button variant/radius/shadow, font family/weight, density, icon_size). Use presets_list first if the user wants a complete restyle. For already-published pages, this saves an unpublished latest revision only. Do not call page_publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page_publish. Do NOT call page_unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

NameTypeReqDescription
editTokenstring––
pageIdstringyes–
themeobjectyesPartial theme patch. Provide only fields you want to change.
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

page_unpublish ~41

Remove a published landing page from public availability while keeping its draft and revision history.

NameTypeReqDescription
editTokenstring––
pageIdstringyes–
NameTypeReqDescription
actionsarrayyes–
canPublishbooleanyes–
claimUrlstring|nullyes–
contentobject––
editTokenstring|nullyes–
expiresAtstring|nullyes–
isClaimedbooleanyes–
isPublishedbooleanyes–
liveUpdateMessagestring|null–Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
liveUpdateRequiredboolean–True after an edit to an already-published page when the public live page still needs page_publish to reflect the latest revision.
missingFieldsarray––
nextStepsarray–Enrichment hints to present to the user. Address 'required' items before publishing.
okbooleanyes–
pageIdstringyes–
previewUrlstringyes–
publishPolicystring|null–For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
publishedUrlstring|nullyes–
slugstringyes–
statusstringyes–
titlestringyes–

No examples provided.

presets_list ~42

List the 8 curated style presets (theme + starter blocks) for link-in-bio. Use to offer the user a choice or to confirm a preset:auto selection.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

source_import ~104

Fetch a public website URL and extract a structured brief with business name, description, contact links, and suggested page blocks. Only works with public HTTP/HTTPS pages. Does not bypass login, CAPTCHA, or paywalls. Returns extracted fields and suggestedBlocks for use with page_create_from_brief.

NameTypeReqDescription
localestring–Preferred output locale if obvious from the conversation, such as es or en.
sourceUrlstringyesPublic http/https source URL to import.
NameTypeReqDescription
briefobjectyes–
confidencenumberyes–
extractedobjectyes–
fetchModestringyes–
finalUrlstringyes–
okbooleanyes–
sourceUrlstringyes–
suggested_blocksarrayyes–
warningsarrayyes–

No examples provided.

Common questions

What is the Create Web Page MCP server?

Create Web Page is an MCP server listed in the public MCP registry as com.create-web-page/create-web-page. Create, edit, preview, publish, and manage web pages from MCP-capable AI clients. This page covers its hosted endpoint (https://create-web-page.com/mcp).

Is the Create Web Page MCP server safe to use?

Create Web Page scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Create Web Page MCP server expose?

Create Web Page exposes 27 tools: account_whoami, page_intake_start, page_onboarding_start, page_onboarding_update, source_import, and 22 more. Their descriptions and schemas cost roughly 5,081 tokens of context every time the server is loaded.

Does the Create Web Page MCP server require authentication?

No. We connected to Create Web Page without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Create Web Page MCP server still maintained?

Create Web Page is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.