# LayUp Sports Booking (remote · mcp.layupsport.com)

Search bookable London courts, pitches, lanes and pickup games across every major UK provider.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.layupsport.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/layup-sport-sports-booking/mcp.md), [page](https://verifymcp.io/servers/layup-sport-sports-booking/mcp)

## Channel facts

- Endpoint: `https://mcp.layupsport.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1724 tokens (~431/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http layup-sport-sports-booking https://mcp.layupsport.com/
```

### Codex

```toml
[mcp_servers.layup-sport-sports-booking]
url = "https://mcp.layupsport.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "layup-sport-sports-booking": {
      "type": "remote",
      "url": "https://mcp.layupsport.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add layup-sport-sports-booking --url https://mcp.layupsport.com/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  layup-sport-sports-booking:
    url: "https://mcp.layupsport.com/"
```

### Other

```json
{
  "mcpServers": {
    "layup-sport-sports-booking": {
      "type": "http",
      "url": "https://mcp.layupsport.com/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (4)

### `search_slots` (~350 tokens)

Search bookable sports slots in London across every provider LayUp aggregates. Use when a user wants to find a court, pitch, lane, class or pickup game for football, tennis, squash, padel or swimming. Filter by sport, area/borough, date range, time of day and max price. Returns upcoming slots with venue, London-local time, price, provider and a booking link. Times default to the next 7 days.

Input parameters:

- `area` (string): London borough, area or venue name to match (e.g. 'Hackney', 'Southwark', 'Clissold').
- `booking_type` (string): 'spot' = book one place (pickup game / swim seat), 'court' = whole court, 'pitch' = whole pitch.
- `date_from` (string): ISO date or datetime — earliest start. Defaults to now.
- `date_to` (string): ISO date or datetime — latest start. Defaults to 7 days out.
- `limit` (integer): Max results to return (1-30, default 15).
- `max_price` (number): Maximum price in GBP. Published prices above this are removed; unpublished-price slots ('Check App', common for padel/tennis) are kept and flagged.
- `sport` (string): One of Football, Tennis, Squash, Padel, Swimming.
- `time_from` (string): London-local earliest start time of day, 'HH:MM' (e.g. '18:00'). Samples the soonest upcoming slots; combine with date_from to target a specific day.
- `time_to` (string): London-local latest start time of day, 'HH:MM'.

### `list_sports` (~39 tokens)

List the sports LayUp covers with a count of slots available in the next 7 days. Useful as a quick overview before a more specific search.

### `get_venue` (~76 tokens)

List upcoming bookable slots at a single venue, identified by its venue_slug (as returned by search_slots). Use to drill into one venue after a search.

Input parameters:

- `limit` (integer): Max slots to return (1-30, default 15).
- `venue_slug` (string, required): The venue_slug from a search_slots result.

### `create_alert` (~461 tokens)

Set up an email alert for the user: LayUp watches for NEW matching slots (e.g. a cancellation freeing up a peak court) and emails them when one appears. Use when the user can't find a slot now and wants to be notified, or asks to 'monitor'/'watch'/'let me know when'. Requires their email. A confirmation email is sent first — the user must click confirm before any alerts fire (so always tell them to check their inbox). LayUp does the watching; the notification arrives by email, not in this chat.

Input parameters:

- `area` (string): London borough / area / neighbourhood to match (e.g. 'Hackney', 'Maida Vale'). NOT a venue name — to watch a specific venue use venue_names. Omit for all London.
- `days_of_week` (array): Only alert on these days (e.g. ['Sat','Sun'] for weekends). The alert is standing — it keeps watching these days every week until the user unsubscribes. Omit for any day.
- `email` (string, required): The user's REAL email address, as given by them (required — alerts are emailed here). Never invent, guess or substitute a placeholder like user@example.com; if you don't have it, ask the user first.
- `max_price` (number): Only alert on slots at or under this GBP price.
- `sport` (string): One of Football, Tennis, Squash, Padel, Swimming. Omit for any.
- `time_from` (string): Earliest London time-of-day, 'HH:MM' (e.g. '18:00').
- `time_to` (string): Latest London time-of-day, 'HH:MM'.
- `venue_names` (array): Pin the alert to specific venues BY NAME, exactly as shown in search results (e.g. ["Hay's Galleria", "Padel Box"]). Use this whenever the user names venues — the server resolves names to the right v…
- `venue_slugs` (array): Pin the alert to specific venues by their exact venue_slug (only if you already have slug values from search_slots). For most cases use venue_names instead. Omit for any venue.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/layup-sport-sports-booking/mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 61
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.layupsport.com/
- Repository: https://github.com/LayUp-Sport/layup-frontend
- Website: https://www.layupsport.com/
- Changelog RSS feed: https://verifymcp.io/servers/layup-sport-sports-booking/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/layup-sport-sports-booking/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/layup-sport-sports-booking/mcp