← All servers

Brandize

connects

brandize.me

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

https://brandize.me/api/mcpWebsiteNo authMCP 2025-11-25v1.2.0+04b62beclast checked 22 Oct 2026spoke MCP on 100% of 88 checks (30 days)initialize in 299 ms

Last checked 22 Oct 2026

✓Answered the MCP handshake (MCP 2025-11-25)
✓Auth detected: No auth
✓Lists 10 tools
✓No blockers or warnings
✓Spoke MCP on 88 of 88 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://brandize.me/api/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://brandize.me/api/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

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

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 22 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 10 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

buy_logo_variationechogenerate_color_palettegenerate_logogenerate_logo_variationsgenerate_meta_tagsgenerate_schema_markupget_logo_resultget_pricing_tierssearch_blog

Contract history

9 Oct 2026v1.2.0+04b62bec1 breaking

Breaking: get_pricing_tiers

22 Sep 2026v1.2.0+d03f93fd10 compatible

17 Sep 2026v1.0.1+eb96fc2510 cosmetic

10 Sep 2026v1.0.1+eb96fc25no contract changes

10 Sep 2026v1.0.02 breakinginstructions rewritten

Breaking: buy_logo_variation, generate_logo

Instructions rewritten: buy_logo_variation, generate_logo. The description an agent follows changed; the callable contract may not have.

7 Sep 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/brandize/badge.svg)](https://mcpi.app/servers/brandize)