Soccer LiveScore Radar

Problem

Football lookups often span disconnected sources: live scores, fixtures, team and player data, head-to-head history, transfer news, and match predictions. Manually collecting and formatting these fields is slow and error-prone. Soccer LiveScore Radar wraps LiveScore MCP football endpoints into a consistent workflow for querying structured football information in chat.

How It Works

After ensuring the livescore MCP connector is available, the skill uses tools such as search, get_live_scores, get_day_fixtures, get_match, get_team, and get_player to fetch data. Common queries are rendered as Markdown tables in Chinese, covering:

• Live scores with team names, goal status, and match progress
• Fixtures and match details grouped by competition, labelled with Beijing time, event timelines, statistics, and H2H
• Team/player profiles including squads, season stats, position, height/weight, career history, and other fields
• Match predictions generated by the built-in predict.py using weighted factors such as recent form, head-to-head record, team strength, squad depth, and home advantage

Transfer information is fetched from designated external sources and formatted into incoming/outgoing tables. Preferred team settings can be stored in profile.json for recent and upcoming fixture lookups.

Boundaries

The skill depends on the MCP connection and network access. When a 429 rate-limit occurs, it should pause rather than retry automatically. LiveScore does not provide a native standings API, so standings must be reconstructed from fixture results. Transfer fees and news depend on accessible external sources, and obscure translations may remain in English with a confirmation note.