At ScriptMasterLabs, the MCP server icon stopped being a cosmetic detail the moment our fleet hit scale. We run 24 MCP servers with 182 tools — 120 free, 52 paid per call over x402, and 10 on special terms — listed across the Official MCP Registry, Glama, Smithery, the CDP Bazaar, and our own hub at scriptmasterlabs.com/muse-connect. This guide is the one we run that fleet by.
The single most important fact we have measured about this ecosystem is this: most directories never run your server. They read your package, your repo, or your registry record. Whatever icon, tool list, and metadata you baked into the published source is what the world sees — in whatever theme each directory happens to render. Get the icon wrong and it fails silently, 24 listings at a time.
Where to find the official icon
Get it from the source, not a mirror. The modelcontextprotocol GitHub organization hosts the official brand assets. Download the SVG or PNG, commit it to your repo, and reference it locally. Never scrape it from a directory listing and never hotlink it: directory sites compress, crop, and re-encode logos, and a hotlinked URL can change without notice. Across our 24 servers we vendor the mark into each package the same way — files committed locally, zero runtime fetches.
Formats and sizes
Treat SVG as the master file: it scales from a 16px favicon to a full-width banner from one source. For contexts that cannot render SVG, export fixed-size PNGs rather than scaling one bitmap: 16x16 for browser tabs and tight UI rows, 32x32 for bookmarks and small badges, 128x128 for registry cards and README inline use, and 512x512 for Open Graph and store listings. Check the 16px export against a white background, a dark editor theme, and a mid-grey registry card — if the mark turns to mush, simplify it: fewer shapes, thicker strokes, no fine text.
Light and dark themes
Use the version with adequate contrast for the background — dark-on-light for docs pages, light-on-dark for terminal screenshots and dark-mode registries. GitHub READMEs honor media queries, so host both SVGs and let the browser choose the right variant at render time. Hardcode a light-theme icon and a dark-theme registry renders a dark mark on a dark background — your server vanishes. One block removes that failure mode for every consumer of your repo.
Brand rules
Treat the icon as a fixed mark: supplied aspect ratio, no stretching, rotating, recoloring, or shadows, and clear space around it at least equal to the height of one glyph inside the mark. The icon signals the protocol, not your product — pair it with your own mark at equal height, and say "built on MCP" or "MCP-compatible," never "official" or "certified." Using the mark to indicate compatibility is fine for commercial offerings, including paid x402 servers; implying endorsement is not. A paid header done right pairs the MCP mark with our own at 24px, with price on the same line — for example, ScriptMasterLabs Trust Check at $0.01/call, settled in USDC on Base.
Bake it into the package: what 24 listings taught us
Bake static icon references and tool lists into your package, because the record is the product as far as directories are concerned. Registry records drift from live servers: our 402Proof record on the Official MCP Registry claimed 11 tools while the live server serves 12, so we republished it as v1.0.2 with the true 12-tool inventory. Quant Terminal's record listed 4 tools against 5 live, republished as v1.1.3. Both fixes were confirmed by fresh reads of the registry API afterward — a commit is not proof; a read-back is.
Some directories cannot be fixed in place at all. Smithery still shows stale tool counts for SML servers because Smithery removed in-site updating; the correction path was a support follow-up, sent November 1, 2026. When a venue cannot be edited, the package and registry record are the only surfaces you control.
Claim and verify, on a cadence. Our Verdict Protocol and OMNIGATE listings on Glama are claimed and read Healthy. OMNIGATE's own index reads back 129 SML resources, and a five-surface verification on November 3, 2026 counted 177 strict SML rows in the CDP Bazaar. Listings rot; we re-probe them like endpoints.
Own a hub you control. Every SML server — all 24, with endpoints and copyable install prompts — lives at scriptmasterlabs.com/muse-connect, with the full catalog at scriptmasterlabs.com/sml-products. Directories are rented land; the hub is ours.
We learned this the expensive way: three releases in four days were spent fixing listings that rendered wrong because the assets directories needed were not in the published source. Bake them in, and a new service renders correctly everywhere on the first try.
Read the full guide at the linked article, and browse the fleet behind it at scriptmasterlabs.com/muse-connect. ScriptMasterLabs is a service-disabled veteran-owned software lab (SDVOSB) building payment and decision infrastructure for AI agents.