Ledgerfc vs Livetennisapi MCP

A side-by-side look at the Ledgerfc and Livetennisapi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Ledgerfc logoLedgerfcSports · Local subprocess (stdio)Grounded sports predictions plus European soccer and tennis arbitrage data for AI agents.59GoodAuth: not declaredLivetennisapi MCP logoLivetennisapi MCPSports · Local subprocess (stdio)Real-time tennis for ATP, WTA, Challenger and ITF — live scores, players, fixtures, model win-probability, and match-winner market prices. 12 read-only tools; a plan wall returns a plain-English explanation instead of a bare 403. Free tier, no card. npx -y livetennisapi-mcp50GoodAuth: api key required

Verdict: choose Ledgerfc for sports work as a local process; choose Livetennisapi MCP for sports as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Ledgerfc logoChoose Ledgerfc when

  • You need dedicated capabilities in the Sports domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_track_record, get_predictions, get_arbs.
Explore Ledgerfc

Livetennisapi MCP logoChoose Livetennisapi MCP when

  • You need dedicated capabilities in the Sports domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: LIVETENNISAPI_KEY.
  • You want tools like get_live_matches, get_upcoming_matches, get_match.
Explore Livetennisapi MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLedgerfc logoLedgerfcLivetennisapi MCP logoLivetennisapi MCP
CategorySportsSports
Quality signal59/100 · Good50/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFreemium
Required env varsNone listedLIVETENNISAPI_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars1152
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools1324

Tools & capabilities

Ledgerfc tools 13

  • get_track_recordHonest settled record + high-confidence subset + CLV.
  • get_predictionsUpcoming predictions with probabilities and model-vs-market edge.
  • get_arbsPRO: recently detected live arbitrage opportunities. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.
  • get_value_betsPRO: upcoming picks with positive model-vs-market edge. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.
  • searchSearch upcoming match predictions. Returns {id,title,url} results; use fetch(id) for the full prediction.
  • fetchFetch the full prediction document for a search result id.
  • submit_predictionSubmit a prediction to be scored by CLV (shadow/points).
  • get_leaderboardContributors ranked by CLV (reputation points, not cash).
  • get_contributor_scoreA contributor's CLV record.
  • place_betPlace a paper bet against our agent's prediction (points only).
  • get_balanceYour paper-points balance (not cash).
  • get_my_betsYour paper bets, newest first.
  • +1 more on the listing page

Livetennisapi MCP tools 24

  • get_live_matchesList tennis matches currently in progress, with live scores. Covers ATP, WTA, Challenger, ITF and juniors. Use this for "what tennis is on right now". Works on the FREE plan (no card needed).
  • get_upcoming_matchesList tennis matches scheduled to start soon, with players, tournament and start time. Use this for "who plays next" or to find a match id before it starts. Works on the FREE plan (no card needed).
  • get_matchFull detail for one match by id: players, score, surface, round and status. Includes market prices on PRO and model analysis on ULTRA. Works on the FREE plan (no card needed).
  • get_match_scoreCurrent score for one match — the fastest, lowest-latency read. Use this when you only need the score and already know the match id. Works on the FREE plan (no card needed).
  • search_playersSearch tennis players by name. Returns id, country, ranking and tour. Use the returned id with get_player. Works on the FREE plan (no card needed).
  • get_playerOne player's profile: ranking, country, handedness, date of birth and cached stats. Works on the FREE plan (no card needed).
  • get_fixturesUpcoming scheduled tennis fixtures, earliest first — the forward schedule, filterable by tour, player and date. Use this for "what is on this week". Works on the FREE plan (no card needed).
  • search_tournamentsSearch the tournament catalogue — the stable id space that match objects carry as tournament_id. Returns surface, indoor, host city/country and category where curated. Works on the FREE plan (no card needed).
  • get_tournamentOne tournament by its stable id — the tournament_id carried on match objects. Name, tour, surface, indoor, plus host city/country and category where curated. Works on the FREE plan (no card needed).
  • get_recent_resultsRecently completed tennis matches with final scores and winners. Filterable by tour, player, nationality and play date. Requires the BASIC plan or any History plan.
  • search_archive_matchesSearch the results archive — completed-match RESULTS from 1968 through 2022: ATP and WTA, main draws, qualifying and the ITF/futures tiers. Winner/loser-shaped records with final score, seeds and ranks AT THE TIME of the match. Use this for historical questions ("Borg's Wimbledon finals"); the archive ends 2022-12-31 where our own results (get_recent_results) begin. Requires the BASIC plan or any History plan.
  • get_archive_matchOne result from the results archive (1968–2022), with per-match serve statistics where the era recorded them — stats are null for most rows before 1991, honestly, never synthesised. Requires the BASIC plan or any History plan.
  • +12 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Ledgerfc

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ledgerfc": {
      "command": "npx",
      "args": [
        "-y",
        "@inbin/ledgerfc-mcp"
      ]
    }
  }
}

Livetennisapi MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "livetennisapi-livetennisapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livetennisapi-mcp"
      ],
      "env": {
        "LIVETENNISAPI_KEY": "YOUR_LIVETENNISAPI_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Ledgerfc is categorized under Sports and uses a local stdio subprocess. Livetennisapi MCP belongs to Sports and uses a local stdio subprocess. Pick Ledgerfc for sports work and Livetennisapi MCP for sports.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Ledgerfc has no declared pricing — check the project's own site. Livetennisapi MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ledgerfc and livetennisapi-livetennisapi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Ledgerfc has a quality signal of 59/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Livetennisapi MCP has 50/100 (Good) with 5 views, 0 installs and 152 GitHub stars.