io.github.yaotsakpo/ledgerfc
REMOTE · MCP.LEDGERFC.COM · 2 COMPONENTS
Grounded sports predictions plus European soccer and tennis arbitrage data for AI agents.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 640 tokens (~49/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: pass → 0.90 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- 28 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.13 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.ledgerfc.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ledgerfc.com | CN=YE2,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 55d9ca4069c4cdd10ad87434b0bc7941fb2 |
| SANs: mcp.ledgerfc.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ledgerfc.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ledgerfc.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ledgerfc.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ledgerfc.com/mcp | HTTPS enforced | 308 | https://mcp.ledgerfc.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch ~37
Fetch the full prediction document for a search result id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A result id from search, e.g. pred:123. |
No output schema declared.
No examples provided.
get_arbs ~160
PRO: recently detected live arbitrage opportunities. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_balance ~25
Your paper-points balance (not cash).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_bet ~23
One paper bet by id.
| Name | Type | Req | Description |
|---|---|---|---|
| bet_id | integer | yes | – |
No output schema declared.
No examples provided.
get_contributor_score ~25
A contributor's CLV record.
| Name | Type | Req | Description |
|---|---|---|---|
| contributor_id | string | yes | – |
No output schema declared.
No examples provided.
get_leaderboard ~23
Contributors ranked by CLV (reputation points, not cash).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_my_bets ~25
Your paper bets, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_predictions ~47
Upcoming predictions with probabilities and model-vs-market edge.
| Name | Type | Req | Description |
|---|---|---|---|
| league | string | – | Filter to one league code, e.g. EPL. |
| limit | integer | – | Max predictions to return. |
No output schema declared.
No examples provided.
get_track_record ~20
Honest settled record + high-confidence subset + CLV.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_value_bets ~87
PRO: upcoming picks with positive model-vs-market edge. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
place_bet ~61
Place a paper bet against our agent's prediction (points only).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| match_id | integer | yes | – |
| side | string | yes | – |
| stake_points | number | yes | Paper points to stake (min 1). |
No output schema declared.
No examples provided.
search ~44
Search upcoming match predictions. Returns {id,title,url} results; use fetch(id) for the full prediction.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Team or league to search upcoming predictions for. |
No output schema declared.
No examples provided.
submit_prediction ~63
Submit a prediction to be scored by CLV (shadow/points).
| Name | Type | Req | Description |
|---|---|---|---|
| contributor_id | string | yes | – |
| match_id | integer | yes | – |
| p_away | number | yes | – |
| p_draw | number | yes | – |
| p_home | number | yes | – |
No output schema declared.
No examples provided.
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.
remote · mcp.ledgerfc.com
claude mcp add --transport http yaotsakpo-ledgerfc 'https://mcp.ledgerfc.com/mcp'
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 72 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.