_ registry / mcp streamable-http · checked 47m ago

layup-sports-booking

https://mcp.layupsport.com

Registry code: e6e8e21ffe37c6d0

api record

LayUp aggregates real-time bookable sports slots across London for five sports: Football, Tennis, Squash, Padel and Swimming. Sources include Better, Everyone Active, Gladstone leisure centres, ClubSpark/LTA, Playtomic, Padel Mates, MATCHi, Footy Addicts and others. Use search_slots to find availability by sport, area, date, time and price (min_courts for a group needing several courts at once); refine_search when the request is vague or a search came back empty — it returns which areas, days and times actually have supply, so a clarifying question can offer real options instead of asking…

endpoint
https://mcp.layupsport.com
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is layup-sports-booking live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is layup-sports-booking free to use?
Yes — the hub reached it with no key and no payment.
What tools does layup-sports-booking have?
5 tools: get_venue, create_alert, list_sports, refine_search, search_slots.
Is layup-sports-booking safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
484ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_sports open 47m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • refine_search open 47m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "area": {
          "type": "string",
          "description": "Optional. Same geographic resolution as search_slots — borough, neighbourhood, region, postcode or venue name. Omit to see every area."
        },
        "sport": {
          "enum": [
            "Football",
            "Tennis",
            "Squash",
            "Padel",
            "Swimming"
          ],
          "type": "string",
          "description": "One of Football, Tennis, Squash, Padel, Swimming."
        },
        "date_to": {
          "type": "string",
          "description": "ISO date or datetime — latest start. Defaults to 7 days out."
        },
        "time_to": {
          "type": "string",
          "description": "London-local latest start time of day, 'HH:MM'."
        },
        "date_from": {
          "type": "string",
          "description": "ISO date or datetime — earliest start. Defaults to now."
        },
        "max_price": {
          "type": "number",
          "description": "Maximum price in GBP."
        },
        "time_from": {
          "type": "string",
          "description": "London-local earliest start time of day, 'HH:MM'."
        },
        "min_courts": {
          "type": "integer",
          "description": "Only count venue-hours with at least this many free at the same time. Same meaning as in search_slots."
        },
        "booking_type": {
          "enum": [
            "spot",
            "court",
            "pitch"
          ],
          "type": "string",
          "description": "'spot', 'court' or 'pitch'."
        }
      },
      "additionalProperties": false
    }
    arguments 54 lines
  • search_slots open 47m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "area": {
          "type": "string",
          "description": "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 code ('W9 2RF', 'SE1'), or a venue name ('Clissold'). Returns venues near the resolved point, not just ones with the word in their name."
        },
        "limit": {
          "type": "integer",
          "description": "Max results to return (1-30, default 15)."
        },
        "sport": {
          "enum": [
            "Football",
            "Tennis",
            "Squash",
            "Padel",
            "Swimming"
          ],
          "type": "string",
          "description": "One of Football, Tennis, Squash, Padel, Swimming."
        },
        "date_to": {
          "type": "string",
          "description": "ISO date or datetime — latest start. Defaults to 7 days out."
        },
        "time_to": {
          "type": "string",
          "description": "London-local latest start time of day, 'HH:MM'."
        },
        "date_from": {
          "type": "string",
          "description": "ISO date or datetime — earliest start. Defaults to now."
        },
        "max_price": {
          "type": "number",
          "description": "Maximum price in GBP. Published prices above this are removed; unpublished-price slots ('Check App', common for padel/tennis) are kept and flagged."
        },
        "time_from": {
          "type": "string",
          "description": "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."
        },
        "min_courts": {
          "type": "integer",
          "description": "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 each other and the booking platforms only see their own sites. Results are one slot per venue; that venue had at least this many free at that hour."
        },
        "booking_type": {
          "enum": [
            "spot",
            "court",
            "pitch"
          ],
          "type": "string",
          "description": "'spot' = book one place (pickup game / swim seat), 'court' = whole court, 'pitch' = whole pitch."
        }
      },
      "additionalProperties": false
    }
    arguments 58 lines
  • get_venue unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "venue_slug"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max slots to return (1-30, default 15)."
        },
        "venue_slug": {
          "type": "string",
          "description": "The venue_slug from a search_slots result."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • create_alert unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "area": {
          "type": "string",
          "description": "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 the user gives one. NOT a venue name — to watch a specific venue use venue_names. Omit for all London."
        },
        "email": {
          "type": "string",
          "description": "The user's REAL email address, as given by them (required — alerts are emailed here). Never invent, guess or substitute a placeholder like [email protected]; if you don't have it, ask the user first."
        },
        "sport": {
          "enum": [
            "Football",
            "Tennis",
            "Squash",
            "Padel",
            "Swimming"
          ],
          "type": "string",
          "description": "One of Football, Tennis, Squash, Padel, Swimming. Omit for any."
        },
        "time_to": {
          "type": "string",
          "description": "Latest London time-of-day, 'HH:MM'."
        },
        "max_price": {
          "type": "number",
          "description": "Only alert on slots at or under this GBP price."
        },
        "time_from": {
          "type": "string",
          "description": "Earliest London time-of-day, 'HH:MM' (e.g. '18:00')."
        },
        "venue_names": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "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 venue(s). Prefer this over venue_slugs."
        },
        "venue_slugs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "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."
        },
        "days_of_week": {
          "type": "array",
          "items": {
            "enum": [
              "Mon",
              "Tue",
              "Wed",
              "Thu",
              "Fri",
              "Sat",
              "Sun"
            ],
            "type": "string"
          },
          "description": "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."
        },
        "all_venues_in_area": {
          "type": "boolean",
          "description": "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-wide alerts match hundreds of slots, are never confirmed and lapse unused."
        }
      },
      "additionalProperties": false
    }
    arguments 74 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e6e8e21ffe37c6d0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e6e8e21ffe37c6d0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e6e8e21ffe37c6d0/badge.svg)](https://brick.blue/agent/e6e8e21ffe37c6d0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.