Skip to main content
Glama
usehyperodds

Hyperodds MCP

by usehyperodds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Hyperodds MCP

No user-submitted related servers found.

    Related Servers

    • hyperliquid-info

      wtfsayo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Hyperliquid's public market, user, vault, and staking data via 61 MCP tools, covering perpetuals, spot, and borrow-lend information.
      MIT

    • hyperliquid-mcp

      kitsune-de
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for querying Hyperliquid perp markets, funding rates, order books, candles, and account positions/fills/funding for any address, without needing API keys or wallets.
      8
      21 npm
      2
      MIT

    • 0xarchive-mcp

      0xArchiveIO
      A
      license
      B
      quality
      A
      maintenance
      MCP server for querying historical and real-time crypto market data across Hyperliquid, Hyperliquid HIP-3, and Lighter.xyz - orderbooks, trades, candles, funding, open interest, liquidations, and data quality metrics.
      100
      64 npm
      13
      MIT

    • polymarket-mcp

      fzlzjerry
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server exposing Polymarket's public prediction-market data. Search markets, read live odds and order books, pull historical probability time-series, and inspect public wallet positions.
      14
      41 PyPI
      MIT

    • polymarket-us-mcp

      anjavera
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to Polymarket US public market data, including prices, order books, and spread/fee analytics, via MCP tools.
      16
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation3/5

    odds_markets vs odds_new overlap heavily: odds_new is essentially odds_markets pre-sorted newest-first with the same fields, and odds_markets already offers a 'new' sort. odds_cluster and odds_fair are clearly distinct (aggregation view vs single-market pricing), but the listing pair creates a real misselection risk.

    Naming Consistency4/5

    All four tools share the same odds_ prefix, giving a predictable namespace. The suffixes vary in kind (plural noun, singular noun, adjective), but the pattern remains readable and consistent enough to infer purpose.

    Tool Count4/5

    Four tools is on the lean side but appropriate for a focused odds/pricing analytics service. Each tool covers a distinct query shape, though odds_new is largely redundant with odds_markets and could be folded into it.

    Completeness4/5

    The surface covers the core domain well: market discovery (with filters, sorting, paging), cross-deployer clustering, and single-market fair line with edge. Minor gaps exist, such as no deployer/category enumeration or historical line tracking, but agents can work around these via filters and text search.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources