# Brandize (remote · brandize.me)

AI logo generation, brand color palettes, SEO meta tags, JSON-LD schema markup, and blog search.

- Trust score: 83/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- remote · `brandize.me`: 83/100 (this document), [markdown](https://verifymcp.io/servers/me-brandize-brandize/api-mcp.md), [page](https://verifymcp.io/servers/me-brandize-brandize/api-mcp)

## Channel facts

- Endpoint: `https://brandize.me/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-30.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1524 tokens (~152/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability check failed: schema churn in the 24 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Brandize MCP server?

Brandize is a hosted endpoint at https://brandize.me/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.

### Claude

```bash
claude mcp add --transport http me-brandize-brandize 'https://brandize.me/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "me-brandize-brandize": {
      "url": "https://brandize.me/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-brandize-brandize": {
      "type": "http",
      "url": "https://brandize.me/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-brandize-brandize]
url = "https://brandize.me/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-brandize-brandize": {
      "type": "remote",
      "url": "https://brandize.me/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-brandize-brandize --url 'https://brandize.me/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-brandize-brandize:
    url: "https://brandize.me/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "me-brandize-brandize": {
      "Transport": "http",
      "Url": "https://brandize.me/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-brandize-brandize -t streamable-http -u 'https://brandize.me/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "me-brandize-brandize": {
      "type": "http",
      "url": "https://brandize.me/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 83, +8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.

### 2026-09-22 (score 73, +1)

- [functional improvement] Tool “buy_logo_variation” now declares an output schema
- [functional improvement] Tool “generate_logo” now declares an output schema
- [functional improvement] Tool “generate_logo_variations” now declares an output schema
- [functional improvement] Tool “get_logo_result” now declares an output schema
- [functional improvement] Tool “echo” now declares an output schema
- [functional improvement] Tool “generate_color_palette” now declares an output schema
- [functional improvement] Tool “generate_meta_tags” now declares an output schema
- [functional improvement] Tool “generate_schema_markup” now declares an output schema
- [functional improvement] Tool “get_pricing_tiers” now declares an output schema
- [functional improvement] Tool “search_blog” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 60
- [functional] Server version: 1.1.0+935795b2 → 1.2.0+d03f93fd
- [functional] Server version: 1.0.1+eb96fc25 → 1.1.0+935795b2

### 2026-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.

### 2026-09-18 (score 71, 0)

- [cosmetic] Tool “buy_logo_variation” changed its title: Buy logo variation
- [cosmetic] Tool “echo” changed its title: Echo (health check)
- [cosmetic] Tool “generate_color_palette” changed its title: Generate color palette
- [cosmetic] Tool “generate_logo” changed its title: Generate logo
- [cosmetic] Tool “generate_logo_variations” changed its title: Generate logo variations
- [cosmetic] Tool “generate_meta_tags” changed its title: Generate meta tags
- [cosmetic] Tool “generate_schema_markup” changed its title: Generate schema markup
- [cosmetic] Tool “get_logo_result” changed its title: Get logo result
- [cosmetic] Tool “get_pricing_tiers” changed its title: Get pricing tiers
- [cosmetic] Tool “search_blog” changed its title: Search blog

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.

## MCP tools (10)

### `echo` (~38 tokens)

Echo (health check)

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

Input parameters:

- `message` (string, required): Text to echo back unchanged.

Output parameters:

- `message` (string): The same text that was sent, echoed back unchanged.

### `get_pricing_tiers` (~33 tokens)

Get pricing tiers

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

Output parameters:

- `tiers` (array): Public service tiers.

### `search_blog` (~50 tokens)

Search blog

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

Input parameters:

- `query` (string, required): Keyword(s) to match against post titles and content.

Output parameters:

- `results` (array): Matching blog posts; empty when nothing matches.

### `generate_color_palette` (~96 tokens)

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.

Input parameters:

- `baseColor` (string, required): Base color as a 6-digit hex, e.g. "#3B82F6".
- `format` (string): Output format for the palette.
- `harmony` (string): Color harmony rule used to derive the palette.

Output parameters:

- `format` (string): Format of `output`.
- `output` (string): The palette rendered as CSS custom properties, a Tailwind snippet, or a hex list.

### `generate_meta_tags` (~208 tokens)

Generate meta tags

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

Input parameters:

- `author` (string): Content author.
- `canonical` (string): Canonical URL (also used for og:url).
- `description` (string): Meta description (og:description fallback).
- `keywords` (string): Comma-separated keywords.
- `ogDescription` (string): Open Graph description; defaults to description.
- `ogImage` (string): Open Graph / Twitter image URL.
- `ogTitle` (string): Open Graph title; defaults to title.
- `ogType` (string): Open Graph type, e.g. "website" or "article".
- `robots` (string): Robots directive, e.g. "index, follow".
- `title` (string): Page title (<title> and og:title fallback).
- `twitterCard` (string): Twitter card type, e.g. "summary_large_image".

Output parameters:

- `html` (string): The generated <head> meta-tag block as HTML.

### `generate_schema_markup` (~109 tokens)

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 }].

Input parameters:

- `data` (object): Fields for the chosen type, e.g. { name, url, description, telephone }. FAQPage uses { items: [{ question, answer }] }.
- `type` (string, required): schema.org type to generate.

Output parameters:

- `jsonLd` (string): The JSON-LD <script type="application/ld+json"> block, ready to paste.

### `generate_logo` (~558 tokens)

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 want one), (4) layout (icon-only, wordmark, horizontal-lockup, or stacked), (5) the primary surface it must read well on, and (6) the industry. Ask for anything the user has not stated; if they have no preference on a field, propose an option and confirm it before generating. Returns a watermarked low-res preview plus a short checkout link priced at the Brandize service tiers, and an `upgrades` list of higher tiers (what each adds + its price) — offer these to the user before checkout and let them upgrade if they want, but never force it. The full-resolution, watermark-free deliverable (PNG + vector SVG + commercial license) unlocks only after payment — poll get_logo_result with the returned jobToken to retrieve it. This is a paid purchase; the hosted checkout page collects the user's acceptance of the Terms of Service and Privacy Policy, so no separate consent step is needed here.

Input parameters:

- `antiReference` (string): Anything the logo should avoid looking like.
- `brandName` (string, required): The brand or product name.
- `colorPrimary` (string, required): Dominant brand color as a 6-digit hex. Ask the user for their color scheme; if unsure, propose one and confirm.
- `colorSecondary` (string): Optional secondary/accent color as a 6-digit hex. Offer it as part of the color scheme.
- `industry` (string, required): Industry category — ask the user; use "other" only if it genuinely fits none.
- `layoutIntent` (string, required): Logo layout (icon-only, wordmark, horizontal-lockup, stacked). Ask the user.
- `primaryUseSurface` (string, required): Primary surface the logo must read well on. Ask the user.
- `style` (string, required): Visual style. Ask the user which style they want.
- `tier` (string, required): Delivery tier — ask the user which package they want to buy; do not assume one. PREMIUM: full-resolution PNG, vector SVG and a commercial license. COMPLETE: adds alternate logo variations (assembled…
- `whatItDoes` (string, required): One short phrase describing what the brand does.

Output parameters:

- `checkoutUrl` (string): Short checkout link to pay for the deliverable.
- `currency` (string): ISO currency code.
- `includes` (array): What the chosen tier delivers.
- `jobToken` (string): Anonymous job token; poll get_logo_result with it. Keep private.
- `note` (string): Guidance for presenting the preview and checkout to the user.
- `previewUrl` (string): URL to the watermarked, low-res preview image.
- `priceUsd` (number): Price of the chosen tier in US dollars.
- `tier` (string): The purchased delivery tier.
- `upgradeNote` (string): Guidance for offering upgrades, when any exist.
- `upgrades` (array): Higher tiers to optionally offer before checkout.

### `get_logo_result` (~93 tokens)

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 for up to a few minutes (payment confirmation is not instant) until the status is paid.

Input parameters:

- `jobToken` (string, required): The jobToken returned by generate_logo.

Output parameters:

- `assetUrl` (string): Download URL for the deliverable; present once paid.
- `brandName` (string): Brand name on the deliverable; present once paid.
- `emailNote` (string): Note about the emailed download link; present once paid.
- `format` (string): Deliverable format (e.g. "zip"); present once paid.
- `includes` (array): What the deliverable bundle includes; present once paid.
- `note` (string): Human-readable guidance for the current state.
- `retryAfterSeconds` (number): Seconds to wait before polling again, when not yet ready.
- `status` (string): Job state. Only `paid` carries a downloadable asset.
- `tier` (string): Purchased delivery tier; present once paid or processing.

### `generate_logo_variations` (~201 tokens)

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 watermarked, low-res preview as generate_logo, plus how many free credits remain. Before any purchase, each result's variationId can be passed to buy_logo_variation to purchase that design instead of the original. On an already-purchased COMPLETE job, this instead adds more alternates to the deliverable itself (retrieve via get_logo_result as usual) — call it again there if the user wants more once revisionCredits allows. Any other purchased tier refuses outright — its deliverable is fixed.

Input parameters:

- `count` (integer): How many alternate-style variations to generate (1-3), capped by the free-preview credits remaining on this job.
- `jobToken` (string, required): The jobToken returned by generate_logo.

Output parameters:

- `jobToken` (string): The job these variations belong to.
- `note` (string): Guidance for presenting the variations and next steps.
- `remainingCredits` (number): Free-preview credits left on this job.
- `variations` (array): The generated alternate-style previews.

### `buy_logo_variation` (~138 tokens)

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 get_logo_result with the same jobToken to retrieve it. This is a paid purchase; the hosted checkout page collects the user's acceptance of the Terms of Service and Privacy Policy, so no separate consent step is needed here.

Input parameters:

- `jobToken` (string, required): The jobToken returned by generate_logo.
- `variationId` (string, required): The variationId of the design to purchase, from generate_logo_variations.

Output parameters:

- `checkoutUrl` (string|null): Short checkout link to pay; null only if Stripe returned no URL.
- `currency` (string): ISO currency code.
- `jobToken` (string): The job this purchase belongs to.
- `note` (string): Guidance for completing payment and retrieving the deliverable.
- `priceUsd` (number): PREMIUM price in US dollars.
- `variationId` (string): The variation being purchased.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-brandize-brandize/api-mcp#diagnostics

## Score history

- 2026-09-30: 83
- 2026-09-29: 83
- 2026-09-28: 83
- 2026-09-27: 75
- 2026-09-26: 75
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66

## Common questions

### What is the Brandize MCP server?

Brandize is an MCP server listed in the public MCP registry as me.brandize/brandize. AI logo generation, brand color palettes, SEO meta tags, JSON-LD schema markup, and blog search. This page covers its hosted endpoint (https://brandize.me/api/mcp).

### Is the Brandize MCP server safe to use?

Brandize scores 83 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 Brandize MCP server expose?

Brandize exposes 10 tools: echo, get_pricing_tiers, search_blog, generate_color_palette, generate_meta_tags, and 5 more. Their descriptions and schemas cost roughly 1,524 tokens of context every time the server is loaded.

### Does the Brandize MCP server require authentication?

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

### Is the Brandize MCP server still maintained?

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

## Links

- Remote endpoint: https://brandize.me/api/mcp
- Repository: https://github.com/minim-l/brandize-mcp
- Website: https://brandize.me/mcp
- Changelog RSS feed: https://verifymcp.io/servers/me-brandize-brandize/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-brandize-brandize/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/me-brandize-brandize/api-mcp