Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.betsbeats/betsbeats

REMOTE · API.BETSBEATS.COM

Verify sealed BetsBeats picks, read the public record, and do odds math. Read-only. 21+.

74 Trust /100

Last scanned (1 hour ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 910 tokens (~151/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 72

    First indexed and scored.

Diagnostics

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://api.betsbeats.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=betsbeats.com CN=YE1,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 ECDSA 256 ECDSA-SHA384 6e7c8bbedf130159d95083b8bc4942d0ca9
SANs: *.betsbeats.com, betsbeats.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 api.betsbeats.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
betsbeats.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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.betsbeats.com/mcp Verified 200
http (plaintext) http://api.betsbeats.com/mcp HTTPS enforced 301 https://api.betsbeats.com/mcp
MCP tools · 6 exposed · ~793 tokens

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 →

Tool Tokens
convert_odds ~164

Convert betting odds between american (+150, -110), decimal (2.5), fractional (3/2) and implied probability (0.4 or 40%). Decimal d = 1 + n/d for fractions, 1 + a/100 for +a, 1 + 100/a for -a; implied probability = 1/decimal. Pure math, no data lookup. For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.

NameTypeReqDescription
formatstringyesFormat of the odds value.
oddsstringyesThe odds value, e.g. "+150", "2.5", "3/2", "0.4".

No output schema declared.

No examples provided.

expected_value ~179

Expected value of a wager from odds and your own win probability (percent, 0-100). EV = stake * (p*(decimal-1) - (1-p)); break-even probability = 1/decimal; edge = p - break-even. The probability is your input, not a prediction by BetsBeats. For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.

NameTypeReqDescription
formatstringyesFormat of the odds.
oddsstringyesThe odds value, e.g. "-110", "1.91", "10/11".
stakenumber–Stake for the EV amount. Default 100.
win_probability_percentnumberyesYour estimated chance of winning, 0-100 exclusive.

No output schema declared.

No examples provided.

get_record ~89

The public running record of the BetsBeats main pick: wins, losses, voids (a void is a push or no pick), the current streak and the date range, exactly as shown on the results page. Losses are included. For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_results ~94

Settled BetsBeats picks for one day (YYYY-MM-DD): the main pick and extras with commitment hashes, selections, odds and results. Only days that are already settled and public are returned. For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.

NameTypeReqDescription
datestringyesDay to read, YYYY-MM-DD.

No output schema declared.

No examples provided.

parlay_payout ~122

Payout of a parlay (accumulator) of 2 to 20 legs that all win: combined decimal odds = product of leg decimals; payout = stake * combined; profit = payout - stake; combined implied probability = 1 / combined (legs assumed independent). For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.

NameTypeReqDescription
legsarrayyes2 to 20 legs.
stakenumber–Stake. Default 100.

No output schema declared.

No examples provided.

verify_pick ~145

Verify a sealed BetsBeats pick from its SHA-256 commitment hash (full 64 hex characters, or a prefix of 16 or more). Before the pick settles this only confirms the hash exists and returns sealed_at and kickoff_at. After settlement it returns the revealed preimage, recomputes SHA-256 on the server and reports matches=true/false, plus the result and a verify_url. For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.

NameTypeReqDescription
hashstringyesCommitment hash: 64 hex characters, or a unique prefix of at least 16.

No output schema declared.

No examples provided.

Install

How do I install the io.github.betsbeats/betsbeats MCP server?

io.github.betsbeats/betsbeats is a hosted endpoint at https://api.betsbeats.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 · api.betsbeats.com

# add to Claude Code
claude mcp add --transport http betsbeats-betsbeats 'https://api.betsbeats.com/mcp'
Common questions

What is the io.github.betsbeats/betsbeats MCP server?

io.github.betsbeats/betsbeats is an MCP server listed in the public MCP registry as io.github.betsbeats/betsbeats. Verify sealed BetsBeats picks, read the public record, and do odds math. Read-only. 21+. This page covers its hosted endpoint (https://api.betsbeats.com/mcp).

Is the io.github.betsbeats/betsbeats MCP server safe to use?

io.github.betsbeats/betsbeats scores 74 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.betsbeats/betsbeats MCP server expose?

io.github.betsbeats/betsbeats exposes 6 tools: verify_pick, get_record, get_results, convert_odds, expected_value, parlay_payout. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.

Does the io.github.betsbeats/betsbeats MCP server require authentication?

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

Is the io.github.betsbeats/betsbeats MCP server still maintained?

io.github.betsbeats/betsbeats 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.