travmaskinen-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@travmaskinen-mcp Which horse in tonight's V64 is the biggest overlay?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Travmaskinen MCP — Nordic harness racing data for AI agents
The first MCP server for Nordic harness racing (trav). Gives Claude, ChatGPT and any MCP-compatible agent direct access to Swedish, Norwegian, Danish and Finnish trotting data: upcoming pool games, full startlists, how the betting public is splitting the pool, and a model-derived win probability for every runner.
Built on a dataset of 204 000 races and 2.06 million starts since 2012.
What your agent can do with it
"What's running in the V85 this Saturday?"
"In tonight's V64, which horses does the model rate higher than the betting public does?"
"Build me a table of every runner in leg 3 with driver, trainer and win probability."
"Which horse in this round is the biggest overlay?"
Related MCP server: iddaa-mcp
Install
// Claude Desktop: claude_desktop_config.json
{
"mcpServers": {
"travmaskinen": {
"command": "npx",
"args": ["-y", "travmaskinen-mcp"],
"env": { "TRAVMASKINEN_API_KEY": "your-key" }
}
}
}Works with any MCP client — Claude Desktop, Claude Code, Cursor, Windsurf, VS Code.
Getting a key
The data is a paid product. Request a key at https://travmaskinen.se/api-access.
The server loads without a key and every tool will tell you how to get one, so you can install first and decide after.
Tools
list_upcoming_races
Upcoming Nordic pool games — V85, V86, V64, V65, GS75 — with track, first start
time and leg count. Returns the game_id needed by the other tool.
Argument | Type | Default | Notes |
| integer 1–14 |
| How many days ahead to look |
Gallop races are excluded: the model is trained on trotting only, and returning probabilities for a sport it never learned would be quietly wrong rather than obviously missing.
get_race_analysis
One full round: every leg, every runner.
Field | Meaning |
| Who is running |
| Share of the betting pool on this horse — what the crowd thinks |
| Win probability, 0–1. Sums to 1 per leg across live runners |
|
|
| Model probability ÷ market probability. > 1 = underbet |
| Non-runner. Probability fields are |
Every response also carries a field_reference explaining each field inline, so an
agent never has to guess what a number means.
Rate limits
1 000 calls/month and 60 calls/minute on the standard key. The tools return a clear message rather than a raw HTTP error when either is hit.
Configuration
Variable | Required | Purpose |
| yes | Your API key |
| no | Override the base URL (testing) |
Notes
Data covers Nordic harness racing (trot), not thoroughbred flat racing. If you need UK or US thoroughbred data, this is the wrong server — and if you need Nordic trot, as far as we know this is the only one.
Times are Europe/Stockholm. Probabilities are model output, not betting advice.
MIT licensed. The data behind it is a commercial product; see the terms at https://travmaskinen.se/api-access.
Available Tools
7 toolsget_driver_statisticsCareer statistics for a driverA
Career record for one driver (kusk): starts, wins, win percentage and strongest tracks. Requires the statistics product.
Inputs: driver_id (required).
get_horse_statisticsCareer statistics for a horseA
Full career record for one horse: starts, wins, placings, earnings, form trend, personal records and performance by track and distance. Data goes back to 2012. Requires the statistics product.
Inputs: horse_id (required).
get_race_analysisGet full analysis for one race roundA
Every leg and every runner in one pool game: horse, driver, trainer, the share of the betting pool on each horse (pool_pct), and Travmaskinen’s own win probability (pool_blend_prob) with implied odds and a value score. A value above 1 means the model rates the horse higher than the betting public does. Scratched horses are flagged and carry null probabilities.
Inputs: game_id (required).
get_track_statisticsStatistics for a racetrackA
Statistics for one Nordic track: typical field sizes, distances raced and how post position affects winning there. Requires the statistics product.
Inputs: track_code (required).
get_trainer_statisticsCareer statistics for a trainerA
Career record for one trainer (tränare): starts, wins, win percentage and stable performance. Requires the statistics product.
Inputs: trainer_id (required).
list_upcoming_racesList upcoming Nordic harness racesA
Upcoming Nordic (Swedish, Norwegian, Danish, Finnish) harness racing pool games — V85, V86, V64, V65, GS75 — with track, first start time and number of legs. Returns a game_id for use with get_race_analysis. Gallop races are excluded. Requires a Travmaskinen API key (https://travmaskinen.se/api-access).
Inputs: days.
search_horsesFind a horse by nameA
Search Nordic harness racing horses by name fragment and return their ids, for use with get_horse_statistics. Requires the statistics product.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: race games, race analysis, horse search/statistics, driver statistics, trainer statistics, and track statistics. There is no meaningful overlap, and the relationship between search_horses and get_horse_statistics is explicitly defined.
Tool names consistently follow a verb_noun pattern, with most using get_ for statistics retrieval and clear action verbs like search_ and list_ for the other operations. The naming is predictable and makes the purpose of each tool immediately understandable.
Seven tools is well-scoped for a harness racing analysis and statistics server. Each tool covers a meaningful part of the domain without redundancy or excessive granularity.
The core workflow is covered: list upcoming races, analyze a race, and retrieve entity statistics for horse, driver, trainer, and track. Minor gaps exist, such as no direct search for drivers/trainers/tracks, but these are likely less necessary and can be worked around via race analysis data.
Maintenance
Related MCP Connectors
Official Intrinio MCP server. US stock prices, options and fundamentals for AI agents.
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
Hosted MCP server for live public-data APIs and Skills for AI agents.
Historical tick, order book and settlement data for Polymarket and Predict.fun crypto up/down markets, plus smart-money lists and backtest quotes, over a read-only MCP server.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP-compatible server that gives AI agents access to alternative sports data across 30+ leagues — odds, events, probabilities, settlement, and futures for prediction markets, DFS platforms, and sportsbooks.2918 PyPIMIT
- AlicenseBqualityDmaintenanceMCP server that provides structured access to real-time sportsbook data from iddaa, including live events, competitions, and league fixtures with strategy analysis. Designed for AI agents and automation workflows.550 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying and optionally trading across prediction markets (Polymarket, Kalshi, Limitless, Manifold) through a unified API.31MIT
- FlicenseAqualityDmaintenanceMCP server for motorsport event documents, enabling AI agents to search, read, compare amendments, and parse schedules via typed tools.9-