Tradememory Protocol vs Findata MCP

A side-by-side look at the Tradememory Protocol and Findata MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tradememory Protocol logoTradememory ProtocolFinance & Fintech · Local subprocess (stdio)Glama 🐍 🏠 - Structured 3-layer memory system (trades → patterns → strategy) for AI trading agents. Supports MT5, Binance, and Alpaca.68GreatAuth: no auth requiredFindata MCP logoFindata MCPFinance & Fintech · Local subprocess (stdio)Real-time stocks, company fundamentals, FRED economic indicators (800k+ series), SEC filings, and crypto prices. Five tools, $0.01/call via x402 micropayments on Base mainnet. No signup required.57GoodAuth: other

Verdict: choose Tradememory Protocol for finance & fintech work as a local process; choose Findata MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tradememory Protocol logoChoose Tradememory Protocol when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like get_strategy_performance, get_trade_reflection, remember_trade.
Explore Tradememory Protocol

Findata MCP logoChoose Findata MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: EVM_PRIVATE_KEY, FINDATA_BACKEND_URL.
  • You want tools like stock_quote, company_fundamentals, economic_indicator.
Explore Findata MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTradememory Protocol logoTradememory ProtocolFindata MCP logoFindata MCP
CategoryFinance & FintechFinance & Fintech
Quality signal68/100 · Great57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredother
PricingFreeFreemium
Required env varsNone listedEVM_PRIVATE_KEYFINDATA_BACKEND_URL
Verified ownerCommunity listingCommunity listing
GitHub stars1,4301
Directory activity 5 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools205

Tools & capabilities

Tradememory Protocol tools 20

  • get_strategy_performanceGet aggregate performance stats per strategy. Use this to evaluate which strategies are working and which need adjustment.
  • get_trade_reflectionGet the full context and reflection for a specific trade. Use this to deep-dive into a particular trade's reasoning and lessons.
  • remember_tradeStore a trade into OWM multi-layer memory with automatic updates. Writes to episodic memory and automatically updates semantic (Bayesian), procedural (running averages + hold time + Kelly), and affective (EWMA confidence/streaks). Also writes to trade_records for backward compatibility.
  • recall_memoriesRecall memories using OWM outcome-weighted scoring. Queries episodic and semantic memories, scores them by outcome quality, context similarity, recency, confidence, and affective modulation. Returns ranked memories with score breakdown.
  • get_behavioral_analysisGet behavioral analysis from procedural memory. Returns aggregate trading behavior stats: hold times, disposition ratio, lot sizing variance, and Kelly criterion comparison.
  • get_agent_stateGet the current agent affective state (confidence, risk, drawdown). Returns confidence level, risk appetite, drawdown percentage, win/loss streaks, equity tracking, and a recommended action based on current drawdown severity.
  • create_trading_planCreate a prospective trading plan that activates when conditions are met. Stores a rule-based plan in prospective memory. The plan stays active until triggered, expired, or manually cancelled.
  • check_active_plansCheck active trading plans against current market context. Queries all active prospective plans, expires any past their expiry date, and matches remaining plans against the provided context.
  • evolution_fetch_market_dataFetch OHLCV market data from Binance for evolution analysis. Downloads historical price bars for backtesting and pattern discovery. Use this before discover_patterns or run_backtest to get data.
  • evolution_discover_patternsDiscover trading patterns from market data using LLM analysis. Uses Claude to analyze OHLCV data and generate candidate trading patterns with entry/exit conditions. Each pattern can be backtested afterward.
  • evolution_run_backtestBacktest a candidate pattern against historical OHLCV data. Takes a pattern dict (from discover_patterns) and runs a vectorized backtest. Returns fitness metrics: Sharpe ratio, win rate, trade count, max drawdown, total PnL.
  • evolution_evolve_strategyRun full evolution loop — generate, backtest, select, eliminate. Multi-generation strategy evolution: generates candidate patterns via LLM, backtests on in-sample data, validates survivors on out-of-sample data, eliminates weak hypotheses. Returns graduated strategies and graveyard.
  • +8 more on the listing page

Findata MCP tools 5

  • stock_quoteReal-time (15-min delayed) stock price, volume, and change % for any NYSE/NASDAQ/global ticker.
  • company_fundamentalsFull fundamental data: revenue, earnings, P/E ratio, market cap, sector, beta, dividend yield, and company description.
  • economic_indicatorUS macroeconomic data from the Federal Reserve FRED database: GDP, CPI, unemployment, interest rates, yield curves, and 800,000+ economic series.
  • sec_filingFull text of SEC filings from EDGAR: 10-K annual reports, 10-Q quarterlies, 8-K material events, proxy statements.
  • crypto_priceCryptocurrency price, market cap, 24h volume, and 7-day sparkline via CoinGecko.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Tradememory Protocol

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mnemox-ai-tradememory-protocol": {
      "command": "uvx",
      "args": [
        "tradememory-protocol"
      ]
    }
  }
}

Findata MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sapph1re-findata-mcp": {
      "command": "uvx",
      "args": [
        "findata-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY_HERE",
        "FINDATA_BACKEND_URL": "YOUR_FINDATA_BACKEND_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Tradememory Protocol is categorized under Finance & Fintech and uses a local stdio subprocess. Findata MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick Tradememory Protocol for finance & fintech work and Findata MCP for finance & fintech.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Tradememory Protocol is listed as free. Auth: no auth required. Findata MCP is listed as freemium — a free tier with paid plans. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mnemox-ai-tradememory-protocol and sapph1re-findata-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tradememory Protocol has a quality signal of 68/100 (Great) with 5 views, 0 installs and 1,430 GitHub stars. Findata MCP has 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars.