dev.dvt/dvt vs NVEIL
dev.dvt/dvt is an MCP server published by dvt.dev. Marketplaces we read that list it: 1 (Official MCP Registry). NVEIL is an MCP server published by nveil-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  NVEIL |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.37 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (PyPI): 88 Downloads/week (PyPI): 17 Forks (GitHub): 0 Stars (GitHub): 3 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 | NVEIL |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 3 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (mcp.dvt.dev/mcp) | On your machine (nveil) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/getdvt/dvt-plugin | github.com/nveil-ai/nveil-toolkit |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | no remote endpoint we check |
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.
NVEIL
Data processing and visualization toolkit — 50+ chart types, raw data stays local.
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
NVEIL As a local MCP server: PyPI package
claude mcp add --env "NVEIL_API_KEY=<YOUR_NVEIL_API_KEY>" --transport stdio nveil -- uvx nveil mcpRequires: NVEIL_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only dev.dvt/dvt 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 dev.dvt/dvt publish no settings it asks for, so we do not compare settings.
What it can do: dev.dvt/dvt · What it can do: NVEIL · 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.