Dashboard Icons review Service matching, variants and formats
Twelve local catalog checks test Dashboard Icons service names, aliases, theme variants, real asset paths and fuzzy limits using a pinned 3515-icon snapshot.
AgentIndex · Published 2026-11-05 · Updated 2026-11-05
Dashboard Icons provides service logos for dashboards and app directories, with an HTTP MCP server for agents. Its practical benefit is helping an agent find an existing icon and return the formats actually available, instead of inventing a filename from a product name. The interesting adoption question is how far a match can be trusted before it becomes a broken image or the wrong brand.
Our local catalog checks matched Plex, Home Assistant, Pi-hole and qBittorrent in caller order, resolved an alias and selected a declared light variant. They also exposed two boundaries: fuzzy matching has a per-call budget, and a ranking score is not a probability. Asset availability was checked against the pinned repository inventory and tracked paths, rather than against a live CDN.
Source and twelve catalog checks
The review pins commit 16c42dc580c144246651d322a079e535cb2b69f8 from November 4, 2026, and was performed November 5. The website package reports 0.2.0. Its metadata snapshot contains 3,515 native icon entries. This is an entry count, not a count of unique brands across every external source or of every format file. Project description
Twelve checks ran on macOS arm64 with Node.js 26.12.1. They execute the actual catalog, search, variant, file-inventory and URL modules. The native metadata loader is replaced with the committed JSON snapshot; external catalogs return empty stand-ins. The Next server-only guard and framework-error helper are substituted so these modules can run independently. There is no deployed MCP transport, OAuth, submission, browser-rendering or CDN-availability test. Fixture and source fingerprints
| Input or condition | Observed result |
|---|---|
| Plex, Home Assistant, Pi-hole, qBittorrent | Correct native entries, original request order retained |
Alias 8311 community | Resolved to 8311 |
Search github white | GitHub ranked first with declared light variant |
| GitHub detail URLs | Formats matched inventory and actual tracked asset paths |
Raster-only radarr-3d | PNG present; SVG absent |
| Made-up, untracked stem | No inferred format availability |
| Eleven names needing fuzzy lookup, then Plex | Eleventh marked fuzzy_limit; Plex still matched |
| Query longer than 100 characters | Refused |
| Two five-item browse pages | No repeated entries across those pages |
| Empty external catalog stand-ins | Sources reported degraded; native Plex remained available |
These checks demonstrate selected catalog behavior on one snapshot. They do not establish that every logo is visually correct or current.
Resolve names before constructing URLs
Normalizing punctuation and spaces helps convert a service label into a catalog identity. In our batch, Home Assistant mapped to home-assistant, and qBittorrent mapped to qbittorrent. An explicit alias resolved to its owner. The caller's service string remained attached to the result, which helps a consuming agent update the correct configuration entry. Catalog implementation
For dashboard generation, keep that mapping until rendering is verified. A human-readable name, catalog slug and filename are related but distinct. Picking the right slug first is more dependable than lowercasing an arbitrary display name and appending .svg.
The four familiar services are examples, not a broad relevance benchmark. An obscure product or a short ambiguous label may need a human choice among candidates. We did not run a labeled sample covering every service in the collection.
Scores rank candidates; they do not express certainty
The tested catalog returned scores including 3.6 for Plex and 3.39 for Home Assistant. Values above one make clear why they should not be displayed as a percentage confidence. The source combines name, alias and other search signals into a ranking score. Search implementation
Use the result as a candidate with an identity and preview. When several products share a short term, preserve alternatives and allow a reviewer to confirm the intended brand. A high rank is not independent validation that a logo belongs in a particular application.
The batch matcher limits new fuzzy lookups to ten distinct normalized names. Our eleventh unknown-style service was returned with no best match and fuzzy_limit; a later exact Plex name still succeeded. A consumer should distinguish that outcome from a genuinely absent icon, then narrow or split the remaining search. Retrying the identical large batch without changing the unresolved part repeats the same boundary.
Theme labels refer to actual variants
Searching github white selected the light variant. In this snapshot, GitHub's light SVG uses github-light.svg, while its default and dark keys both point to the base github.svg. A theme key therefore need not imply a separate suffixed file.
The native detail function returns per-format URLs based on declared variants and a checked-in stem inventory. We checked those URLs against both the inventory and Git tree paths. A fabricated stem received no available formats. A raster-only native entry had a PNG URL but no invented SVG. Native format inventory handling
Prefer these detail URLs to guessing that every icon has three formats and two theme suffixes. A usable integration also needs a fallback when its preferred format is absent. Our path checks do not measure a live CDN response, cache freshness, rendering contrast or image dimensions. If repeatable builds matter, decide separately how assets will be pinned or copied into the consuming project's own asset workflow.
Source degradation should remain visible
With empty external-source stand-ins, the actual catalog reported selfh.st, LobeHub and Simple Icons as degraded while still returning native Plex. When we injected a failure into the native metadata loader, a native-only search returned no hits and marked the native source degraded. That distinction helps avoid treating an unavailable catalog as evidence that a product has no icon.
External-source identity also matters to format and license metadata. Native GitHub details returned a null per-icon license in this test. The repository's Apache-2.0 license does not fill that field automatically. The README separately discusses brand ownership and external-source credits; consumers should retain available source information rather than synthesizing a per-icon license. Repository and external-source notes
Adoption decision
Dashboard Icons fits dashboards, service directories and agents that need recognizable logos from an existing collection. The documented endpoint supports public lookup; account and submission operations are a separate workflow. We did not authenticate, submit an icon or modify a client configuration. MCP interface documentation
For a trial, match a small real service list, request details, inspect the chosen variant on the intended background and handle absent formats and degraded sources explicitly. For broader interface decisions, see the Taste Skill browser-check review. For diagnosing MCP transport independently of catalog semantics, see the MCP TypeScript SDK review.