Sugra API MCP
OfficialRelated Servers
Alternatives to Sugra API MCP
AlicenseBqualityBmaintenanceUS/HK markets — 110 tools: real-time quotes, options, orders, fundamentals, alerts, DCA & portfolio19316Apache 2.0- AlicenseAqualityCmaintenanceProvides curated US economic data from Treasury, FRED, BLS, BEA, and other sources through an MCP interface. Enables querying economic series, fetching data with provenance tracking, and accessing cached artifacts.9MIT
Related Servers

AxionQuant MCP Serverofficial
AlicenseCqualityCmaintenanceEnables AI agents and LLM apps to answer natural-language financial questions using live market data, including stocks, crypto, forex, futures, indices, ETFs, economic data, news, sentiment, SEC filings, earnings, financials, insider trading, ESG, credit ratings, and web traffic.13289 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access real-time financial data including crypto, equities, on-chain, prediction markets, and macro via a single API key.MIT
- AlicenseNot gradedqualityDmaintenanceProvides live data API for AI agents with 51 REST endpoints across finance, travel, weather, news, and more, using USDC micropayments without API keys.42 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to pull end-of-day and historical stock prices, ticker metadata with available date ranges, crypto pair prices at a chosen resample frequency, and recent financial news filtered by ticker or tag. Runs either against a hosted gateway endpoint or locally over stdio, with API-key handling for the account tiers each data source requires.301 npmMIT

inferventisofficial
FlicenseNot gradedqualityCmaintenanceEnables AI agents to access real-time financial data, news, and web reading through a single MCP endpoint with zero installation.-
ApexTick MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to access low-latency global market data, including quotes, fundamentals, technical indicators, earnings context, sector movers, and options implied-volatility screening across equities, ETFs, FX pairs, and cryptocurrencies.8MIT
TDQS
Scored across 8 tools
Each tool has a reasonably distinct role: catalog discovery (list_toolsets, list_sources, search_endpoints, describe_endpoint), execution (call_endpoint, fetch_data), and entity screening (sugra_entity_lookup, sugra_entity_screen). The main overlap is fetch_data versus the search+describe+call sequence, and list_toolsets versus list_sources, but the descriptions explicitly explain when to prefer each, so misselection risk is low.
All names are snake_case with a verb_noun shape (search_endpoints, call_endpoint, fetch_data, list_sources, describe_endpoint), which is consistent and readable. The two entity tools break the pattern by prefixing a product name (sugra_entity_lookup, sugra_entity_screen), a minor deviation that still conveys grouping.
Eight tools is well within the ideal range and each one earns its place: discovery, description, direct calling, a one-step convenience path, and two domain-specific entity operations. Nothing appears redundant or bolted on.
The surface covers the full loop of finding, inspecting, and invoking catalog endpoints, plus the entity KYB/screening use case, with structured errors and parameter feedback. Minor gaps exist — no tool to enumerate all endpoints within a toolset/source without a query, and batch invocation is only implicit via call_endpoint's bulk bodies — but agents can work around these.