mcp-data-gateway_skill

This skill unifies access to multiple financial data sources, delivering real-time quotes, historical data, and financial metrics with a single interface.
  • Rust

7

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill louloulin/claude-agent-sdk --skill mcp-data-gateway

  • SKILL.md1.7 KB

Overview

This skill provides a unified gateway for querying market and financial data across stocks, ETFs, indices, and cryptocurrencies. It consolidates multiple providers (Yahoo Finance, Alpha Vantage, Tushare, Binance) behind a consistent Rust API and automatic failover strategy. It is designed for applications that need reliable quotes, historical time series, and company financials.

How this skill works

The gateway routes requests to the preferred data source based on asset type and regional priority, then falls back to alternate providers if a call fails. It exposes methods for real-time quotes, historical OHLCK data, corporate actions, and fundamental financial statements. The Rust client offers simple async calls like get_quote, get_history, and get_fundamental with a consistent return format regardless of origin.

When to use it

  • Build trading dashboards or price feeds that need multi-market coverage
  • Fetch historical OHLC data for backtesting strategies
  • Retrieve standardized financial statements for screening and valuation
  • Power mobile apps or bots that show live crypto and stock quotes
  • Aggregate market data from multiple vendors to improve availability

Best practices

  • Prefer symbol normalization before requests (exchange suffixes, local tickers) to avoid ambiguity
  • Cache recent quotes and common historical ranges to reduce API usage and latency
  • Configure API keys and rate limits per provider to avoid throttling
  • Use the default source order but override for known regional or instrument exceptions
  • Validate and reconcile key fields (timestamps, volumes, currency) when combining sources

Example use cases

  • Real-time trader dashboard using get_quote for multiple exchanges with automatic failover
  • Backtesting pipeline that pulls daily and intraday K-lines via get_history
  • Financial screening service that extracts revenue, net income, and ROE via get_fundamental
  • Crypto portfolio tracker that prioritizes Binance for spot pricing and falls back to Yahoo
  • Cross-market reporting tool that consolidates US, China, and crypto data into one feed

FAQ

The gateway chooses by instrument type and market: US stocks prefer Yahoo → Alpha Vantage, China A-shares use Tushare → Yahoo, and crypto uses Binance → Yahoo as fallback.

How do I handle rate limits and API keys?

Configure provider credentials in the client and set per-source rate limits; cache results and batch historical requests to minimize calls.

Can I force a specific data source?

Yes. The client allows overriding the default source selection for individual requests or globally in the configuration.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational