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 gradedqualityDmaintenanceEnables 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.-
- AlicenseBqualityBmaintenanceEnables 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.9MIT
- 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.558 npmApache 2.0
TDQS
Scored across 3 tools
get_timeseries and get_latest both fetch bar data, but the descriptions clearly separate them (explicit date ranges vs. most-recent N bars), and list_sources is a distinct discovery tool. An agent could occasionally pick the wrong fetch tool, but the split is well-explained. Naming edges toward the same verb, which slightly increases the chance of misselection between the two read tools.
All three tools follow a consistent snake_case verb_noun pattern: get_timeseries, get_latest, list_sources. The pattern is predictable and readable, and no conventions are mixed.
Three tools is slightly thin, but the server's purpose is narrow read-only market/source data, and each tool earns its place. A small surface is appropriate here rather than over-scoped.
The core workflow (discover sources, fetch historical ranges, fetch latest bars) is fully covered with sensible allowance and truncation behavior. Minor gap: no ticker search/metadata lookup to resolve valid symbols before fetching, which an agent must work around via list_sources.