# io.github.yaotsakpo/ledgerfc (remote · mcp.ledgerfc.com)

Grounded sports predictions plus European soccer and tennis arbitrage data for AI agents.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.ledgerfc.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/yaotsakpo-ledgerfc/mcp.md), [page](https://verifymcp.io/servers/yaotsakpo-ledgerfc/mcp)
- npm · `@inbin/ledgerfc-mcp`: 39/100, [markdown](https://verifymcp.io/servers/yaotsakpo-ledgerfc/inbin-ledgerfc-mcp.md), [page](https://verifymcp.io/servers/yaotsakpo-ledgerfc/inbin-ledgerfc-mcp)

## Channel facts

- Endpoint: `https://mcp.ledgerfc.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 640 tokens (~49/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the io.github.yaotsakpo/ledgerfc MCP server?

io.github.yaotsakpo/ledgerfc is a hosted endpoint at https://mcp.ledgerfc.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http yaotsakpo-ledgerfc 'https://mcp.ledgerfc.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "yaotsakpo-ledgerfc": {
      "url": "https://mcp.ledgerfc.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "yaotsakpo-ledgerfc": {
      "type": "http",
      "url": "https://mcp.ledgerfc.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.yaotsakpo-ledgerfc]
url = "https://mcp.ledgerfc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yaotsakpo-ledgerfc": {
      "type": "remote",
      "url": "https://mcp.ledgerfc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yaotsakpo-ledgerfc --url 'https://mcp.ledgerfc.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yaotsakpo-ledgerfc:
    url: "https://mcp.ledgerfc.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "yaotsakpo-ledgerfc": {
      "Transport": "http",
      "Url": "https://mcp.ledgerfc.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add yaotsakpo-ledgerfc -t streamable-http -u 'https://mcp.ledgerfc.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "yaotsakpo-ledgerfc": {
      "type": "http",
      "url": "https://mcp.ledgerfc.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `get_track_record` (~20 tokens)

Honest settled record + high-confidence subset + CLV.

### `get_predictions` (~47 tokens)

Upcoming predictions with probabilities and model-vs-market edge.

Input parameters:

- `league` (string): Filter to one league code, e.g. EPL.
- `limit` (integer): Max predictions to return.

### `get_arbs` (~160 tokens)

PRO: recently detected live arbitrage opportunities. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.

Input parameters:

- `api_key` (string): Optional Pro API key (get one with /key in the Ledger FC Telegram bot). Preferred instead: send it as an Authorization: Bearer header, so it never enters the conversation.
- `live_rescan` (boolean): If true, fetch fresh odds NOW and return current arbs (age ~0) instead of logged ones. Rate-limited (costs API credits). Falls back to logged arbs if unavailable.
- `within_seconds` (integer): Look-back window in seconds. Default is tight because arbs die fast; widen only for a historical view.

### `get_value_bets` (~87 tokens)

PRO: upcoming picks with positive model-vs-market edge. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.

Input parameters:

- `api_key` (string): Optional Pro API key (get one with /key in the Ledger FC Telegram bot). Preferred instead: send it as an Authorization: Bearer header, so it never enters the conversation.

### `search` (~44 tokens)

Search upcoming match predictions. Returns {id,title,url} results; use fetch(id) for the full prediction.

Input parameters:

- `query` (string): Team or league to search upcoming predictions for.

### `fetch` (~37 tokens)

Fetch the full prediction document for a search result id.

Input parameters:

- `id` (string, required): A result id from search, e.g. pred:123.

### `submit_prediction` (~63 tokens)

Submit a prediction to be scored by CLV (shadow/points).

Input parameters:

- `contributor_id` (string, required)
- `match_id` (integer, required)
- `p_away` (number, required)
- `p_draw` (number, required)
- `p_home` (number, required)

### `get_leaderboard` (~23 tokens)

Contributors ranked by CLV (reputation points, not cash).

### `get_contributor_score` (~25 tokens)

A contributor's CLV record.

Input parameters:

- `contributor_id` (string, required)

### `place_bet` (~61 tokens)

Place a paper bet against our agent's prediction (points only).

Input parameters:

- `agent_id` (string, required)
- `match_id` (integer, required)
- `side` (string, required)
- `stake_points` (number, required): Paper points to stake (min 1).

### `get_balance` (~25 tokens)

Your paper-points balance (not cash).

Input parameters:

- `agent_id` (string, required)

### `get_my_bets` (~25 tokens)

Your paper bets, newest first.

Input parameters:

- `agent_id` (string, required)

### `get_bet` (~23 tokens)

One paper bet by id.

Input parameters:

- `bet_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yaotsakpo-ledgerfc/mcp#diagnostics

## Score history

- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 63
- 2026-09-03: 63
- 2026-09-02: 62
- 2026-09-01: 62
- 2026-08-31: 62
- 2026-08-30: 48
- 2026-08-29: 60
- 2026-08-28: 60
- 2026-08-27: 60
- 2026-08-26: 59
- 2026-08-25: 56
- 2026-08-24: 55
- 2026-08-23: 55

## Common questions

### What is the io.github.yaotsakpo/ledgerfc MCP server?

io.github.yaotsakpo/ledgerfc is an MCP server listed in the public MCP registry as io.github.yaotsakpo/ledgerfc. Grounded sports predictions plus European soccer and tennis arbitrage data for AI agents. This page covers its hosted endpoint (https://mcp.ledgerfc.com/mcp).

### Is the io.github.yaotsakpo/ledgerfc MCP server safe to use?

io.github.yaotsakpo/ledgerfc scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.yaotsakpo/ledgerfc MCP server expose?

io.github.yaotsakpo/ledgerfc exposes 13 tools: get_track_record, get_predictions, get_arbs, get_value_bets, search, and 8 more. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.

### Does the io.github.yaotsakpo/ledgerfc MCP server require authentication?

No. We connected to io.github.yaotsakpo/ledgerfc without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.yaotsakpo/ledgerfc MCP server still maintained?

io.github.yaotsakpo/ledgerfc is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.ledgerfc.com/mcp
- Repository: https://github.com/yaotsakpo/ledgerfc-mcp
- Changelog RSS feed: https://verifymcp.io/servers/yaotsakpo-ledgerfc/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/yaotsakpo-ledgerfc/mcp.json
- HTML version of this page: https://verifymcp.io/servers/yaotsakpo-ledgerfc/mcp