Skip to main content
Glama
Handigraphs

handigraphs-stats-api-mcp

Official
by Handigraphs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to handigraphs-stats-api-mcp

No user-submitted related servers found.

    Related Servers

    • sleeper-mcp

      yooitsgreg
      A
      license
      A
      quality
      D
      maintenance
      Provides read-only access to the Sleeper Fantasy Sports API for league info, rosters, matchups, drafts, transactions, and player data.
      18
      100 npm
      1
      MIT

    • sleeper-mcp

      tweiss777
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only access to Sleeper fantasy sports data, including users, leagues, rosters, matchups, transactions, drafts, players, trending activity, playoff brackets, traded picks, and sport state via MCP tools.
      18
      -

    • sports-mcp-server

      YJSummers
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive sports intelligence including live scores, standings, schedules, betting odds, news, highlights, and more via SSE transport.
      -
    • therundown-data by TheRundown

      therundown-dataofficial

      TheRundown
      F
      license
      A
      quality
      A
      maintenance
      Enables local read-only access to TheRundown Product API data including sports, affiliates, market definitions, events, futures, and open main lines using your own API key.
      6
      -
    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.6/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct resource+action targets, but there is overlap between discovery tools (describe_resource vs describe_filter_capabilities) and between the two 'research' families (saved Angles research vs filter research jobs), which could cause misselection. Descriptions do a good job of clarifying the boundaries, so confusion is limited.

    Naming Consistency5/5

    Nearly every tool follows a clean verb_noun snake_case pattern (list_saved_filters, get_saved_filter, start_filter_research, cancel_filter_research). The convention is applied uniformly across discovery, CRUD, and research tools with no stylistic drift.

    Tool Count3/5

    19 tools is on the heavy side for the stated scope and includes some redundancy (two describe/discovery tools). The domain is genuinely complex (filters, research jobs, gamecenter, discovery), so most tools earn their place, but the count is borderline heavy.

    Completeness4/5

    Filter and research lifecycles are well covered (list/get/validate/save/update plus start/list/get/cancel for research), and discovery/query/gamecenter are present. The main gap is the absence of any delete operation for saved filters or saved research, which agents cannot fully work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources