Hub Equity MCP vs Tradememory Protocol

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

Hub Equity MCP logoHub Equity MCPFinance & Fintech · Local subprocess (stdio)Standardized, restatement-aware SEC + European (ESEF) XBRL fundamentals, served to your agent.59GoodAuth: api key requiredTradememory 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 required

Verdict: choose Hub Equity MCP for finance & fintech work as a local process; choose Tradememory Protocol 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?

Hub Equity MCP logoChoose Hub Equity MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HUBEQUITY_API_KEY, HUBEQUITY_API_URL.
  • You want tools like find_entity, get_fact, get_fact_decomposition.
Explore Hub Equity MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHub Equity MCP logoHub Equity MCPTradememory Protocol logoTradememory Protocol
CategoryFinance & FintechFinance & Fintech
Quality signal59/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreemiumFree
Required env varsHUBEQUITY_API_KEYHUBEQUITY_API_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars01,431
Directory activity 3 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools2120

Tools & capabilities

Hub Equity MCP tools 21

  • find_entitySearch Hub-Equity entities by name, ticker (e.g. 'CSCO'), or CIK. Returns up to 5 matches ranked by exactness. Use this first when the user mentions a company by name or ticker - you need the entity_id to call any other tool.
  • get_factGet a normalized financial value for an entity at a given period. `hub_concept_code` is a Hub-Equity standardized code (e.g. 'REVENUE', 'NET_INCOME', 'TOTAL_ASSETS', 'OTHER_CURRENT_LIABILITIES'). Use `search_concept` first if you don't know the code. `fiscal_period_type` defaults to FY; the served values are annual, and another period type is refused with an error. When nothing is served for that combination, the call returns an error result that says so: never fill the gap with an estimate.
  • get_fact_decompositionDecompose a financial fact into its constituent parts. Pass EITHER `hub_concept_code` (preferred - e.g. TOTAL_ASSETS) OR `qname` (raw XBRL like 'us-gaap:DeferredRevenueNoncurrent') for concepts without a hub mapping. Returns three layers: 1. `rollup_children` - the components this issuer reported for the figure, with their sign, on a paid plan; empty below it, with a note. 2. `linkbase_children` - XBRL calc linkbase children, RECURSIVE up to `depth` (max 3). Each child has its own `children` list. 3. `dimensional_breakdown` - axis/member slices (segment, geography), on a paid plan; empty below it, with a note. `depth=1` is open to every caller. On a paid plan, use `depth=2` for aggregates (TOTAL_ASSETS, TOTAL_LIABILITIES) to get the full breakdown tree in ONE call instead of N round-trips.
  • search_conceptSearch Hub-Equity standardized hub concepts by code or label. Returns up to 10 matches. Use this when you don't know the exact `hub_concept_code`. Accepts plain English ('Costs and Expenses') and bare hub codes ('TOTAL_ASSETS').
  • list_hubsList the catalog of standardized Hub-Equity hubs. Useful when you need to enumerate available metrics for a category (e.g. all balance-sheet hubs) without making N search_concept calls. Args: category: One of income_statement, balance_sheet, cash_flow, ratio, equity_info, metadata. Omit to list across all categories. include_non_primary: True to include derived/secondary hubs. limit: Cap (max 200, default 80).
  • get_entity_profileComprehensive company snapshot: identifiers, sector, auditor, employees, legal form, fiscal year end, recent filings summary. Use after `find_entity` when the user wants context, or as a first call when the user asks 'tell me about <company>' / 'qui est <entreprise>'.
  • get_metric_historyN-year time series for one metric (annual values only), with YoY growth (null across a missing year) and CAGR computed. Use for trend / growth questions: 'evolution of revenue over 5 years', 'CAGR du CF operating', 'Microsoft net income trend'.
  • get_segmentsDimensional breakdown of a metric (axis/member from XBRL dimensions). Use for 'revenue par région', 'profit by segment', 'split by product/geography'. Reads the dimensional (segment) values for the given period. Returns empty `axes` when the issuer reported only the consolidated total. The members of each axis need a paid plan: below it the axes are listed without them, with a note.
  • get_amendmentsSurface 10-K/A restatements for an entity (per-concept diffs when available). Use when the user asks 'has X amended any filing?', 'restatements?', 'what changed in the FY20xx 10-K/A?'.
  • get_amendment_diffPer-concept restatement diff (old_value, new_value, diff_pct, kind) across all 10-K/A amendments of an entity. Sorted by |diff_pct| desc. Differs from `get_amendments` (which returns counts per amendment): this tool flattens the per-concept changes and filters by materiality (`min_diff_pct`, default 1%) and optionally by hub_concept_code or kind. Use for 'what specifically changed in the FY24 10-K/A?', 'show all REVENUE restatements', 'material accounting corrections only'.
  • get_silent_restatementsFigures a later filing reprinted differently in its comparative columns, with no amendment filed, grouped by the filing that revealed them. The restatements `get_amendments` cannot see: most restatements are never filed as a 10-K/A or an amended ESEF report. `fiscal_year` is the year of the restated figure. `diff_pct` is in percent. Use for 'did X quietly change its past numbers?', 'restatements without an amendment', 'was FY2023 CapEx revised later?'.
  • get_silent_restatement_diffPer-concept silent restatements (old_value, new_value, diff_abs, diff_pct, kind, label, both filings as sources), sorted by |diff_pct| desc. `get_amendment_diff` on the other source: figures a later filing reprinted differently in its comparative columns, with no amendment filed. Filters by materiality (`min_diff_pct`, a fraction, default 1%), hub_concept_code and kind (`modified`, or `added` for a newly disclosed figure). Use for 'all silent REVENUE restatements of X', 'material quiet revisions only', 'which filing revised FY2023 and by how much?'.
  • +9 more on the listing page

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

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.

Hub Equity MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hub-equity-mcp": {
      "command": "uvx",
      "args": [
        "hub-equity-mcp"
      ],
      "env": {
        "HUBEQUITY_API_KEY": "YOUR_HUBEQUITY_API_KEY_HERE",
        "HUBEQUITY_API_URL": "YOUR_HUBEQUITY_API_URL_HERE"
      }
    }
  }
}

Tradememory Protocol

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

Frequently asked questions

Hub Equity MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Tradememory Protocol belongs to Finance & Fintech and uses a local stdio subprocess. Pick Hub Equity MCP for finance & fintech work and Tradememory Protocol 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.

Hub Equity MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Tradememory Protocol is listed as free. Auth: no auth required. 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 hub-equity-mcp and mnemox-ai-tradememory-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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