Dotnet Sherlock MCP

Sherlock MCP for .NET is a comprehensive Model Context Protocol (MCP) server that provides deep introspection capabilities for .NET assemblies. It enables Language Learning Models (LLMs) to analyze and understand your .NET code with precision, delivering accurate and context-aware responses for complex development scenarios. Its 34 documented tools cluster into read & search, analyze assembly, analyze type, analyze method.

People who need these tools inside Claude, Cursor, VS Code, or another MCP client. The project is written in C#.

VERIFIED ACTIVE

LAST COMMIT 2026-08-06 · ★ 6 · #778 OF 848 MAINTAINED OTHER · VERIFIED 2026-08-25

MIT · C# · how we verify → /methodology

01 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

license MIT - declared in the repository

registry namespace io.github.jcucci is GitHub-verified and matches the repo owner

02 · What Dotnet Sherlock MCP can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can find assemblies by file name in common build paths, resolve a DLL from the local NuGet cache by package id (optional version/tfm), list all public types with metadata (paginated), and extract type-level XML documentation.

Capability map

Tools grouped from the project's README - what Dotnet Sherlock MCP lets an agent do.

read & search

27 tools - e.g. Assembly-level metadata - identity/version, target framework, and referenced assemblies (projection=full adds all assembly attributes); Locate assemblies containing specific class names; Find assemblies…

GetAssemblyInfo · FindAssemblyByClassName · FindAssemblyByFileName · FindAssemblyByNugetPackage · GetTypesFromAssembly · GetTypeInfo…

Analyze Assembly

1 tool - e.g. Complete assembly overview with public types and metadata

AnalyzeAssembly

Analyze Type

1 tool - e.g. Comprehensive type analysis with all members

AnalyzeType

Analyze Method

1 tool - e.g. Deep method analysis with overloads and attributes

AnalyzeMethod

Analyze Solution

1 tool - e.g. Parse .sln files and enumerate projects

AnalyzeSolution

Analyze Project

1 tool - e.g. Project metadata, references, and build configuration

AnalyzeProject

Resolve Package References

1 tool - e.g. Map NuGet packages to cached assemblies

ResolvePackageReferences

update

1 tool - e.g. Modify pagination, caching, and search behavior

UpdateRuntimeOptions

Latest releases

v2.13.0 · 2026-08-06

Added · Behavioural annotations on all 36 tools (readOnlyHint, destructiveHint, openWorldHint, idempotentHint) alongside a human-readable title. Every tool was previously declared with a bare [McpServerTool], so the…

v2.12.0 · 2026-06-21

Added · Transitive dependency resolution from the NuGet global packages cache. When an assembly is loaded from an isolated lib/<tfm> folder (e.g. ~/.nuget/packages/.../lib/net8.0/) whose dependencies are not sitting…

v2.11.0 · 2026-06-12

Added · The server now emits MCP usage instructions to connecting clients, giving agents built-in guidance on how to drive the introspection tools - token-efficient summary/full projections and the discovery → type →…

03 · Who maintains Dotnet Sherlock MCP

dotnet-sherlock-mcp is maintained by jcucci. It's the only MCP server we track from this author; the repo dates to Jul 2025.

04 · Facts

category
other - ranked #778 of 848 actively-maintained other servers as of 2026-08-25.
release cadence
5 releases in the last 90 days (latest 2026-08-06)
registry
io.github.jcucci/dotnet-sherlock-mcp (active, first published 2025-09-24 · 7 versions)
packages
nuget:Sherlock.MCP.Server

05 · Dotnet Sherlock MCP FAQ

Is Dotnet Sherlock MCP still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-06 and it shipped 5 releases in the last 90 days. We re-verify nightly.

What can Dotnet Sherlock MCP do?

With this server connected, an agent can find assemblies by file name in common build paths, resolve a DLL from the local NuGet cache by package id (optional version/tfm), list all public types with metadata (paginated), and extract type-level XML documentation.

06 · Alternatives to Dotnet Sherlock MCP