# ContextManager (nuget · ContextManager)

Roslyn-powered structural context and a dependency graph of C# solutions for AI coding agents.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- nuget · `ContextManager`: 66/100 (this document), [markdown](https://verifymcp.io/servers/nushey-context-manager/contextmanager.md), [page](https://verifymcp.io/servers/nushey-context-manager/contextmanager)

## Channel facts

- Registry: `nuget`
- Package: `ContextManager`
- Version: `1.3.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Build provenance not yet verified.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1600 tokens (~228/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ContextManager MCP server?

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

### Claude

```bash
claude mcp add nushey-context-manager -- dnx ContextManager@1.3.5 --yes
```

### Cursor

```json
{
  "mcpServers": {
    "nushey-context-manager": {
      "command": "dnx",
      "args": [
        "ContextManager@1.3.5",
        "--yes"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nushey-context-manager": {
      "command": "dnx",
      "args": [
        "ContextManager@1.3.5",
        "--yes"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add nushey-context-manager -- dnx ContextManager@1.3.5 --yes
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nushey-context-manager": {
      "type": "local",
      "command": [
        "dnx",
        "ContextManager@1.3.5",
        "--yes"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  nushey-context-manager:
    command: "dnx"
    args: ["ContextManager@1.3.5", "--yes"]
```

### Netclaw

```json
{
  "McpServers": {
    "nushey-context-manager": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "ContextManager@1.3.5",
        "--yes"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "nushey-context-manager": {
      "command": "dnx",
      "args": [
        "ContextManager@1.3.5",
        "--yes"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +1)

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

### 2026-11-04 (score 65, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-03 (score 65, +16)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified

### 2026-11-02 (score 49, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 197 → 228
- [functional] Package version: 1.3.4 → 1.3.5

### 2026-11-01 (score 64, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.3.2 → 1.3.4
- [functional] Package version: 1.3.2 → 1.3.3

### 2026-10-31 (score 64)

First indexed and scored.

## MCP tools (7)

### `graph_get_dependencies` (~321 tokens)

Return the aggregated in-and-out neighbors of a graph node. Before answering, the graph is synchronized: built when the solution has no graph yet, otherwise only the invalidated contributions are re-extracted; source and MSBuild input files are compared by content hash, while changes that only alter environment-dependent MSBuild evaluation are not detected (run project_scan to force re-evaluation); a failed synchronization returns the same error as project_scan and keeps the previous graph. Type queries include the edges of the type's own members, so consumers that only call into its methods still appear; neighbor member nodes are rolled up to their declaring type. Each entry carries: id (rolled-up node ID), kind (Class/Interface/Record), direction ("out" = the queried node depends on it, "in" = it depends on the queried node), edgeKinds (per-edge-kind counts, e.g. {"CALLS": 3, "REFERENCES": 1}), and file (the neighbor's declaring source file, when known, ready for inspect_file). One entry is emitted per (id, direction). The queried node's own CONTAINS member edges are excluded — use inspect_file for a type's members. Output order is out-entries first, then in-entries, in graph-encounter order.

Input parameters:

- `nodeId` (string, required): The ISymbol.ToDisplayString() ID of the node whose neighbors to retrieve.
- `solutionPath` (string, required): Absolute path to the .sln whose graph to query, the same path passed to project_scan.

### `graph_impact_analysis` (~270 tokens)

Performs an impact-specific backward traversal from a node following CALLS, INJECTS, REFERENCES, RETURNS, and INHERITS edges. Before answering, the graph is synchronized: built when the solution has no graph yet, otherwise only the invalidated contributions are re-extracted; source and MSBuild input files are compared by content hash, while changes that only alter environment-dependent MSBuild evaluation are not detected (run project_scan to force re-evaluation); a failed synchronization returns the same error as project_scan and keeps the previous graph. Seeds the BFS with the node, its direct members (via CONTAINS), and any interfaces it implements (via IMPLEMENTS) plus their members, so member-level dependencies aggregate to their declaring type. The implementors of every interface reached are included. Member nodes reached during traversal are rolled up to their declaring type. Returns an object with 'affectedIds' (ordered list of impacted type IDs) and 'affectedFiles' (each returned affected ID mapped to its declaring source file, when known, ready for inspect_file).

Input parameters:

- `nodeId` (string, required): The ISymbol.ToDisplayString() ID of the node to analyze for impact.
- `solutionPath` (string, required): Absolute path to the .sln whose graph to query, the same path passed to project_scan.

### `graph_search` (~416 tokens)

Discover files and methods by possible names when no file path or node ID is known. A term matches an ordinal case-insensitive substring of a file name without .cs or a method name without its signature; any term is enough. Constructors match their type name. Searches every Method node in the graph, including private methods; directory paths, parameter types, bodies and namespaces are not searched. Terms are trimmed before matching; an empty term list, or any term shorter than 3 characters after trimming, rejects the entire query with invalid_query before synchronization. Selects exact matches before partial matches, each in graph encounter order, without boosting names that match several terms, up to 50 unique file/method matches before grouping by file (one per matching file and one per matching method ID). Returns compact JSON with results and truncated; each result always has file, namespaces (every namespace in the file), fileMatched and methods, and each method has name and nodeId. Arrays remain present even when empty. fileMatched is true only when the file-name match was kept within the limit; a file can appear through a kept method while its own name match was omitted. truncated means additional matches were omitted; there is no pagination, so narrow the terms. Pass a returned file to inspect_file, or a nodeId unchanged to the other graph tools. Before answering, the graph is synchronized: built when the solution has no graph yet, otherwise only the invalidated contributions are re-extracted; source and MSBuild input files are compared by content hash, while changes that only alter environment-dependent MSBuild evaluation are not detected (run project_scan to force re-evaluation); a failed synchronization returns the same error as project_scan and keeps the previous graph.

Input parameters:

- `queries` (array, required): Possible file or method names, at least one; any term can match. Each term must be at least 3 characters long after trimming whitespace.
- `solutionPath` (string, required): Absolute path to the .sln whose graph to query, the same path passed to project_scan.

### `graph_path_find` (~197 tokens)

Find the directed shortest path between two nodes in the knowledge graph. Before answering, the graph is synchronized: built when the solution has no graph yet, otherwise only the invalidated contributions are re-extracted; source and MSBuild input files are compared by content hash, while changes that only alter environment-dependent MSBuild evaluation are not detected (run project_scan to force re-evaluation); a failed synchronization returns the same error as project_scan and keeps the previous graph. Returns an ordered list of node IDs from source to target (inclusive). Returns an error if either node is not found or no directed path exists.

Input parameters:

- `solutionPath` (string, required): Absolute path to the .sln whose graph to query, the same path passed to project_scan.
- `sourceId` (string, required): The ISymbol.ToDisplayString() ID of the source node.
- `targetId` (string, required): The ISymbol.ToDisplayString() ID of the target node.

### `project_scan` (~164 tokens)

Scan a .NET solution and bring its knowledge graph up to date from loaded C# source documents. The first scan builds the graph; later scans re-evaluate the solution with MSBuild and re-extract only the documents of projects whose sources, evaluated membership, or compilation inputs changed (plus the projects that depend on them), reusing every other contribution. The result reports project/document coverage, unsupported languages, and skipped documents. Persistence and in-memory publication succeed together; failed, empty, or cancelled scans preserve the previous graph. The graph is persisted in .context-manager/<solution name>.graph.json next to the .sln, so every session working on the solution sees the latest scan.

Input parameters:

- `solutionPath` (string, required): Absolute path to a .sln file to scan.

### `inspect_context` (~153 tokens)

Analyze cross-file relationships in up to 15 C# source files using Roslyn semantic model. BCL/framework types (e.g. CancellationToken, Task) are resolved via framework metadata and EXCLUDED from 'unresolved' — that list only contains user types missing from the input set. Output is a compressed format by design: methods are one-line strings ('Name(params): ReturnType', prefixed with the access level when not public, e.g. 'protected Name(params): ReturnType'), no properties, no line numbers. There is no parity with inspect_file — use inspect_file for full per-type detail.

Input parameters:

- `filePaths` (array, required): List of absolute paths to .cs files to analyze (max 15).

### `inspect_file` (~79 tokens)

Returns a structural JSON contract for a single C# file: its absolute path, namespace, usings, and each non-private type with its kind, base type, implemented interfaces, attributes, constructor dependencies, methods (with line numbers), properties, and events.

Input parameters:

- `filePath` (string, required): Absolute or working-directory-relative path to a .cs file.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nushey-context-manager/contextmanager#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 49
- 2026-11-01: 64
- 2026-10-31: 64

## Common questions

### What is the ContextManager MCP server?

ContextManager is an MCP server listed in the public MCP registry as io.github.nushey/context-manager. Roslyn-powered structural context and a dependency graph of C# solutions for AI coding agents. This page covers its NuGet package (ContextManager).

### Is the ContextManager MCP server safe to use?

ContextManager scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 ContextManager MCP server expose?

ContextManager exposes 7 tools: graph_get_dependencies, graph_impact_analysis, graph_search, graph_path_find, project_scan, and 2 more. Their descriptions and schemas cost roughly 1,600 tokens of context every time the server is loaded.

### Is the ContextManager MCP server still maintained?

ContextManager is still listed as active in the MCP registry. We last reached this channel on 5 November 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 ContextManager MCP server under?

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

## Links

- NuGet package: https://www.nuget.org/packages/ContextManager
- Socket report: https://socket.dev/nuget/package/ContextManager
- Changelog RSS feed: https://verifymcp.io/servers/nushey-context-manager/contextmanager.xml
- Changelog JSON feed: https://verifymcp.io/servers/nushey-context-manager/contextmanager.json
- HTML version of this page: https://verifymcp.io/servers/nushey-context-manager/contextmanager