MCP.Market

NuGet API Inspector MCP server

by DimonSmart·io.github.DimonSmart/NugetMcpServer·v1.1.10·24 stars

Inspect NuGet package APIs, dependencies, metadata, and breaking changes across versions.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

24 stars

Reviews

Write one

Nobody has reviewed NuGet API Inspector yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

NuGet API Inspector tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How NuGet API Inspector compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
GitHub stars
24
more than 91% of 28,688 servers

Install NuGet API Inspector in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the NuGet API Inspector repository's README, as published. We do not edit it. Read it on GitHub

NugetMcpServer

<!-- mcp-name: io.github.DimonSmart/NugetMcpServer -->

Bad NuGet API guesses are expensive.

NugetMcpServer lets Codex, Claude Code, VS Code, Claude Desktop, and other MCP clients inspect real NuGet package metadata and public APIs before generating code. It is most useful when package version details matter or when the package lives in a private feed.

Fastest path: install it with codex mcp add or claude mcp add, then ask your assistant to use the NuGet MCP server before writing package-dependent code.

Why this exists

LLMs often know popular libraries, but they do not reliably know the exact API surface of every package version. NugetMcpServer gives the assistant a way to check the package first instead of filling gaps from memory.

NugetMcpServer connects the assistant to NuGet packages directly, including private feeds and local package folders.

What it gives to your assistant

  • Search NuGet packages and inspect package metadata.
  • Read public API definitions for real package versions.
  • Compare versions, inspect package files, and use nuget.org, private feeds, or local package folders.

Quick start

These commands use the current published NuGet package version, 1.1.7. dnx downloads and runs the .NET tool from NuGet, so you do not need a separate dotnet tool install step.

1. Install via Codex CLI

codex mcp add nuget -- dnx DimonSmart.NugetMcpServer@1.1.7 --yes

Check available MCP commands:

codex mcp --help

Inside the Codex TUI, run:

/mcp

Codex CLI and the Codex IDE extension share MCP configuration, so configuring the server once should make it available in both clients.

2. Install via Claude Code CLI

claude mcp add --transport stdio nuget -- dnx DimonSmart.NugetMcpServer@1.1.7 --yes

Everything after -- is the actual MCP server command and arguments.

Manage and verify the server:

claude mcp list
claude mcp get nuget

Inside Claude Code, run:

/mcp

3. Install in VS Code

Open the NuGet package page, select the MCP Server tab, and copy the generated VS Code configuration.

For manual VS Code configuration, add this to mcp.json. Replace with the package version you want to pin:

{
  "servers": {
    "nuget": {
      "type": "stdio",
      "command": "dnx",
      "args": ["DimonSmart.NugetMcpServer@<version>", "--yes"]
    }
  }
}

4. Install via Docker

Use Docker when the MCP client environment does not have the .NET SDK available.

Codex:

codex mcp add nuget-docker -- docker run -i --rm ghcr.io/dimonsmart/nugetmcpserver:latest

Claude Code:

claude mcp add --transport stdio nuget-docker -- docker run -i --rm ghcr.io/dimonsmart/nugetmcpserver:latest

Run the container directly:

docker run -i --rm ghcr.io/dimonsmart/nugetmcpserver:latest

VS Code mcp.json:

{
  "servers": {
    "nuget": {
      "type": "stdio",
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/dimonsmart/nugetmcpserver:latest"]
    }
  }
}

Install in VS Code with Docker

5. Manual configuration

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

NuGet API Inspector: common questions

Is NuGet API Inspector MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the NuGet API Inspector safety report
Does NuGet API Inspector need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is NuGet API Inspector maintained?
The last commit was 24 days ago (2026-10-11). The latest release is v1.1.10.
What can I use instead of NuGet API Inspector?
Servers from other publishers that do the same job: PartCAD MCP server.
How does NuGet API Inspector compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); github stars 24 (more than 91% of 28,688 servers). Full comparison.

Alternatives to NuGet API Inspector

Same job from other publishers: the closest match first, then the best rated.

  • PartCAD
    Inspect, render, test and export the parts and assemblies of PartCAD hardware packages
    A