OpenBrand vs LogoAPI.sh
OpenBrand is an MCP server published by ethanjyx. Marketplaces we read that list it: 1 (Official MCP Registry). LogoAPI.sh is an MCP server published by logoapi.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (npm): 159 Downloads/week (npm): 75 Forks (GitHub): 66 Stars (GitHub): 808 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 24 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | OpenBrand | LogoAPI.sh |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 808 (better) | 24 (worse) |
| Forks (GitHub) (differs) | 66 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | On your machine (openbrand-mcp) | Remote server (logoapi.sh/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ethanjyx/openbrand | github.com/logoapi/logo-api |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-03 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
OpenBrand
Extract brand assets (logos, colors, backdrop images, brand name) from any website URL
LogoAPI.sh
Company logos by domain as SVG or PNG URLs. Free, no API key. Search brands, get favicons.
How to run each
OpenBrand As a local MCP server: npm package
claude mcp add --env "OPENBRAND_API_KEY=<YOUR_OPENBRAND_API_KEY>" --transport stdio openbrand -- npx -y openbrand-mcp
Requires: OPENBRAND_API_KEY (secret)
LogoAPI.sh As a remote MCP server
claude mcp add --transport http logos https://logoapi.sh/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only LogoAPI.sh has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of LogoAPI.sh publish no settings it asks for, so we do not compare settings.
What it can do: OpenBrand · What it can do: LogoAPI.sh · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.