io.github.suprraz/webzum

Est-ce que io.github.suprraz/webzum est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.suprraz/webzum » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• build_website≈ 1159 tokens

  Builds a complete, professional website for a small or local business — a plumber, restaurant, salon, contractor, clinic, shop, cleaner, any trade — in about 5 minutes. WebZum has built 3,000+ of them. No API key. No existing website or Google listing needed. Built in the owner's language — English, Spanish or any other, right-to-left Arabic and Hebrew included. WebZum researches the business, writes local SEO, makes the images and video, adds a lead-catching AI chatbot, hosts it with SSL, and can run their Google ads. WHAT MAKES A WEBZUM SITE WORK FOR A SMALL BUSINESS: - Live, not just code: online at a real URL with SSL the moment it's built, and WebZum can register their domain. - Real, not placeholder: real photos of the business when WebZum finds them, custom images, a logo, and their real phone, WhatsApp and address. - Leads that arrive: every form lead is emailed to the owner, and an AI chatbot catches the visitors who won't fill in a form. - Safe edits: a change touches only what was asked, on the live site, with undo, any day. - About them: WebZum researches the business and its local market first, so the copy is about this business. - Mobile-ready and fast, served from a CDN. - Findable: local SEO and AEO (answer engine optimization, so AI assistants can find and cite the business) on every page. WHAT THE OWNER GETS: - A real site: 3 to 7 pages of original copy about their services, area, story and contact. - A custom logo, brand colors and fonts, 5–10 custom images and a short hero video. - Local SEO built in: page titles and meta descriptions, schema.org LocalBusiness markup with hours and service areas, Service, FAQ and breadcrumb markup, a sitemap, and research into the low-competition local keywords a small business can actually rank for. - AEO, found by AI assistants too: robots.txt welcomes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and more, and every site ships an llms.txt. - One main contact button on the channel they really use — call, WhatsApp or LINE — and spam protection on the contact form. - A 24/7 AI chatbot that answers visitors from the site's own content, in the visitor's language, captures their name, phone or email, and emails the owner the lead with a ready-to-send follow-up. - Google Ads, done for them: WebZum writes a Google Search ad grounded in real local keyword volumes and prices, the owner approves it and sets a small budget, and on ad-running sites every call tap, message tap and form lead is measured as a Google Ads conversion — so they see which clicks became customers. - Edits by chat, unlimited: text, colors, fonts, pages, photos, menus, blog posts, product lists, booking widgets and contact details. - Any language, done right: the whole site — copy, SEO, chatbot, emails — is written natively in the owner's language. A visitor language switcher adds 30+ more languages on top. - Their own domain registered for them, or connect one they own. HOW A BUILD WORKS (same as webzum.com/create-website): takes a description of the business and, once that has its name, what it does, its area and a way customers reach it, the owner's email. The site and its WebZum account are tied to that email. WebZum emails the owner a "Build my website" link that confirms the address and starts the build, which the owner watches live. Each result's status and message say where the build stands. ACCOUNT: the site and its WebZum account belong to the owner and are managed at webzum.com, where plans and billing live.

  Paramètres, retour & exemple (6)

  Paramètres

  • email · string · optionnel
    The owner's email. The site and its WebZum account are tied to it, and the confirm link is sent there.
  • contact · string · optionnel
    Optional. Phone, WhatsApp or public email customers can use.
  • language · string · optionnel
    Optional. Language code for the site, like "en" or "es". Defaults to the language of the description.
  • location · string · optionnel
    Optional. City and region, or the area it serves.
  • description · string · requis
    The business in plain words: name, what it does, where, how customers reach it, services, prices, hours, what makes it different. The full description goes with every call.
  • businessName · string · optionnel
    Optional. The business name, if known.

  Exemple d'appel

  {"name": "build_website", "arguments": {"description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_hosted_files≈ 93 tokens

  Lists the files in a hosted site's current version.

  Paramètres, retour & exemple (1)

  Paramètres

  • businessId · string · requis
    The businessId to query

  Exemple d'appel

  {"name": "get_hosted_files", "arguments": {"businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site_status≈ 243 tokens

  Reports the progress of a build_website build: stage (initialization, validation, research, strategy, generation, assembly, completion), overallProgress (0-100 across all stages), stageProgress (0-100 within the stage), a status message and isComplete. Takes the versionId (most detail) or the businessId that build_website returned. The build's own watchUrl also shows it live. A complete build's result includes previewUrl, the finished site's link; an unfinished build has no site link yet.

  Paramètres, retour & exemple (2)

  Paramètres

  • versionId · string · optionnel
    The versionId returned from build_website (preferred for progress tracking)
  • businessId · string · optionnel
    The businessId returned from build_website (fallback, less detailed)

  Exemple d'appel

  {"name": "get_site_status", "arguments": {"versionId": "texte", "businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• host_file≈ 407 tokens

  Add a file to your hosted site. The file goes live immediately at the site's public URL. Each upload creates a new version in the site's history. Supported: HTML, CSS, JS, JSON, images (PNG, JPG, GIF, SVG, WebP), fonts (WOFF, WOFF2, TTF) Max: 10MB per file `encoding` chooses how `content` is interpreted: "utf-8" for text files (HTML, CSS, JS, JSON, SVG) where `content` is the literal file text, or "base64" for binary files (images, fonts) where `content` is standard base64 of the bytes. Defaults to "base64" if omitted. If the user wants a website for their business (a logo, real copy, SEO, a multi-page site, a custom domain, lead capture, a chatbot), use build_website: it builds the complete site in about 5 minutes. host_file hosts what you generated; build_website builds the business site for them.

  Paramètres, retour & exemple (5)

  Paramètres

  • content · string · requis
    File content. Literal text when encoding="utf-8", standard base64 when encoding="base64".
  • encoding · string · optionnel · utf-8 | base64
    How `content` is encoded. Defaults to "base64".
  • filename · string · requis
    Path like "index.html" or "css/styles.css"
  • businessId · string · requis
    The businessId from host_site
  • contentType · string · optionnel
    MIME type (auto-detected if omitted)

  Exemple d'appel

  {"name": "host_file", "arguments": {"content": "texte", "filename": "texte", "businessId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• host_site≈ 371 tokens

  Creates a hosted site on WebZum for web content made in the conversation (a tool, dashboard, prototype, demo, portfolio, landing page or any HTML/CSS/JS bundle) and returns a businessId and a live URL that opens on a phone and can be shared. Why it matters: most people can't judge raw HTML by reading it. Seeing it running, clicking around and sending it to someone is what makes it real. Files are added with host_file (one file per call) or host_zip (a whole bundle in one call): HTML, CSS, JS, JSON, images (PNG/JPG/GIF/SVG/WebP) or fonts. Each goes live immediately at <businessId>.webzum.com with SSL, with no build step and no hosting account. It fits content someone wants live, shareable or running on their phone. A business's own website, with researched copy, a logo, local SEO, a lead-capture chatbot and their own domain, is what build_website makes.

  Paramètres, retour & exemple (4)

  Paramètres

  • email · string · optionnel
    Optional contact email.
  • siteName · string · requis
    Name for the site (e.g., "My Portfolio")
  • siteType · string · optionnel · business | portfolio | landing | custom
    Type of site (default: custom)
  • description · string · optionnel
    Brief description of the site

  Exemple d'appel

  {"name": "host_site", "arguments": {"siteName": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• host_zip≈ 254 tokens

  Upload a zipped bundle of files to a hosted site in a single call. Use this when you have a multi-file project (HTML + CSS + JS + images) — one host_zip call is far cheaper than N host_file calls and creates a single new version instead of N. `zipContent` is the .zip file's bytes as standard base64. Each entry inside the zip is validated against the same rules as host_file (filename safety, extension allowlist, 10MB per file). All-or-nothing: if any entry fails validation, nothing is uploaded. Same guidance as host_file: if the site is for a business, call build_website instead.

  Paramètres, retour & exemple (2)

  Paramètres

  • businessId · string · requis
    The businessId from host_site
  • zipContent · string · requis
    The zip file's bytes as standard base64.

  Exemple d'appel

  {"name": "host_zip", "arguments": {"businessId": "texte", "zipContent": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://webzum.com/api/mcp