In-depth architectural comparison of the Basic Memory and MCP Contradiction Check MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Basic Memory
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
MCP Contradiction Check
Knowledge & Memory · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Basic Memory if you need specialized Knowledge & Memory tools running via a local process. Choose MCP Contradiction Check if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Basic Memory when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Persistent, local-first AI memory: a semantic knowledge graph of plain Markdown files that humans and LLMs both read and write. Works with any MCP client, with optional cloud sync and team workspaces.
Find where your notes disagree — contradiction detection for markdown vaults.
Basic Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, MCP Contradiction Check belongs to Knowledge & Memory using local stdio subprocess. Select Basic Memory when you need capabilities focused on knowledge & memory and MCP Contradiction Check when you require tools for knowledge & memory.
Scan the vault for note pairs with high concept overlap but conflicting numerical or qualitative claims. Returns all detected conflicts with the specific issues flagged.
check_pair
Run the full contradiction check between two specific notes (by path or filename stem). Returns the detailed conflict analysis — shared concepts, quantitative conflicts, negation conflicts.
extract_claims
Pull all quantitative claims (numbers with units) and negation patterns from a single note. Useful as input to your own verification pipeline.
generate_reconciliation_prompt
For a detected contradiction, produce a structured prompt you can feed to an LLM to reason through the conflict and suggest a resolution. Preserves the exact claims + shared concepts + both notes' context windows.