Skip to main content
Glama
xcreener

@xcreener/mcp

Official
by xcreener

Related Servers

Alternatives to @xcreener/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      A resilient MCP server wrapping FiinQuant/FiinQuantX Python SDK for Claude Desktop and Cursor, providing market data, fundamental analysis, screening, and technical indicators via stdio with timeouts, error envelopes, and free-tier guards.
      26
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for TradingView's market screener API, enabling stock, forex, crypto, and ETF screening, technical analysis, and investor workflows via Claude or CLI.
      12
      290 npm
      50
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for screening Indian stocks and mutual funds by wrapping screener.in and Morningstar India, enabling fundamental queries from Claude or Cursor.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A thin stdio proxy to Quantustik's hosted MCP server, providing live S&P 500 signals, forecasts, and market data for MCP clients that only support local stdio servers.
      58 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP proxy that bridges Mendix Marketplace's Streamable HTTP endpoint to stdio, enabling Claude Code and other stdio-only MCP clients to access Mendix Marketplace tools and prompts dynamically.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Institutional Financial Intelligence MCP Server for Claude Desktop & AI Agents. Sub-second market data, technical indicators, SEC EDGAR 10-K parsing, and local SQLite backtesting.
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: validate parses/plans without execution, explain returns the execution plan and explanation, run executes against live data, and nl_reference fetches documentation. There is no overlap in purpose despite validate and explain sharing a parsing/planning step.

    Naming Consistency4/5

    All tool names share the consistent 'xql_' prefix, but the pattern after the prefix is not perfectly uniform: three use a verb (validate, explain, run) while one uses a noun phrase (nl_reference). Still readable and predictable, with minor deviation.

    Tool Count5/5

    With only 4 tools, the server is tightly focused on XQL query operations: validate, explain, run, and reference. Each tool serves a necessary function in the query workflow without redundancy.

    Completeness5/5

    The tool surface covers the full query lifecycle: reference for syntax, validate for error checking, explain for plan analysis, and run for execution. No obvious gaps exist given the stated purpose of an XQL query server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues