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.DanielTomaro13/sportsdata-mcp

PYPI · SPORTSDATA-MCP

Live sports data and cross-book betting odds — 801 tools, 63 providers, 43 needing no key.

Available components

−15 this week 52 Trust /100

Last scanned (11 hours ago)

Scores higher than 55% of PyPI servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to DanielTomaro13/sportsdata-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 38 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (10)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Package version: 0.22.1 → 0.27.0 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 0.22.1 → 0.27.0 functional
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
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 · Analysed pypi/sportsdata-mcp@0.27.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo DanielTomaro13/sportsdata-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/DanielTomaro13/sportsdata-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.27.0
Rekor log index 2495408497
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:36dc547c2c01923c5e7dbb3e574270908535812286c659a920e6ee0870c05dd2

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 24 packages
Packages resolved 24
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 803 exposed · ~120,232 tokens partial

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
datagolf_fantasy_projections ~136

No description provided.

NameTypeReqDescription
file_formatstring––
sitestring––
slatestring––
tourstring––

No output schema declared.

No examples provided.

datagolf_field_updates ~106

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_hist_dfs_event_list ~112

No description provided.

NameTypeReqDescription
file_formatstring––
sitestring––

No output schema declared.

No examples provided.

datagolf_hist_dfs_points ~150

No description provided.

NameTypeReqDescription
event_idintegeryes–
file_formatstring––
sitestring––
tourstring––
yearintegeryes–

No output schema declared.

No examples provided.

datagolf_hist_event_list ~118

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––
yearinteger––

No output schema declared.

No examples provided.

datagolf_hist_matchups ~160

No description provided.

NameTypeReqDescription
bookstring––
event_idintegeryes–
file_formatstring––
odds_formatstring––
tourstring––
yearintegeryes–

No output schema declared.

No examples provided.

datagolf_hist_odds_event_list ~93

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_hist_outrights ~204

No description provided.

NameTypeReqDescription
bookstring––
event_idintegeryes–
file_formatstring––
marketstring––
odds_formatstring––
tourstring––
yearintegeryes–

No output schema declared.

No examples provided.

datagolf_hist_results ~141

No description provided.

NameTypeReqDescription
event_idintegeryes–
file_formatstring––
tourstring––
yearintegeryes–

No output schema declared.

No examples provided.

datagolf_hist_results_event_list ~99

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_hist_rounds ~148

No description provided.

NameTypeReqDescription
event_idintegeryes–
file_formatstring––
tourstring––
yearintegeryes–

No output schema declared.

No examples provided.

datagolf_in_play ~138

No description provided.

NameTypeReqDescription
file_formatstring––
odds_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_live_hole_stats ~128

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_live_strokes_gained ~127

No description provided.

NameTypeReqDescription
file_formatstring––
sgstring––

No output schema declared.

No examples provided.

datagolf_live_tournament_stats ~151

No description provided.

NameTypeReqDescription
displaystring––
file_formatstring––
roundstring––
statsarray––

No output schema declared.

No examples provided.

datagolf_matchups ~162

No description provided.

NameTypeReqDescription
file_formatstring––
marketstring––
odds_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_matchups_all_pairings ~137

No description provided.

NameTypeReqDescription
file_formatstring––
odds_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_outrights ~187

No description provided.

NameTypeReqDescription
file_formatstring––
marketstring––
odds_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_player_decompositions ~111

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_player_list ~76

No description provided.

NameTypeReqDescription
file_formatstring––

No output schema declared.

No examples provided.

datagolf_pre_tournament ~163

No description provided.

NameTypeReqDescription
add_positionstring––
file_formatstring––
odds_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_pre_tournament_archive ~159

No description provided.

NameTypeReqDescription
event_idinteger––
file_formatstring––
odds_formatstring––
tourstring––
yearinteger––

No output schema declared.

No examples provided.

datagolf_rankings ~82

No description provided.

NameTypeReqDescription
file_formatstring––

No output schema declared.

No examples provided.

datagolf_schedule ~98

No description provided.

NameTypeReqDescription
file_formatstring––
tourstring––

No output schema declared.

No examples provided.

datagolf_skill_ratings ~110

No description provided.

NameTypeReqDescription
displaystring––
file_formatstring––

No output schema declared.

No examples provided.

entain_cms_entries ~156

No description provided.

NameTypeReqDescription
content_typestring––
includeinteger––
limitinteger––
orderstring––
skipinteger––

No output schema declared.

No examples provided.

entain_event_market_rules ~46

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

entain_event_market_type_group_maps ~65

No description provided.

NameTypeReqDescription
category_idstringyes–

No output schema declared.

No examples provided.

entain_event_market_type_groups ~62

No description provided.

NameTypeReqDescription
category_idstringyes–

No output schema declared.

No examples provided.

entain_featured_slider ~49

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

entain_graphql_call ~227

No description provided.

NameTypeReqDescription
operationstringyes–
variables–––

No output schema declared.

No examples provided.

entain_metadata_by_url ~60

No description provided.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

entain_quicklinks_list ~97

No description provided.

NameTypeReqDescription
filter–yes–

No output schema declared.

No examples provided.

entain_racing_future_markets ~97

No description provided.

NameTypeReqDescription
exclude–––
methodstring––

No output schema declared.

No examples provided.

entain_racing_meeting ~108

No description provided.

NameTypeReqDescription
datestringyes–
timezonestringyes–

No output schema declared.

No examples provided.

entain_racing_next_races ~84

No description provided.

NameTypeReqDescription
categories–yes–
countintegeryes–

No output schema declared.

No examples provided.

entain_racing_racecard ~145

No description provided.

NameTypeReqDescription
idstringyes–
methodstring––

No output schema declared.

No examples provided.

entain_racing_search ~88

No description provided.

NameTypeReqDescription
category_ids–––
qstring––

No output schema declared.

No examples provided.

entain_sport_event_card ~110

No description provided.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

entain_sport_event_request ~65

No description provided.

NameTypeReqDescription
category_ids–yes–

No output schema declared.

No examples provided.

entain_video_channels ~48

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

entitysport_competitions ~170

No description provided.

NameTypeReqDescription
pagedinteger––
per_pageinteger––
statusstring––

No output schema declared.

No examples provided.

entitysport_match_commentary ~242

No description provided.

NameTypeReqDescription
inningsIdintegeryes–
matchIdintegeryes–

No output schema declared.

No examples provided.

entitysport_match_info ~160

No description provided.

NameTypeReqDescription
matchIdintegeryes–

No output schema declared.

No examples provided.

entitysport_match_scorecard ~220

No description provided.

NameTypeReqDescription
matchIdintegeryes–

No output schema declared.

No examples provided.

entitysport_matches ~273

No description provided.

NameTypeReqDescription
datestring––
pagedinteger––
per_pageinteger––
statusinteger––

No output schema declared.

No examples provided.

espn_cdn_call ~261

No description provided.

NameTypeReqDescription
operationstringyes–
path_params–––
query_params–––

No output schema declared.

No examples provided.

espn_core_call ~276

No description provided.

NameTypeReqDescription
operationstringyes–
path_params–––
query_params–––

No output schema declared.

No examples provided.

espn_game_summary ~179

No description provided.

NameTypeReqDescription
eventstringyes–
leaguestringyes–
sportstringyes–

No output schema declared.

No examples provided.

espn_news ~136

No description provided.

NameTypeReqDescription
leaguestringyes–
limitinteger––
sportstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.DanielTomaro13/sportsdata-mcp server?

io.github.DanielTomaro13/sportsdata-mcp runs locally as a PyPI package, launched with uvx sportsdata-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · sportsdata-mcp

# add to Claude Code
claude mcp add danieltomaro13-sportsdata-mcp -- uvx sportsdata-mcp
Common questions

What is the io.github.DanielTomaro13/sportsdata-mcp server?

io.github.DanielTomaro13/sportsdata-mcp is listed in the public MCP registry as io.github.DanielTomaro13/sportsdata-mcp. Live sports data and cross-book betting odds, 801 tools, 63 providers, 43 needing no key. This page covers its PyPI package (sportsdata-mcp).

Is the io.github.DanielTomaro13/sportsdata-mcp server safe to use?

io.github.DanielTomaro13/sportsdata-mcp scores 52 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.

Is the io.github.DanielTomaro13/sportsdata-mcp server still maintained?

io.github.DanielTomaro13/sportsdata-mcp 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.

What licence is the io.github.DanielTomaro13/sportsdata-mcp server under?

io.github.DanielTomaro13/sportsdata-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.DanielTomaro13/sportsdata-mcp server?

VerifyMCP ran 10 checks on io.github.DanielTomaro13/sportsdata-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 6 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.DanielTomaro13/sportsdata-mcp: Malware scan, Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.