Tradememory Protocol vs Octodamus Core

In-depth architectural comparison of the Tradememory Protocol and Octodamus Core 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.

Which MCP Server Should You Choose?

Choose Tradememory Protocol 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: get_strategy_performance, get_trade_reflection, remember_trade.

Explore Tradememory Protocol Details

Choose Octodamus Core when:

• You need dedicated capabilities in the Finance & Fintech domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: API Key required (Freemium).
• Primary tools included: get_agent_signal, get_market_brief, get_polymarket_edge.

Explore Octodamus Core Details

Feature & Specification Comparison

Specification	Tradememory Protocol mnemox-ai Finance & Fintech	Octodamus Core Octodamus Finance & Fintech
Summary
Category & Scope	Finance & Fintech	Finance & Fintech

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "mnemox-ai-tradememory-protocol": {
      "command": "uvx",
      "args": [
        "tradememory-protocol"
      ]
    }
  }
}

{
  "mcpServers": {
    "octodamus-octodamus-core": {
      "url": "https://api.octodamus.com"
    }
  }
}

Related MCP Server Comparisons