SXS Match Data MCP server
com.sxs-ai/sxs-match-datasxs-ai.comstreamable-httpv0.1.0Scanned
SXS (Sports x Science) read-only match data and reviews. Free: previous match day. Data only.
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SXS Match Data MCP server can do
The SXS Match Data MCP server is published by sxs-ai.com, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (get_match_review).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
get_match_data查第一层赛事数据(全场/半场/让球三套推荐、圆整自算概率、竞彩赔率)。 Args: match_date: 竞彩日(YYYY-MM-DD)。免费层只提供**昨日**竞彩日。 team: 球队名(模糊匹配)。与 match_date 二选一;同时传以 match_date 优先。 Returns: status: ok / no_coverage / not_…No findings
Why it is in this group
- The name "get_match_data" says "get": a word for reading.
Description, as the server wrote it 查第一层赛事数据(全场/半场/让球三套推荐、圆整自算概率、竞彩赔率)。 Args: match_date: 竞彩日(YYYY-MM-DD)。免费层只提供**昨日**竞彩日。 team: 球队名(模糊匹配)。与 match_date 二选一;同时传以 match_date 优先。 Returns: status: ok / no_coverage / not_published / silent / unauthorized / rate_limited (今日数据需授权;未授权一律默认拒绝,不返回任何今日场次)
get_match_review检索官网已公开的赛后复盘(只返已公开内容与链接)。 Args: match_date: 比赛日期(YYYY-MM-DD)。 home: 主队名。away: 客队名。Reads text others writeNo findings
Why it is in this group
- The name "get_match_review" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_match_review" says "get" and "review": it reads comments, which other people can write.
Description, as the server wrote it 检索官网已公开的赛后复盘(只返已公开内容与链接)。 Args: match_date: 比赛日期(YYYY-MM-DD)。 home: 主队名。away: 客队名。
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:48 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none.View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Protocol version: 2025-06-18 to none
Tools2 changed.~2 changedView diff
- Changed:get_match_dataOnly readsinputSchema
- Changed:get_match_reviewOnly readsinputSchema
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http sxs-match-data https://mcp.sxs-ai.com/mcpclaude mcp add --transport http sxs-match-data https://mcp.sxs-ai.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__sxs-match-data__get_match_data",
"mcp__sxs-match-data__get_match_review"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sxs-match-data. Review it before you use it.
Capability tags behind 1 rule
- mcp__sxs-match-data__get_match_review untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.sxs-ai/sxs-match-data/verify?hash=6d563200a4eb6df45a07d90f604cadd7e45484e186c897947843a4083e831a55" | jq -e '.changed == false'Pinned hash 6d563200a4eb, from Nov 14, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.sxs-ai/sxs-match-data/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.sxs-ai/sxs-match-data)Source: MCP Registry. Synced Oct 21, 2026, 18:06 UTC.
SXS Match Data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SXS Match Data MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the SXS Match Data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SXS Match Data MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SXS Match Data MCP server have?
- 2 tools: 2 read. get_match_data and get_match_review.
Does the SXS Match Data MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the SXS Match Data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SXS Match Data MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.