LayUp Sports Booking
REMOTE · MCP.LAYUPSPORT.COM
Search bookable London courts, pitches, lanes and pickup games across every major UK provider.
Available components
Last scanned (17 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2430 tokens (~486/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "without warning the user", at byte 3085 of that field. See how to fix → Fail
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Tool “create_alert” rewrote its description, which is the text the model reads security
- “create_alert” added an optional parameter “all_venues_in_area” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- “create_alert” reworded the description of “area” cosmetic
- “search_slots” reworded the description of “area” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.layupsport.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.layupsport.com | CN=YR1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 6864b6ee1f13c65ee1832aa6631bb9c9906 |
| SANs: mcp.layupsport.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.layupsport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| layupsport.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.layupsport.com | Verified | 200 | |
| http (plaintext) | http://mcp.layupsport.com | HTTPS enforced | 308 | https://mcp.layupsport.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_alert ~634
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. NARROW IT FIRST. An alert with no venues attached matches hundreds of slots, so the emails read as a dump rather than an alert: of 20 such alerts, 1 was ever confirmed and 8 died unconfirmed at the send cap. Call this without venue_names and the tool will NOT create an alert — it returns the venues LayUp covers in that area so you can ask the user which ones they want, and prompts for the days and times that suit them. Then call again with their answers. LayUp does the watching; the notification arrives by email, not in this chat.
| Name | Type | Req | Description |
|---|---|---|---|
| all_venues_in_area | boolean | – | Set true ONLY after the user has explicitly said they want every venue in the area rather than a chosen few. Without venue_names the tool refuses and hands you the venue list to offer them — area-wid… |
| area | string | – | Where to watch, resolved geographically: a borough ('Hackney'), a neighbourhood ('Maida Vale'), a region ('North London'), or a postcode ('W9 2RF', 'SE1'). A postcode is the most precise option when… |
| 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. |
| string | yes | 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. |
No output schema declared.
No examples provided.
get_venue ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max slots to return (1-30, default 15). |
| venue_slug | string | yes | The venue_slug from a search_slots result. |
No output schema declared.
No examples provided.
list_sports ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
refine_search ~328
Find out WHERE and WHEN there is availability, before asking the user a clarifying question. Takes the same filters as search_slots and returns counts by area, day, time band and price — not slots. Use it when the request is under-specified ('find me a tennis court', 'somewhere for a group') so the question you ask back is grounded in real supply: ask 'Wandsworth (8 venues) or Richmond (7)?' rather than an open 'which area?'. Also use it when a search returned nothing, to say which nearby area or time DOES have slots instead of reporting a dead end.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional. Same geographic resolution as search_slots — borough, neighbourhood, region, postcode or venue name. Omit to see every area. |
| booking_type | string | – | 'spot', 'court' or '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. |
| max_price | number | – | Maximum price in GBP. |
| min_courts | integer | – | Only count venue-hours with at least this many free at the same time. Same meaning as in search_slots. |
| sport | string | – | One of Football, Tennis, Squash, Padel, Swimming. |
| time_from | string | – | London-local earliest start time of day, 'HH:MM'. |
| time_to | string | – | London-local latest start time of day, 'HH:MM'. |
No output schema declared.
No examples provided.
search_slots ~495
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Where to look. Resolved geographically, so any of these work: a borough ('Hackney'), a neighbourhood ('Shoreditch', 'Maida Vale'), a region ('North London', 'Central London'), a postcode or outward c… |
| 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. |
| min_courts | integer | – | Only return venues with at least this many courts/pitches free AT THE SAME TIME. Use for groups: padel and tennis are 4 per court, so 16 people need 4. Nobody else can answer this — venues cannot see… |
| 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'. |
No output schema declared.
No examples provided.
How do I install the LayUp Sports Booking MCP server?
LayUp Sports Booking is a hosted endpoint at https://mcp.layupsport.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.layupsport.com
claude mcp add --transport http layup-sport-sports-booking 'https://mcp.layupsport.com/'
What is the LayUp Sports Booking MCP server?
LayUp Sports Booking is an MCP server listed in the public MCP registry as io.github.LayUp-Sport/sports-booking. Search bookable London courts, pitches, lanes and pickup games across every major UK provider. This page covers its hosted endpoint (https://mcp.layupsport.com).
Is the LayUp Sports Booking MCP server safe to use?
LayUp Sports Booking scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LayUp Sports Booking MCP server expose?
LayUp Sports Booking exposes 5 tools: search_slots, refine_search, list_sports, get_venue, create_alert. Their descriptions and schemas cost roughly 1,572 tokens of context every time the server is loaded.
Does the LayUp Sports Booking MCP server require authentication?
No. We connected to LayUp Sports Booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LayUp Sports Booking MCP server still maintained?
LayUp Sports Booking is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.