Skip to main content
Glama
yaotsakpo

ledgerfc-mcp

by yaotsakpo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ledgerfc-mcp

No user-submitted related servers found.

    Related Servers

    • sharpapi-mcp by Sharp-API

      sharpapi-mcpofficial

      Sharp-API
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query live sports betting odds, best prices, arbitrage, +EV bets, and middles directly through Model Context Protocol tools.
      8
      MIT
    • Odds-API MCP Server by odds-api-io

      Odds-API MCP Serverofficial

      odds-api-io
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to access sports betting odds data from 265+ bookmakers across 34 sports, including events, odds, historical data, arbitrage, and value bets.
      25
      94 npm
      2
      MIT

    • io.github.christianclaudio/esp

      christianclaudio
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to query live and historical sports analytics, consensus betting odds, predictions, scores, schedules, standings, rosters, news, play-by-play, and win probabilities through structured tools and resources.
      33
      648 PyPI
      Apache 2.0

    • betbetter-mcp

      edushinka
      A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with sports model win probabilities and fair odds across nine sports without requiring an API key.
      3
      60 npm
      MIT

    • SportWizzard MCP Server

      sportwizzard
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to query live sports betting data including odds, edges, arbitrage opportunities, player/team stats, and reference data using the SportWizzard API.
      20
      240 npm
      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

    B3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: track record, predictions, arbs, value bets, search/fetch pair, submission, leaderboard, contributor score, betting operations. No two tools overlap in a way that would cause misselection.

    Naming Consistency5/5

    All tools use consistent lowercase snake_case with a verb_noun pattern. Most start with 'get_', with a few action verbs like 'search', 'fetch', 'submit_prediction', and 'place_bet' that still follow the same style.

    Tool Count5/5

    13 tools is well within the ideal range for a domain covering predictions, submission, scoring, and betting. Each tool serves a distinct function and none appear redundant.

    Completeness4/5

    The surface covers the main lifecycle: viewing predictions, fetching details, submitting predictions, checking leaderboard and contributor scores, placing bets, and viewing balance and bet history. Minor missing operations like updating or canceling bets are not critical for the core workflow.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources