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.

WebZum - Websites for Small & Local Businesses

REMOTE · WEBZUM.COM

Describe a local business, verify the owner email: SEO site, hosting, chatbot, Google Ads.

Available components

0 this week 80 Trust /100

Last scanned (16 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1929 tokens (~321/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 0
    • Tool “build_website” rewrote its description, which is the text the model reads security
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 +2
    • Stability: fail → pass ▲ security
  • 3 Nov 26 +8
    • Tool “build_website” rewrote its description, which is the text the model reads security
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 21 Nov 2026 · Probed https://webzum.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=webzum.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 6 Aug 2026 19 Feb 2027 RSA 2048 SHA256-RSA 6e72c5d298cd19fb2ed786727cdd2a1
SANs: webzum.com, *.webzum.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of webzum.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
webzum.com. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://webzum.com/api/mcp Verified 200
http (plaintext) http://webzum.com/api/mcp HTTPS enforced 301 https://webzum.com/api/mcp
MCP tools · 6 exposed · ~1,929 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
build_website ~971

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,200+ 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 ch…

NameTypeReqDescription
businessNamestring–Optional. The business name, if known.
contactstring–Optional. Phone, WhatsApp or public email customers can use.
descriptionstringyesThe 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.
emailstring–The owner's email. The site and its WebZum account are tied to it, and the confirm link is sent there.
languagestring–Optional. Language code for the site, like "en" or "es". Defaults to the language of the description.
locationstring–Optional. City and region, or the area it serves.

No output schema declared.

No examples provided.

get_hosted_files ~33

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

NameTypeReqDescription
businessIdstringyesThe businessId to query

No output schema declared.

No examples provided.

get_site_status ~157

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.

NameTypeReqDescription
businessIdstring–The businessId returned from build_website (fallback, less detailed)
versionIdstring–The versionId returned from build_website (preferred for progress tracking)

No output schema declared.

No examples provided.

host_file ~320

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.

NameTypeReqDescription
businessIdstringyesThe businessId from host_site
contentstringyesFile content. Literal text when encoding="utf-8", standard base64 when encoding="base64".
contentTypestring–MIME type (auto-detected if omitted)
encodingstring–How `content` is encoded. Defaults to "base64".
filenamestringyesPath like "index.html" or "css/styles.css"

No output schema declared.

No examples provided.

host_site ~269

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.

NameTypeReqDescription
descriptionstring–Brief description of the site
emailstring–Optional contact email.
siteNamestringyesName for the site (e.g., "My Portfolio")
siteTypestring–Type of site (default: custom)

No output schema declared.

No examples provided.

host_zip ~179

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.

NameTypeReqDescription
businessIdstringyesThe businessId from host_site
zipContentstringyesThe zip file's bytes as standard base64.

No output schema declared.

No examples provided.

Install

How do I install the WebZum - Websites for Small & Local Businesses MCP server?

WebZum - Websites for Small & Local Businesses is a hosted endpoint at https://webzum.com/api/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 · webzum.com

# add to Claude Code
claude mcp add --transport http suprraz-webzum 'https://webzum.com/api/mcp'
Common questions

What is the WebZum - Websites for Small & Local Businesses MCP server?

WebZum - Websites for Small & Local Businesses is an MCP server listed in the public MCP registry as io.github.suprraz/webzum. Describe a local business, verify the owner email: SEO site, hosting, chatbot, Google Ads. This page covers its hosted endpoint (https://webzum.com/api/mcp).

Is the WebZum - Websites for Small & Local Businesses MCP server safe to use?

WebZum - Websites for Small & Local Businesses scores 80 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 WebZum - Websites for Small & Local Businesses MCP server expose?

WebZum - Websites for Small & Local Businesses exposes 6 tools: build_website, get_site_status, host_site, host_file, get_hosted_files, host_zip. Their descriptions and schemas cost roughly 1,929 tokens of context every time the server is loaded.

Does the WebZum - Websites for Small & Local Businesses MCP server require authentication?

No. We connected to WebZum - Websites for Small & Local Businesses without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WebZum - Websites for Small & Local Businesses MCP server still maintained?

WebZum - Websites for Small & Local Businesses is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the WebZum - Websites for Small & Local Businesses MCP server?

VerifyMCP ran 13 checks on WebZum - Websites for Small & Local Businesses, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.