CogniRepo vs Openttt MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
CogniRepo vs Openttt MCP
In-depth architectural comparison of the CogniRepo and Openttt MCP 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
CogniRepo
Finance & Fintech · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Openttt MCP
Finance & Fintech · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose CogniRepo if you need specialized Finance & Fintech tools running via a local process. Choose Openttt MCP if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose CogniRepo when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: AST-based symbol lookup, FAISS and BM25 retrieval, Persistent session and episodic memory.
CogniRepo is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Openttt MCP belongs to Finance & Fintech using local stdio subprocess. Select CogniRepo when you need capabilities focused on finance & fintech and Openttt MCP when you require tools for finance & fintech.
ancestors in chronological order (depth-compressed for large chains)
forwardChain
steps that follow the given eventId
chainBroken
`true` if a gap is detected (ancestor was evicted from ring buffer, or the chain root references an unknown entry)
brokenAt
`"server_restart"` if the gap was caused by a server restart clearing in-memory state; otherwise the eventId at which the break occurred; `null` if chain is intact
reachableDepth
number of ancestors successfully traversed before the gap (or chain root)
checkpointId
unique checkpoint identifier
rollup
compressed event history (depth-adaptive: full/compact/minimal/rollup)