Next.js DevTools vs nft-metadata
nft-metadata is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). nft-metadata is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Next.js DevTools | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:3064e349c266 Forks (GitHub): 1 Pulls (Docker Hub): 55 086 Stars (Docker Hub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 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 | Next.js DevTools | nft-metadatano longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 7 | 3 |
| Pulls (Docker Hub) (differs) | 55 086 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/next-devtools-mcp) | On your machine (@barnburner121/plugin-hub-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/kgprs/next-devtools-mcp | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of nft-metadata
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
alchemy-nft com.mcparmory/alchemy-nft
Retrieve NFT metadata, ownership, and contract details across blockchains
-
Access to OpenZeppelin Stylus Contracts.
-
solana-nft-mcp io.github.p1xelapp/solana-nft-mcp
Read-only Solana NFT data for AI: ownership history, custody rules, marketplace sales and floors.
-
Your saved nanoodle workflow graphs as MCP tools — BYOK or pay per call in Nano (x402)
-
negbit io.github.ag3ntlab-ai/negbit
Buy negbit's curated, provenance-verified knowledge bundles with your own x402 wallet. Read-only.
-
AI skills for building fullstack Aptos dApps — Move smart contracts, TypeScript SDK, wallet integration, security auditing, and gas optimization.
What each says it does
Next.js DevTools
next-devtools-mcp is a Model Context Protocol (MCP) server that provides Next.js development tools and utilities for AI coding assistants.
nft-metadata
Generate NFT metadata schemas and validation
How to run each
Next.js DevTools As a local MCP server: Docker image
claude mcp add --transport stdio next-devtools-mcp -- docker run -i --rm mcp/next-devtools-mcpnft-metadata
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of nft-metadata publish no list of 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: Next.js DevTools · What it can do: nft-metadata · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.