Brandize MCP server

• Registry nameme.brandize/brandizeverified in the MCP registry

The registry name sits under brandize.me. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools10
• Server calls itselfbrandize
• Server version1.2.0+04b62bec
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 196 ms.

• Its tools do every use case we checked: generate a logo from a short business description; produce vector files for signage and business cards; create a consistent logo for app stores and social profiles.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer355 ms
• Space in an agent's context≈ 2,563 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results10 of 10 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• echo

  Health check that returns the provided message verbatim, confirming the Brandize MCP endpoint is reachable.

• get_pricing_tiers

  List Brandize service tiers with their price (USD) and included features. Read-only; nothing is purchased.

• search_blog

  Search Brandize blog posts (logo design and branding guides) by keyword. Returns matching post titles, excerpts, and URLs.

• generate_color_palette

  Generate a 5-color brand palette from a base hex color and a harmony rule. Returns CSS custom properties, a Tailwind config snippet, or a plain hex list.

• generate_meta_tags

  Generate an HTML <head> meta-tag block (title, description, canonical, robots, Open Graph, Twitter Card) from page details. All fields optional.

• generate_schema_markup

  Generate a JSON-LD <script> block for a schema.org type (LocalBusiness, Organization, WebSite, Article, FAQPage, or Product) from a flat data object. For FAQPage, pass data.items as [{ question, answer }].

• generate_logo

  Generate a brand logo. Before calling, collect a short design brief from the user — do not assume defaults: (1) which package/tier they want to buy, (2) visual style, (3) color scheme (a primary brand color, and a secondary/accent if they…

• get_logo_result

  Poll a logo job by its jobToken. Once payment has settled, returns a URL to download the full-resolution, watermark-free asset; otherwise a pending status. Read-only and safe to poll — after the user pays, keep polling every ~5 seconds…

• generate_logo_variations

  Generate alternate style directions for an existing generate_logo job. Free — no checkout — but limited to this job's free-preview credit (1 by default; a COMPLETE purchase grants 2 more, other tiers grant none). Returns the same kind of…

• buy_logo_variation

  Purchase one of the alternate designs from generate_logo_variations instead of the original logo. Priced the same as the PREMIUM tier. Mints a short checkout link; once paid, the chosen variation becomes the job's deliverable — poll…