track-live-scores▌
livescore.com/track-live-scores-txxdp5 · updated May 21, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Track every in-play soccer match on LiveScore via the public JSON API — for each live match return competition, home/away teams, current and half-time scores, elapsed minute, match phase, kickoff time, and canonical match URL. Browser fallback documented for the rare case the API misbehaves.
| name | track-live-scores |
| title | LiveScore Live Soccer Score Tracker |
| description | >- Track every in-play soccer match on LiveScore via the public JSON API — for each live match return competition, home/away teams, current and half-time scores, elapsed minute, match phase, kickoff time, and canonical match URL. Browser fallback documented for the rare case the API misbehaves. |
| website | livescore.com |
| category | sports |
| tags | - sports - soccer - football - live-scores - read-only - json-api |
| source | 'browserbase: agent-runtime 2026-05-20' |
| updated | '2026-05-20' |
| recommended_method | api |
| alternative_methods | - method: browser rationale: >- Browser fallback: open https://www.livescore.com/en/football/live/ in a Browserbase session and text-extract the rendered list. ~50x slower than the JSON API because the page is fully JS-rendered with no inline score data; use only if the API returns 4xx/5xx (not observed during testing). |
| verified | true |
| proxies | true |
LiveScore Live Soccer Score Tracker
Purpose
Track currently-live soccer (football) matches on LiveScore.com — for every match in play right now, return competition, country, home and away teams (name + abbreviation + team ID), current score, half-time score, elapsed-minute string ("34'", "HT", "90+1'"), match phase (1st half / HT / 2nd half / FT / AP), scheduled kickoff time, and the canonical livescore.com match URL. Read-only — never opens or interacts with sportsbook / betting links.
When to Use
- "What soccer games are live right now?" — pure live-only feed.
- Polling-driven score notifications (cache TTL is 10 s — fine for ≥ 15 s polls).
- Building a multi-match live dashboard (Europa League + domestic leagues + lower divisions surface together).
- As a higher-fidelity supplement to the on-screen UI when you also need per-match incidents (goals, cards, subs) via the per-event scoreboard/incidents endpoints.
- Filtering live results to a specific league, country, or team — the response is already grouped by
Stages[](competition).
Workflow
LiveScore's web UI is a thin client over a public JSON API at prod-cdn-mev-api.livescore.com. The endpoint is unauthenticated, no cookies, no CSRF token, no signing, and serves CORS responses keyed to https://www.livescore.com — but the server does not enforce Origin or Referer (we verified 200 OK from browse cloud fetch with neither header). A residential proxy is not required. Lead with the API. The browser path works as a fallback but pays a ~50× cost premium because the live page is JS-rendered (the HTML body served by /en/football/live/ contains no inline score data — the React app hydrates from the same API call after load).
Recommended path — direct API
-
List currently-live soccer matches:
GET https://prod-cdn-mev-api.livescore.com/v1/api/app/live/soccer/{tzOffsetHours}?countryCode={CC}&locale=entzOffsetHours— integer hour offset from UTC, e.g.-7(US Pacific),0(UTC),5,+1. Controls the "today" boundary used by the server when deciding which matches belong to the current calendar day for the caller. For a pure live feed (no boundary effect) any value works; pick the user's local offset for safety.countryCode— ISO 3166-1 alpha-2 (e.g.US,GB,DE). Controls TV-channelallowedCountriesfiltering inside theMedia[]array; does not filter which matches appear. Pass the user's country if you care about media broadcast hints, otherwiseUSis a safe default.locale— language for team/league display strings (en,es,de, ...). Always include — omitting still returnsenbut the server occasionally returnsSnm/Cnmblank without it.
Returns:
{ "Ts": 1779305661, "Stages": [ { /* competition */ "Events": [ /* matches */ ] } ] }Tsis the snapshot epoch in seconds.Stagesis empty when no soccer match anywhere in the world is currently in play (rare — soccer is essentially 24/7 across the global fixture list; expect ≥ 1 stage during normal hours). -
Decode each Stage (one per competition appearing in the live feed):
Sid— stage id.Snm— display name of the stage (e.g."Eliteserien","Final","Serie B: Promotion: Play-off"). For tournaments mid-flight,Snmmay be the round name ("Final","Semi-finals"); the league/cup display name isCnm+CompN.Cnm/Csnm— country display name (e.g."Norway","Saudi Arabia","Europa League"for UEFA competitions whereCnmdoubles as the competition).Ccd— country slug used in URLs ("saudi-arabia","norway","europa-league","north-macedonia"→ note URL uses"macedonia"for this one, see gotchas).Scd— stage slug used in URLs ("eliteserien","premier-league","saudi-professional-league").CompId/CompN/CompUrlName— globally-stable competition id, full competition name, and competition URL slug. Prefer these overSid/Snmwhen grouping/de-duplicating across iterations.badgeUrl,firstColor— branding hints. Badge full URL:https://lsm-static-prod.livescore.com/medium/{badgeUrl}.
-
Decode each Event (one per live match):
Eid— event id (use this for the per-match scoreboard/incidents calls in step 4).T1[0]/T2[0]— home and away team. Fields:ID(team id),Nm(display name),Abr(3-letter abbrev),Img(badge path — full URL:https://lsm-static-prod.livescore.com/medium/{Img}),Fc/Sc(primary/secondary hex color, no#).Tr1/Tr2— current score (string-encoded integers —"1","3"; cast before use).Trh1/Trh2— half-time score (snapshot when match was at HT; equalsTr1/Tr2during 1st half).Tr1OR/Tr2OR— score at end of regulation (90 min). Diverges fromTr1/Tr2only for matches with extra time / penalties.Eps— elapsed period string."34'"mid-half,"HT"at half-time,"90+1'"injury time,"FT"full-time,"AP"after penalties. Use this directly for human display.Esid— event status id (integer enum, see "Site-Specific Gotchas"). For the/live/endpoint expect only2/3/10/13(any in-play state). Matches that finish during the response's cache TTL may briefly appear withEsid=6(FT).Epr— phase:0upcoming,1in-play,2finished. The/live/endpoint generally only returnsEpr=1.Esd— scheduled start packed as decimalYYYYMMDDHHMMSSin UTC (e.g.20260520120000= 2026-05-20 12:00:00 UTC). Parse with a regex split orString.match(/^(\d{4})(\d{2})(\d{2})(\d{2})(\d{2})(\d{2})$/).Etm.ATm— actual kickoff timestamp in milliseconds (epoch). Use this for "match has been running for X minutes" calculations; do not rely onEpsfor sub-minute precision.Etm.RTm— running-time-since-kickoff in milliseconds (server's count, includes added time but not the HT break).seriesInfo— present on two-legged ties (e.g. Champions League knockout, Serie B promotion play-offs). Fields:totalLegs,currentLeg,aggScoreTeam1,aggScoreTeam2. Surface this when present — agents that only look atTr1/Tr2will misreport aggregate context.Shck(boolean) — "score has changed since last snapshot" flag. Useful for polling diffs.Media— broadcast hints. Sub-keys are provider IDs ("112"= TV channels,"29"= audio commentary,"33"= liveactions widget). Each item hasallowedCountries/deniedCountries.
-
Per-match deeper detail (optional, when surfacing one specific match):
GET https://prod-cdn-public-api.livescore.com/v1/api/app/scoreboard/soccer/{Eid}?locale=en GET https://prod-cdn-public-api.livescore.com/v1/api/app/incidents/soccer/{Eid}?locale=enscoreboardreturns a single Event object with the same shape as step 3, plusVenue,LuUT(last-updated timestamp),Eact(active-state flags), andIncs-s(summarized incidents — goals only).incidentsreturns the full event timeline keyed by team number:Incs: { "1": [...home incidents...], "2": [...away incidents...] }. Each incident hasMin(minute),Pn(player display name),Pnt(player URL slug),Aid(player id),IT(incident type, see Gotchas),Sor(sort order). -
Construct the canonical match URL when surfacing a result:
https://www.livescore.com/en/football/{Ccd}/{Scd}/{slug(T1.Nm)}-vs-{slug(T2.Nm)}/{Eid}/Where
slug(x)isx.toLowerCase().replace(/[^a-z0-9]+/g, '-')(verified against captured URLs — e.g.Freiburg→freiburg,Aston Villa→aston-villa,Al Khaleej→al-khaleej). The{Eid}/{trailing slash}is mandatory — omitting either segment 404s.
Browser fallback
If the API returns 4xx/5xx (we observed no anti-bot blocking during ~5 minutes of testing, but as a contingency):
sid=$(browse cloud sessions create --keep-alive --proxies --verified \
| node -e "let s='';process.stdin.on('data',c=>s+=c).on('end',()=>process.stdout.write(JSON.parse(s).id))")
export BROWSE_SESSION="$sid"
browse open "https://www.livescore.com/en/football/live/" --remote
browse wait load --remote
browse get text --remote
The page is fully JS-rendered. browse snapshot returns refs but the live-match list is in a virtual-scroller — browse get text is the simplest extraction. The DOM exposes per-match elements with class names like Eh/bb/db (auto-generated, may shift between deploys); the text-flow order matches the API's stage → events grouping. Don't waste turns trying to find a stable CSS selector — fall back to regex-splitting the text by stage name. Cost: ~10-30s for the full page render plus extraction parsing, vs. ~0.5s for the API.
Site-Specific Gotchas
Esidenum — integer event-status code. Observed values from production data:1= Not Started (NS),2= 1st Half (in-play),3= 2nd Half (in-play),6= Full Time (FT),10= Half Time (HT),13= After Penalties (AP). The/live/endpoint only returnsEsid ∈ {2, 3, 10, 13}(plus occasionally6for matches that finished within the last cache TTL window). Other values likely exist for extra time, postponements, abandonments — not directly observed.Epr≠Esid—Epris a coarser 3-value phase (0upcoming /1live /2finished). UseEprwhen you only need live/finished classification; useEsidfor the specific period.Tr*fields are strings, not numbers —"Tr1":"1","Tr2":"3". Cast withparseIntorNumber()before arithmetic. Free / 0-0 matches use"0", not the empty string.Esdis packed decimal in UTC, not ISO 8601 —20260520120000means 2026-05-20T12:00:00Z. Parsing this as a plain integer or naiveDateconstructor (which interprets as local time) silently shifts kickoff times by the local offset. Use an explicit regex parse toDate.UTC().Etm.ATmis milliseconds,Tsis seconds. The top-level snapshot timestampTsis in seconds, but inside each eventEtm.ATm(actual kickoff) andEtm.RTm(running time) are in milliseconds. Mixing the units in a "match age" calculation produces wildly wrong numbers — always reconcile (Ts * 1000 - Etm.ATm).- Country-slug ≠ country-name slug for two countries.
Cnm="North Macedonia"hasCcd="macedonia"(no "north-" prefix in the URL slug).Cnm="Bosnia and Herzegovina"typically resolves toCcd="bosnia-herzegovina". Don't rederive the URL slug from the display name — always pullCcdandScddirectly from the API response. Cnmdoubles as competition for UEFA tournaments. For Champions League / Europa League / Conference League,Cnmis the competition name ("Europa League") andSnmis the round ("Final","Quarter-finals"). For domestic leagues,Cnmis the country ("Saudi Arabia","Italy") andSnm/CompNis the league. If you need a uniform "competition name" field, preferCompN(always set when defined; falls back toSnmfor non-UEFA cup ties without aCompN).- Detail URL pattern is
/en/football/{Ccd}/{Scd}/{slug}/{Eid}/, NOT/en/football/{Scd}/{slug}/{Eid}/. The country segment is mandatory between sport and league. We verified that omitting it (/en/football/europa-league/freiburg-vs-aston-villa/1746767/) returns a 404; the correct URL puts the UEFA "country" in:/en/football/europe/europa-league/freiburg-vs-aston-villa/1746767/. The trailing slash is also mandatory. - Cache TTL = 10 s (
Cache-Control: max-age=10, public). Polling faster than every ~10 s wastes calls — the CDN returns the sameX-Cache-Status: HITbody until TTL expires. Hits are also cached per(path, tzOffset, countryCode, locale)tuple — varyingtzOffsetbusts the cache uselessly. /live/soccer/0and/live/soccer/-7return the same matches. The timezone offset only affects the date-grouping boundary, not the live filter. Vary it only when calling the per-day endpoint (/date/soccer/YYYYMMDD/{tz}).Snmmay be the value"Final"literally — not "finished", but "the Final round" (e.g.Sid=25365 Snm="Final" Cnm="Europa League"is the actual UEL Final fixture). Don't mistake this for a finished-match flag. UseEsid/Epr/Epsfor match status.- Two-legged tie aggregate score is in
seriesInfo, NOTTr1/Tr2.Tr1/Tr2is always the score of the current leg only. Surfacing "Catanzaro 3-1 on aggregate" requires checkingseriesInfo.aggScoreTeam1/aggScoreTeam2. Absent for single-leg matches. browse get texton the live page returns a "Your browser is out of date" warning string in the markup even when the browser is current. It's a noscript-fallback sentence that the React app does not visibly render. Ignore lines matching/browser is.*out of date/when text-parsing the fallback.- The legacy domain
livescores.com(with trailings) is referenced in the noscript fallback for older browsers — it is a separate, much sparser product and does not serve the JSON API. Do not redirect there. - No
--proxiesor--verifiedneeded for the JSON API. Verified viabrowse cloud fetch(default proxy-less path) returningstatusCode: 200with full payload, no captcha, no Akamai. The browser fallback may benefit from--verifiedon aggressive polling, but for one-shot reads a bare session is fine. - Field
Pidsmaps provider IDs to that provider's match ID. Useful for cross-referencing — e.g.Pids["8"]is the LiveScore canonical id (=Eid),Pids["112"]is the SBTE/sportsbook ID,Pids["33"]is the Stats Perform/Opta ID. Most agents only needEid.
Expected Output
The API returns the full Stages → Events tree. The recommended downstream shape (one flat record per live match) is:
{
"snapshot_ts": 1779305661,
"matches": [
{
"event_id": "1746767",
"competition": {
"name": "Europa League",
"round": "Final",
"country": "Europa League",
"country_slug": "europa-league",
"stage_slug": "final",
"competition_id": "36",
"badge_url": "https://lsm-static-prod.livescore.com/medium/europa-league-2024.png"
},
"home": { "id": "365", "name": "Freiburg", "abbr": "SCF", "badge_url": "https://lsm-static-prod.livescore.com/medium/enet/8358.png" },
"away": { "id": "3863", "name": "Aston Villa", "abbr": "AVL", "badge_url": "https://lsm-static-prod.livescore.com/medium/teambadge/aston-villa-2024.png" },
"score": { "home": 0, "away": 0 },
"half_time_score": { "home": 0, "away": 0 },
"regulation_score": { "home": 0, "away": 0 },
"aggregate_score": null,
"period_label": "34'",
"period_status": "2nd_half",
"esid": 2,
"epr": 1,
"kickoff_utc": "2026-05-20T12:00:00Z",
"kickoff_ms": 1779305616262,
"running_time_ms": 1980000,
"match_url": "https://www.livescore.com/en/football/europa-league/europa-league/freiburg-vs-aston-villa/1746767/",
"score_changed_since_last_snapshot": false
},
{
"event_id": "1776155",
"competition": {
"name": "Serie B",
"round": "Promotion Play-offs - Semi-finals",
"country": "Italy",
"country_slug": "italy",
"stage_slug": "serie-b-promotion-play-off",
"competition_id": "110"
},
"home": { "id": "11873", "name": "Palermo", "abbr": "PAL" },
"away": { "id": "4073", "name": "Catanzaro", "abbr": "CAT" },
"score": { "home": 1, "away": 0 },
"half_time_score": { "home": 1, "away": 0 },
"regulation_score": { "home": 1, "away": 0 },
"aggregate_score": { "home": 1, "away": 3, "current_leg": 2, "total_legs": 2 },
"period_label": "69'",
"period_status": "2nd_half",
"esid": 3,
"epr": 1,
"kickoff_utc": "2026-05-20T11:00:00Z",
"match_url": "https://www.livescore.com/en/football/italy/serie-b-promotion-play-off/palermo-vs-catanzaro/1776155/"
},
{
"event_id": "1777644",
"competition": { "name": "Serie C", "round": "Promotion Play-offs - 4th Round", "country": "Italy", "country_slug": "italy", "stage_slug": "serie-c-promotion-play-off" },
"home": { "id": "4042", "name": "Catania", "abbr": "CAT" },
"away": { "id": "4283", "name": "Lecco", "abbr": "LEC" },
"score": { "home": 2, "away": 2 },
"half_time_score": { "home": 2, "away": 2 },
"aggregate_score": { "home": 2, "away": 2, "current_leg": 2, "total_legs": 2 },
"period_label": "HT",
"period_status": "half_time",
"esid": 10,
"epr": 1
}
]
}
period_status mapping (derive from esid):
esid | period_status | Description |
|---|---|---|
| 1 | not_started | Pre-match (only on /date/) |
| 2 | first_half | In-play, 1st half |
| 3 | second_half | In-play, 2nd half |
| 6 | full_time | Finished after 90 min |
| 10 | half_time | In the HT break |
| 13 | after_penalties | Finished via shootout |
If Stages[] is empty (no live matches anywhere in the world — extremely rare for soccer, but plausible during the early-morning UTC lull):
{ "snapshot_ts": 1779305661, "matches": [] }
How to use track-live-scores on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add track-live-scores
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches track-live-scores from GitHub repository livescore.com/track-live-scores-txxdp5 and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate track-live-scores. Access the skill through slash commands (e.g., /track-live-scores) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★73 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
track-live-scores fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kaira Srinivasan· Dec 24, 2024
Keeps context tight: track-live-scores is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kiara Bhatia· Dec 12, 2024
track-live-scores has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aisha Flores· Dec 4, 2024
Useful defaults in track-live-scores — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Tariq Yang· Nov 23, 2024
track-live-scores has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Xiao Zhang· Nov 23, 2024
track-live-scores fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hassan Menon· Nov 19, 2024
Keeps context tight: track-live-scores is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Advait Ramirez· Nov 15, 2024
Registry listing for track-live-scores matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kaira Zhang· Nov 3, 2024
Useful defaults in track-live-scores — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kaira Huang· Oct 22, 2024
I recommend track-live-scores for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 73