Brandize
REMOTE · BRANDIZE.ME · SCANNED SEP 30
AI logo generation, brand color palettes, SEO meta tags, JSON-LD schema markup, and blog search.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability check failed: schema churn in the 24 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · brandize.me
claude mcp add --transport http me-brandize-brandize 'https://brandize.me/api/mcp'
{
"mcpServers": {
"me-brandize-brandize": {
"url": "https://brandize.me/api/mcp"
}
}
} {
"servers": {
"me-brandize-brandize": {
"type": "http",
"url": "https://brandize.me/api/mcp"
}
}
} [mcp_servers.me-brandize-brandize] url = "https://brandize.me/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"me-brandize-brandize": {
"type": "remote",
"url": "https://brandize.me/api/mcp",
"enabled": true
}
}
} openclaw mcp add me-brandize-brandize --url 'https://brandize.me/api/mcp' --transport streamable-http
mcp_servers:
me-brandize-brandize:
url: "https://brandize.me/api/mcp" {
"McpServers": {
"me-brandize-brandize": {
"Transport": "http",
"Url": "https://brandize.me/api/mcp"
}
}
} assistant mcp add me-brandize-brandize -t streamable-http -u 'https://brandize.me/api/mcp'
{
"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.
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.
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.
- 22 Sept 26 +1
- Tool “buy_logo_variation” now declares an output schema ▲ functional
- Tool “generate_logo” now declares an output schema ▲ functional
- Tool “generate_logo_variations” now declares an output schema ▲ functional
- Tool “get_logo_result” now declares an output schema ▲ functional
- Tool “echo” now declares an output schema ▲ functional
- Tool “generate_color_palette” now declares an output schema ▲ functional
- Tool “generate_meta_tags” now declares an output schema ▲ functional
- Tool “generate_schema_markup” now declares an output schema ▲ functional
- Tool “get_pricing_tiers” now declares an output schema ▲ functional
- 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 functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 18 Sept 26 0
- 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 cosmetic
10 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.
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 30 Sept 2026 · Probed https://brandize.me/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=brandize.me | CN=YR1,O=Let's Encrypt,C=US | 6 Aug 2026 | 4 Nov 2026 | RSA 2048 | SHA256-RSA | 51e95eb28fbe8ca9f5fbb00cd75fa7fbfea |
| SANs: brandize.me | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of brandize.me. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| me. | present | 45352 | 8 | Verified |
| brandize.me. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://brandize.me/api/mcp | Verified | 200 | |
| http (plaintext) | http://brandize.me/api/mcp | HTTPS enforced | 308 | https://brandize.me/api/mcp |
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 →
buy_logo_variation Buy logo variation ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobToken | string | yes | The jobToken returned by generate_logo. |
| variationId | string | yes | The variationId of the design to purchase, from generate_logo_variations. |
| Name | Type | Req | Description |
|---|---|---|---|
| checkoutUrl | string|null | yes | Short checkout link to pay; null only if Stripe returned no URL. |
| currency | string | yes | ISO currency code. |
| jobToken | string | yes | The job this purchase belongs to. |
| note | string | yes | Guidance for completing payment and retrieving the deliverable. |
| priceUsd | number | yes | PREMIUM price in US dollars. |
| variationId | string | yes | The variation being purchased. |
No examples provided.
echo Echo (health check) ~38
Health check that returns the provided message verbatim, confirming the Brandize MCP endpoint is reachable.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Text to echo back unchanged. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The same text that was sent, echoed back unchanged. |
No examples provided.
generate_color_palette Generate color palette ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| baseColor | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | Format of `output`. |
| output | string | yes | The palette rendered as CSS custom properties, a Tailwind snippet, or a hex list. |
No examples provided.
generate_logo Generate logo ~558
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.
| Name | Type | Req | Description |
|---|---|---|---|
| antiReference | string | – | Anything the logo should avoid looking like. |
| brandName | string | yes | The brand or product name. |
| colorPrimary | string | yes | 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 | yes | Industry category — ask the user; use "other" only if it genuinely fits none. |
| layoutIntent | string | yes | Logo layout (icon-only, wordmark, horizontal-lockup, stacked). Ask the user. |
| primaryUseSurface | string | yes | Primary surface the logo must read well on. Ask the user. |
| style | string | yes | Visual style. Ask the user which style they want. |
| tier | string | yes | 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 | yes | One short phrase describing what the brand does. |
| Name | Type | Req | Description |
|---|---|---|---|
| checkoutUrl | string | yes | Short checkout link to pay for the deliverable. |
| currency | string | yes | ISO currency code. |
| includes | array | yes | What the chosen tier delivers. |
| jobToken | string | yes | Anonymous job token; poll get_logo_result with it. Keep private. |
| note | string | yes | Guidance for presenting the preview and checkout to the user. |
| previewUrl | string | yes | URL to the watermarked, low-res preview image. |
| priceUsd | number | yes | Price of the chosen tier in US dollars. |
| tier | string | yes | The purchased delivery tier. |
| upgradeNote | string | – | Guidance for offering upgrades, when any exist. |
| upgrades | array | yes | Higher tiers to optionally offer before checkout. |
No examples provided.
generate_logo_variations Generate logo variations ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many alternate-style variations to generate (1-3), capped by the free-preview credits remaining on this job. |
| jobToken | string | yes | The jobToken returned by generate_logo. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobToken | string | yes | The job these variations belong to. |
| note | string | yes | Guidance for presenting the variations and next steps. |
| remainingCredits | number | yes | Free-preview credits left on this job. |
| variations | array | yes | The generated alternate-style previews. |
No examples provided.
generate_meta_tags Generate meta tags ~208
Generate an HTML <head> meta-tag block (title, description, canonical, robots, Open Graph, Twitter Card) from page details. All fields optional.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The generated <head> meta-tag block as HTML. |
No examples provided.
generate_schema_markup Generate schema markup ~109
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 }].
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Fields for the chosen type, e.g. { name, url, description, telephone }. FAQPage uses { items: [{ question, answer }] }. |
| type | string | yes | schema.org type to generate. |
| Name | Type | Req | Description |
|---|---|---|---|
| jsonLd | string | yes | The JSON-LD <script type="application/ld+json"> block, ready to paste. |
No examples provided.
get_logo_result Get logo result ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobToken | string | yes | The jobToken returned by generate_logo. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Job state. Only `paid` carries a downloadable asset. |
| tier | string | – | Purchased delivery tier; present once paid or processing. |
No examples provided.
get_pricing_tiers Get pricing tiers ~33
List Brandize service tiers with their price (USD) and included features. Read-only; nothing is purchased.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| tiers | array | yes | Public service tiers. |
No examples provided.
search_blog Search blog ~50
Search Brandize blog posts (logo design and branding guides) by keyword. Returns matching post titles, excerpts, and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Keyword(s) to match against post titles and content. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Matching blog posts; empty when nothing matches. |
No examples provided.
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.