dev.dvt/dvt vs CustomerDashboard
dev.dvt/dvt is an MCP server published by dvt.dev. Marketplaces we read that list it: 1 (Official MCP Registry). CustomerDashboard is an MCP server published by customerdashboard.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  dev.dvt/dvt |  CustomerDashboard |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.37 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.0 No figure published 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 | dev.dvt/dvt | CustomerDashboard |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (mcp.dvt.dev/mcp) | Remote server (app.customerdashboard.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/getdvt/dvt-plugin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | Responded 6 days 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
dev.dvt/dvt
Dashboards as data. Author, validate, render, and share dvt dashboards from any MCP client.
CustomerDashboard
Build dashboards on your own data, including multi-customer views with per-customer login.
How to run each
dev.dvt/dvt As a remote MCP server
claude mcp add --transport http dvt https://mcp.dvt.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
CustomerDashboard As a remote MCP server
claude mcp add --transport http customerdashboard https://app.customerdashboard.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of dev.dvt/dvt nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: dev.dvt/dvt · What it can do: CustomerDashboard · 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.