Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ProjGraph MCP Server

NUGET · PROJGRAPH.MCP · SCANNED SEP 20

Analyze .NET solutions: Generate Mermaid graphs, ERDs, class diagrams, and project metrics.

Available components

+1 this week 85 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • 80% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 439 tokens (~87/item across 5 items; 4 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ProjGraph MCP Server server?

ProjGraph MCP Server runs locally as a NuGet package, launched with dnx ProjGraph.Mcp@1.2.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

nuget · ProjGraph.Mcp

# add to Claude Code
claude mcp add handys11-projgraph -- dnx ProjGraph.Mcp@1.2.0 --yes
// .cursor/mcp.json
{
  "mcpServers": {
    "handys11-projgraph": {
      "command": "dnx",
      "args": [
        "ProjGraph.Mcp@1.2.0",
        "--yes"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "handys11-projgraph": {
      "command": "dnx",
      "args": [
        "ProjGraph.Mcp@1.2.0",
        "--yes"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add handys11-projgraph -- dnx ProjGraph.Mcp@1.2.0 --yes
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "handys11-projgraph": {
      "type": "local",
      "command": [
        "dnx",
        "ProjGraph.Mcp@1.2.0",
        "--yes"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  handys11-projgraph:
    command: "dnx"
    args: ["ProjGraph.Mcp@1.2.0", "--yes"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "handys11-projgraph": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "ProjGraph.Mcp@1.2.0",
        "--yes"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "handys11-projgraph": {
      "command": "dnx",
      "args": [
        "ProjGraph.Mcp@1.2.0",
        "--yes"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +16
    • Malware scan: unverified → pass security
  • 15 Sept 26 −18
    • Malware scan: pass → unverified security
    • Stability: pass → 0.83 functional
    • Package version: 1.1.0 → 1.2.0 functional
  • 14 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed nuget/ProjGraph.Mcp@1.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem nuget
Reason Signature present, unreadable

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~432 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_class_diagram ~90

Generates a Mermaid class diagram for the types defined in a specific C# file or directory, with options to discover inheritance and related types in the workspace.

NameTypeReqDescription
optionsobject|nullAnalysis and discovery options.
pathstringyesAbsolute path to the .cs file or directory to analyze.
showTitlebooleanWhether to include the title in the diagram (default: true).

No output schema declared.

No examples provided.

get_erd ~158

Generates a Mermaid Entity Relationship Diagram (ERD) from an Entity Framework Core DbContext or ModelSnapshot file, including entities, properties, relationships, constraints, and inherited properties from base classes.

NameTypeReqDescription
contextNamestring|nullSpecific DbContext or ModelSnapshot class name to use if multiple are present.
ownedModestringHow EF Core owned types are shown: 'mirror' (default) inlines table-split owned types onto the owner as EF names them; 'classic' gives every owned type its own entity
pathstringyesAbsolute path to a .cs file containing a DbContext or ModelSnapshot.
showTitlebooleanWhether to include the title in the diagram (default: true).

No output schema declared.

No examples provided.

get_project_graph ~86

Analyzes a .NET solution or project file and returns the dependency graph as a Mermaid diagram.

NameTypeReqDescription
includePackagesbooleanWhether to include NuGet package dependencies in the graph (default: false).
pathstringyesAbsolute path to the project or solution file.
showTitlebooleanWhether to include the title in the diagram (default: true).

No output schema declared.

No examples provided.

get_project_stats ~98

Analyses a .NET solution or project file and returns key architectural metrics: project count, type breakdown, dependency depth statistics, most-referenced (hotspot) projects, and cycle detection.

NameTypeReqDescription
pathstringyesAbsolute path to a .NET solution (.sln/.slnx) or project (.csproj) file.
topNintegerNumber of top most-referenced projects to include. Defaults to 5.

No output schema declared.

No examples provided.

Common questions

What is the ProjGraph MCP Server server?

ProjGraph MCP Server is listed in the public MCP registry as io.github.HandyS11/projgraph. Analyze .NET solutions: Generate Mermaid graphs, ERDs, class diagrams, and project metrics. This page covers its NuGet package (ProjGraph.Mcp).

Is the ProjGraph MCP Server server safe to use?

ProjGraph MCP Server scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ProjGraph MCP Server server expose?

ProjGraph MCP Server exposes 4 tools: get_project_stats, get_erd, get_class_diagram, get_project_graph. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

Is the ProjGraph MCP Server server still maintained?

ProjGraph MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ProjGraph MCP Server server under?

ProjGraph MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.