Skip to main content
Glama
Sugra-Systems

Sugra API MCP

Official

Related Servers

Alternatives to Sugra API MCP

  • A
    license
    B
    quality
    A
    maintenance
    US/HK markets — 110 tools: real-time quotes, options, orders, fundamentals, alerts, DCA & portfolio
    164
    14
    Apache 2.0
  • A
    license
    A
    quality
    C
    maintenance
    Provides 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.
    9
    MIT

Related Servers

  • A
    license
    C
    quality
    B
    maintenance
    Enables 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.
    132
    66 npm
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to access real-time financial data including crypto, equities, on-chain, prediction markets, and macro via a single API key.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides live data API for AI agents with 51 REST endpoints across finance, travel, weather, news, and more, using USDC micropayments without API keys.
    61 npm
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Provides Claude with real-time access to markets, research, X/Twitter, and crypto data via a unified pay-per-call system with no API keys.
    19
    1,121 npm
    394
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI agents to access SEC EDGAR filings, US Treasury rates, BLS labor statistics, and economic indicators without API keys.
    6
    21 npm
    MIT

TDQS

A4.3/5.0

Scored across 8 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityActive
ResponsivenessWithin a week