Skip to main content
Glama

Related Servers

Alternatives to CryptoCapi

Related Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-compatible AI clients to access live crypto market data and AI-driven quantitative analysis, with structured outputs and full observability.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    AI-powered crypto signal intelligence for 20 assets (BTC, ETH, SOL, etc). 6 scoring dimensions: whale activity, technical analysis, derivatives flow, narrative strength, sentiment, market structure. Market regime detection (TRENDING/RANGING), portfolio optimization, and accuracy tracking. 9 read-only MCP tools. Free via MCP, $0.001 USDC via x402 on Base for REST API.
    3
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    A remote Model Context Protocol (MCP) server for real-time cryptocurrency and stock market analysis. Provides AI-powered market intelligence tools with 9 theory-based analysis engines, multi-chain DEX discovery, and enterprise features.
    -
  • A
    license
    A
    quality
    B
    maintenance
    Real-time crypto market & tokenized equity intelligence MCP over x402 USDC on Base mainnet (eip155:8453) by Keith S. (kwizzlesurp.com · Sevtech · Dragon&PandaDuo). Includes price feeds, volatility, sentiment, risk scores, NAV deviation, and peg-gap radar. Verified provider on x402-trust.com.
    2
    13
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents and trading desks to query institutional quantitative market telemetry, 100-bin auction profiles, order-book crowd sentiment, conformal volatility cones, macro session radar, and prop-risk metrics across 130+ global assets. It also renders interactive market-intelligence micro-app frames inside MCP-compatible chat clients.
    5
    Apache 2.0

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

Each tool maps to a distinct engine and access tier: get_insight (Radar/Quant Plus analysis per coin), scan_market (Quant Plus ranking), batch_signals (Quant Plus multi-coin), get_signal (Quant Pro trading pair). The main risk is get_signal vs batch_signals, which sound similar, but the descriptions explicitly contrast the input formats ("BTCUSDT" vs "bitcoin") and passes, so an agent can tell them apart.

Naming Consistency4/5

All four names are snake_case with a verb/noun shape (get_insight, get_signal, scan_market) and one noun-led outlier (batch_signals). The convention is consistent and readable, with only a minor deviation in the batch_ prefix style.

Tool Count4/5

Four tools for a crypto analytics/signal service is compact and each covers a genuinely different surface (single-asset insight, market scan, multi-asset batch, trading-pair signal). It is slightly thin—no dedicated asset-discovery or history tool—but nothing is redundant.

Completeness3/5

Core analytical workflows are covered, but there is no tool to list supported assets, engines, or historical readings, which the descriptions repeatedly reference. Agents will discover the curated universe only by trial and error via available:false or 403 responses, a notable gap for a data service.

Maintenance

ActivityActive
ResponsivenessNo recent community issues