#1 AIUnknown
memorylens-mcp — alternative #1 to mcp-dotnet-diagnostics
#️⃣ 🏠 🪟 - On-demand .NET memory profiling MCP server. Wraps JetBrains dotMemory with a heuristic rule engine (10 rules) to detect memory lea...
GitHub source
Recorded alternatives
Alternatives to mcp-dotnet-diagnostics
Every candidate below sits in AI. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.
#2 AIUnknown
agentkits-memory — alternative #2 to mcp-dotnet-diagnostics
📇 🏠 🍎 🪟 🐧 - Persistent memory for AI coding assistants with hybrid search (FTS5 + vector embeddings), session tracking, automatic context ho...
GitHub source3MIT
#3 AIUnknown
engram — alternative #3 to mcp-dotnet-diagnostics
📇 🏠 🍎 🪟 🐧 - Local-first persistent memory for AI agents. SQLite + local embeddings (all-MiniLM-L6-v2), hybrid semantic + FTS5 recall, secret...
GitHub source
#4 AIUnknown
memory-arbiter-mcp — alternative #4 to mcp-dotnet-diagnostics
🐍 🏠 🍎 🪟 🐧 - AI enhancement middleware: precise retrieval replaces full-memory loading (~80%+ token cut), rule-based conflict arbitration wit...
GitHub source10Apache-2.0
#5 AIUnknown
nucleus-mcp — alternative #5 to mcp-dotnet-diagnostics
🐍 🏠 ☁️ 🍎 🪟 🐧 - Sovereign Agent OS — persistent memory, governance, and audit trails for AI agents. One brain for Cursor, Claude Code, Windsu...
GitHub source
#6 AIUnknown
nvim-mcp — alternative #6 to mcp-dotnet-diagnostics
🐍 🏠 🐧 - MCP server providing AI assistants with full control of Neovim instances via msgpack-RPC. Read/edit buffers, run commands, send keys...
GitHub source
#7 AIUnknown
robo-cortex — alternative #7 to mcp-dotnet-diagnostics
🐍 🏠 - Git-aware, evidence-based memory store for AI coding agents. Memories anchored to git blob hashes are automatically flagged for review...
GitHub source
#8 AIUnknown
sessionmem — alternative #8 to mcp-dotnet-diagnostics
📇 🏠 - Local-first memory layer for AI coding assistants. Watches your coding sessions and injects a compact summary at the start of each new...
GitHub source9MIT
Questions about this page
How were these alternatives selected?
Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.
Are these alternatives ranked by payment?
No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.
Always verify current terms with mcp-dotnet-diagnostics directly — Oryxen records pricing classes, not live quotes.