Build, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints.
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
WEBCAKE_JWTAPI keyoptionalWebcake backend JWT; required only for the persistence tools (create/update/list pages).
PEXELS_API_KEYAPI keyoptionalOptional Pexels API key for search_images; without one a shared hosted proxy is used.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
new_elementNo description publishedThis tool published no description. Forge does not invent one.
new_page_skeletonNo description publishedThis tool published no description. Forge does not invent one.
validate_pageNo description publishedThis tool published no description. Forge does not invent one.
ingest_htmlNo description publishedThis tool published no description. Forge does not invent one.
ingest_urlNo description publishedThis tool published no description. Forge does not invent one.
search_imagesNo description publishedThis tool published no description. Forge does not invent one.
upload_imagesNo description publishedThis tool published no description. Forge does not invent one.
list_organizationsNo description publishedThis tool published no description. Forge does not invent one.
create_pageNo description publishedThis tool published no description. Forge does not invent one.
list_pagesNo description publishedThis tool published no description. Forge does not invent one.
find_pagesNo description publishedThis tool published no description. Forge does not invent one.
get_pageNo description publishedThis tool published no description. Forge does not invent one.
update_pageNo description publishedThis tool published no description. Forge does not invent one.
add_sectionNo description publishedThis tool published no description. Forge does not invent one.
patch_pageNo description publishedThis tool published no description. Forge does not invent one.
publish_pageNo description publishedThis tool published no description. Forge does not invent one.
get_generation_guideNo description publishedThis tool published no description. Forge does not invent one.
list_elementsNo description publishedThis tool published no description. Forge does not invent one.
get_elementNo description publishedThis tool published no description. Forge does not invent one.
get_page_schemaNo description publishedThis tool published no description. Forge does not invent one.
0 of 20 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Build, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.