Skip to main content
Glama
a10102010

north7-market-intelligence

by a10102010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to north7-market-intelligence

No user-submitted related servers found.

    Related Servers

    • oneqaz-trading-mcp by oneqaz-trading

      oneqaz-trading-mcpofficial

      oneqaz-trading
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with real-time financial market intelligence including regime detection, adaptive signals, macro context chains, and cross-market analysis for crypto, US, and Korean stocks.
      81 PyPI
      MIT

    • fia-signals-mcp

      Odds7
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access professional crypto market intelligence via 8 MCP tools, covering market regime, fear/greed, funding rates, DeFi yields, token signals, wallet risk, and contract audits. Backed by real-time data from Binance, DeFiLlama, Etherscan, with both free tools and x402 micropayment options.
      2
      -

    • TradingView MCP Server

      niketbiyani
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and trading microservices to access real-time technical indicators, market regime classification, moving average summaries, and oscillator signals for stocks, indices, crypto, and forex via MCP tools or REST endpoints.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several tools have overlapping purposes: get_agent_context aggregates get_risk_index, get_market_regime, and get_events; get_impact overlaps with get_events; and get_commodity_signals partially duplicates the scr_daily source inside get_trading_signals. Descriptions do clarify intended usage order (e.g. 'use get_risk_index first'), which prevents total confusion, but an agent could still misselect.

    Naming Consistency5/5

    Every tool follows a clean get_<noun> snake_case pattern (get_prices, get_market_regime, get_stock_analysis, get_risk_index, etc.). There are no deviations in casing or verb style.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range and each covers a distinct data domain (prices, signals, analysis, regime, risk, events, relationships). The count is neither thin nor bloated for a market intelligence server.

    Completeness4/5

    The surface covers a broad lifecycle: regime/risk assessment, prices, per-stock analysis, signals, commodity signals, sector rotation, events, event-to-asset mapping, and a knowledge graph. Minor gaps exist (e.g. no historical time-series or portfolio history depth beyond what get_model_portfolio returns), but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources