io.github.MarcelRoozekrans/memorylens-mcp
NUGET · MEMORYLENS.MCP · 2 COMPONENTS · SCANNED SEP 20
MCP server for .NET memory profiling — in-process heap snapshots via EventPipe with leak heuristics
Available components
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 & Transparency45
- 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 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 426 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability check failed: the tool surface changed between 1.7.2 and 2.1.2: 1 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
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 5 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
How do I install the io.github.MarcelRoozekrans/memorylens-mcp server?
io.github.MarcelRoozekrans/memorylens-mcp runs locally as a NuGet package, launched with dnx MemoryLens.Mcp@2.1.2 --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 · MemoryLens.Mcp
claude mcp add marcelroozekrans-memorylens-mcp -- dnx MemoryLens.Mcp@2.1.2 --yes
{
"mcpServers": {
"marcelroozekrans-memorylens-mcp": {
"command": "dnx",
"args": [
"MemoryLens.Mcp@2.1.2",
"--yes"
]
}
}
} {
"servers": {
"marcelroozekrans-memorylens-mcp": {
"command": "dnx",
"args": [
"MemoryLens.Mcp@2.1.2",
"--yes"
]
}
}
} codex mcp add marcelroozekrans-memorylens-mcp -- dnx MemoryLens.Mcp@2.1.2 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"marcelroozekrans-memorylens-mcp": {
"type": "local",
"command": [
"dnx",
"MemoryLens.Mcp@2.1.2",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
marcelroozekrans-memorylens-mcp:
command: "dnx"
args: ["MemoryLens.Mcp@2.1.2", "--yes"] {
"McpServers": {
"marcelroozekrans-memorylens-mcp": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"MemoryLens.Mcp@2.1.2",
"--yes"
]
}
}
} {
"mcpServers": {
"marcelroozekrans-memorylens-mcp": {
"command": "dnx",
"args": [
"MemoryLens.Mcp@2.1.2",
"--yes"
]
}
}
} 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
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83.
- 18 Sept 26 +1
- Package version: 1.7.1 → 2.1.2 functional
- 17 Sept 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 83 to 73.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 10 Sept 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 83 to 63.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83.
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/MemoryLens.Mcp@2.1.2
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 →
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 →
analyze ~119
Analyzes a memory snapshot using built-in rules to detect leaks, fragmentation, excessive allocations, and anti-patterns. Returns findings with severity, description, and optional code suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| afterPath | string|null | – | Path to 'after' snapshot for comparison |
| beforePath | string|null | – | Path to 'before' snapshot for comparison |
| snapshotId | string | yes | Snapshot ID or path to analyze |
| snapshotPath | string|null | – | Path to snapshot file |
| workingDirectory | string|null | – | Working directory for resolving relative paths |
No output schema declared.
No examples provided.
compare_snapshots ~121
Takes two memory snapshots of a .NET process with a delay between them for comparison. Useful for detecting memory leaks by comparing before/after state. Provide a pid. Returns the ids and paths of both snapshots.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string|null | – | Not implemented; a process id is required |
| delaySeconds | integer|null | – | Seconds to wait between before and after snapshots (default: 10) |
| pid | integer|null | – | Process ID to snapshot |
| processName | string|null | – | Process name, used only to apply the profiling exclusion list |
No output schema declared.
No examples provided.
get_rules ~38
Lists all active analysis rules with their ID, title, severity, and category. Rules can be configured via .memorylens.json in the project root.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_processes ~54
Lists running .NET processes suitable for memory profiling, discovered from their diagnostic IPC endpoints. Excludes IDE, tooling, and MCP server processes to prevent interference.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string|null | – | Optional filter to match process name |
No output schema declared.
No examples provided.
snapshot ~94
Takes a memory snapshot of a running .NET process. Provide a pid. Returns a snapshot id to pass to analyze.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string|null | – | Not implemented; a process id is required |
| durationSeconds | integer|null | – | Seconds to wait before taking snapshot |
| pid | integer|null | – | Process ID to snapshot |
| processName | string|null | – | Process name, used only to apply the profiling exclusion list |
No output schema declared.
No examples provided.
What is the io.github.MarcelRoozekrans/memorylens-mcp server?
io.github.MarcelRoozekrans/memorylens-mcp is listed in the public MCP registry as io.github.MarcelRoozekrans/memorylens-mcp. MCP server for .NET memory profiling, in-process heap snapshots via EventPipe with leak heuristics. This page covers its NuGet package (MemoryLens.Mcp).
Is the io.github.MarcelRoozekrans/memorylens-mcp server safe to use?
io.github.MarcelRoozekrans/memorylens-mcp scores 82 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 io.github.MarcelRoozekrans/memorylens-mcp server expose?
io.github.MarcelRoozekrans/memorylens-mcp exposes 5 tools: list_processes, snapshot, get_rules, compare_snapshots, analyze. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.
Is the io.github.MarcelRoozekrans/memorylens-mcp server still maintained?
io.github.MarcelRoozekrans/memorylens-mcp 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 io.github.MarcelRoozekrans/memorylens-mcp server under?
io.github.MarcelRoozekrans/memorylens-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.