Skip to main content
Glama
qtexuk

racing-alpha-mcp

by qtexuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote
README.md
# Racing Alpha MCP server — shut down

**This server no longer exists.** The Racing Alpha service closed in
October 2026. The remote endpoint at `racingalpha.co.uk/api/mcp` and the
public API it fronted have been switched off, and the official MCP
Registry entry `uk.co.racingalpha/signals` has been removed.

The code in this repository (a small stdio-to-HTTP bridge) is kept for
reference only. It will not work, because the endpoint it connects to is
gone.

Thank you to everyone who built on it.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct question: race lists, per-race signals, tips ledger, draw bias stats, and trainer-jockey combos. There is no functional overlap, making selection unambiguous.

Naming Consistency5/5

All tools follow the same get_<object> pattern (e.g., get_today_races, get_race_signals). The naming is predictable and consistent.

Tool Count5/5

Five tools is a well-scoped size for a horse racing tips-and-stats server. Each tool fills a clear role without redundancy or bloat.

Completeness4/5

The core workflow is covered: browse today's races, drill into signals, check historical tips, and consult statistical context. Minor gaps exist like historical racecards or non-today races, but they don't undermine the primary purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources