AuraStream MCP
Related Servers
Alternatives to AuraStream MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query cryptocurrency network and market data through tools for time-series metrics, OHLCV candles, bid/ask quotes, index levels, and asset or market metadata.MIT
- FlicenseNot gradedqualityDmaintenanceEnables fetching live crypto market data from Binance, Bybit, and Hyperliquid via MCP tools, including klines, orderbook, funding rates, technical indicators, and market breadth for real-time analysis by LLMs.-

Iturri MCP serverofficial
AlicenseNot gradedqualityFmaintenanceEnables AI agents to discover, validate, and fetch verified crypto and US-equity market data, including quality-flagged OHLCV bars, leakage-safe features, funding, open interest, order flow, context, events, and regime labels. It supports free catalog discovery and x402 USDC payments per call.MIT- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to access live crypto market data and AI-driven quantitative analysis, with structured outputs and full observability.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to pull crypto discovery, rankings, and market-cap data from CoinMarketCap, Fed macro and liquidity series with point-in-time vintages via FRED/ALFRED, and a curated, sourced FOMC hike/cut/hold decision calendar. It exposes eight MCP tools whose API credentials are resolved server-side, and also feeds bounded, checkpointed ingestion streams through the agent-connector-sdk source adapter.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and analyze financial data, stock information, company fundamentals, and market insights through 250+ tools spanning stocks, ETFs, crypto, forex, commodities, and economics. Supports dynamic, static, or full toolset loading over HTTP/SSE for Claude and other MCP clients.436 npmApache 2.0
TDQS
Scored across 3 tools
Each tool maps to a distinct step: discovery (list_sources), bounded historical fetch (get_timeseries), and a convenience recent-bars fetch (get_latest). get_timeseries and get_latest overlap substantially since the latter is effectively a date-free subset of the former, but the descriptions clearly frame get_latest as the 'don't pick dates' shortcut.
All three tools are snake_case verb-first names (list_/get_/get_) that read predictably and map loosely to resource retrieval. No mixed conventions or cryptic abbreviations.
Three tools is on the lean side but each earns its place: source discovery, ranged history, and latest bars. A small read-only data-fetch server doesn't need a larger surface, though it sits near the thin end.
The read-only retrieval lifecycle (discover sources → fetch history → fetch recent bars) is fully covered with no dead ends for the core workflow. Notable gap: every metered call consumes monthly allowance, yet there is no tool to check remaining quota/usage, and no ticker search or validation helper.