Read-only sports match data and published post-match reviews from SXS, letting an assistant look up recommendations, odds and recaps by date or team.
What you can do
Look up first-layer match data for a betting day: full-time, half-time and handicap recommendation sets, rounded self-computed probabilities and lottery odds
Query by match date or by team name with fuzzy matching, with the date taking priority when both are given
Retrieve already-published post-match reviews from the official site, including links, by date and home/away team names
Receive explicit status values such as ok, no coverage, not published, silent, unauthorized or rate limited
When to use it
Useful when you want an assistant to pull SXS match recommendations, odds and published recaps for a given day or team, for example to review yesterday's picks or check whether a review exists for a specific fixture.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared. The free tier only serves the previous match day; today's data requires authorization, and unauthorized requests are refused by default.
Before you install
Today's data is gated behind authorization and is denied by default without it. The service is read-only and returns data only, but it is betting-related content with recommendations and odds, so treat it as informational rather than advice. Requests are sent to a third-party endpoint.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.sxs-ai%2Fsxs-match-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.