Sugra API MCP
OfficialRelated Servers
Alternatives to Sugra API MCP
AlicenseBqualityAmaintenanceUS/HK markets — 110 tools: real-time quotes, options, orders, fundamentals, alerts, DCA & portfolio16513Apache 2.0- AlicenseAqualityDmaintenanceProvides 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
AlicenseCqualityBmaintenanceEnables 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.13299 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access real-time financial data including crypto, equities, on-chain, prediction markets, and macro via a single API key.-
- AlicenseNot gradedqualityCmaintenanceProvides live data API for AI agents with 51 REST endpoints across finance, travel, weather, news, and more, using USDC micropayments without API keys.76 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.24 npmMIT

inferventisofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to access real-time financial data, news, and web reading through a single MCP endpoint with zero installation.-
BlockRun MCPofficial
AlicenseAqualityAmaintenanceProvides Claude with real-time access to markets, research, X/Twitter, and crypto data via a unified pay-per-call system with no API keys.191,144 npm391MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: entity screening, identifier lookup, catalog search/describe/call, and listing. Some ambiguity exists between sugra_entity_screen and sugra_entity_lookup (both produce screening signals) and between fetch_data and the search_endpoints/call_endpoint workflow, but descriptions make the intended use clear.
The catalog tools consistently use verb_noun names like search_endpoints, describe_endpoint, call_endpoint, list_toolsets, and list_sources. The two entity tools use a different pattern with the sugra_entity_ prefix, creating a minor but noticeable inconsistency.
Eight tools is well-scoped for a server that combines two specialized entity operations with a general endpoint-catalog workflow. Each tool earns its place, and the count avoids both sprawl and thinness.
The tool set covers the full loop for entity screening and identifier-based KYB lookup, plus discovery and execution of catalog endpoints via search, describe, and call. The one-step fetch_data and structured error handling prevent dead ends.