Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
LayUp Sports Booking is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Search bookable London courts, pitches, lanes and pickup games across every major UK provider.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http layup-sports-booking-mcp https://mcp.layupsport.com
# 2 — ask your agent for something these tools do
# search_slots, refine_search, list_sports and 2 more
LayUp Sports Booking costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LSAll 1 server
LayUp-Sport1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http layup-sports-booking-mcp https://mcp.layupsport.comReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sport | string | no | One of Football, Tennis, Squash, Padel, Swimming. |
| area | string | no | 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 co |
| date_from | string | no | ISO date or datetime — earliest start. Defaults to now. |
| date_to | string | no | ISO date or datetime — latest start. Defaults to 7 days out. |
| time_from | string | no | 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 | no | London-local latest start time of day, 'HH:MM'. |
| max_price | number | no | Maximum price in GBP. Published prices above this are removed; unpublished-price slots ('Check App', common for padel/tennis) are kept and flagged. |
| booking_type | string | no | 'spot' = book one place (pickup game / swim seat), 'court' = whole court, 'pitch' = whole pitch. |
| min_courts | integer | no | 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 |
| limit | integer | no | Max results to return (1-30, default 15). |
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)?' rathe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sport | string | no | One of Football, Tennis, Squash, Padel, Swimming. |
| area | string | no | Optional. Same geographic resolution as search_slots — borough, neighbourhood, region, postcode or venue name. Omit to see every area. |
| date_from | string | no | ISO date or datetime — earliest start. Defaults to now. |
| date_to | string | no | ISO date or datetime — latest start. Defaults to 7 days out. |
| time_from | string | no | London-local earliest start time of day, 'HH:MM'. |
| time_to | string | no | London-local latest start time of day, 'HH:MM'. |
| max_price | number | no | Maximum price in GBP. |
| booking_type | string | no | 'spot', 'court' or 'pitch'. |
| min_courts | integer | no | Only count venue-hours with at least this many free at the same time. Same meaning as in search_slots. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| venue_slug | string | yes | The venue_slug from a search_slots result. |
| limit | integer | no | Max slots to return (1-30, default 15). |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. | |
| sport | string | no | One of Football, Tennis, Squash, Padel, Swimming. Omit for any. |
| area | string | no | 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 t |
| venue_names | array | no | 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 ve |
| venue_slugs | array | no | 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. |
| time_from | string | no | Earliest London time-of-day, 'HH:MM' (e.g. '18:00'). |
| time_to | string | no | Latest London time-of-day, 'HH:MM'. |
| days_of_week | array | no | 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. |
| max_price | number | no | Only alert on slots at or under this GBP price. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LayUp Sports Booking or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digeste65f59f2d1cd60165876d1b437bf928bd635f44b374e999670809d3c6527b2af
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_slots | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| refine_search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_sports | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_venue | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_alert | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digeste65f59f2d1cd6016
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LayUp Sports Booking can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.