Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gaplessly Booking

REMOTE · GAPLESSLY.COM

Find free times at Gaplessly businesses on a plan with AI booking, then get a link to book.

Available components

0 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2919 tokens (~486/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +60
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 20 Nov 26 −60
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 +5
    • Stability: fail → pass ▲ security
  • 2 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_appointment_times” rewrote its description, which is the text the model reads security
    • Tool “find_table_times” rewrote its description, which is the text the model reads security
    • Tool “get_venue” rewrote its description, which is the text the model reads security
    • Schema quality: 356 → 486 ▼ functional
    • Server version: 1.1.0 → 1.2.0 functional
    • New tool “find_venues” functional
    • “find_appointment_times” added an optional parameter “maxPerDay” cosmetic
    • “find_appointment_times” added an optional parameter “near” cosmetic
    • “find_appointment_times” added an optional parameter “notAfter” cosmetic
    • “find_appointment_times” added an optional parameter “notBefore” cosmetic
    • “find_appointment_times” added an optional parameter “partOfDay” cosmetic
    • “find_appointment_times” added an optional parameter “slug” cosmetic
    • “find_table_times” added an optional parameter “maxPerDay” cosmetic
    • “find_table_times” added an optional parameter “near” cosmetic
    • “find_table_times” added an optional parameter “notAfter” cosmetic
    • “find_table_times” added an optional parameter “notBefore” cosmetic
    • “find_table_times” added an optional parameter “partOfDay” cosmetic
    • “find_table_times” added an optional parameter “slug” cosmetic
    • “get_venue” added an optional parameter “slug” cosmetic
    • “start_appointment_booking” added an optional parameter “slug” cosmetic
    • “start_table_booking” added an optional parameter “slug” cosmetic
    • “find_appointment_times” reworded the description of “venue” cosmetic
    • “find_table_times” reworded the description of “venue” cosmetic
    • “get_venue” reworded the description of “venue” cosmetic
    • “start_appointment_booking” reworded the description of “venue” cosmetic
    • “start_table_booking” reworded the description of “venue” cosmetic
    • “find_appointment_times” made “venue” optional cosmetic
    • “find_table_times” made “venue” optional cosmetic
    • “get_venue” made “venue” optional cosmetic
    • “start_appointment_booking” made “venue” optional cosmetic
    • “start_table_booking” made “venue” optional cosmetic
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.

Diagnostics

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 21 Nov 2026 · Probed https://gaplessly.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.gaplessly.com CN=YR1,O=Let's Encrypt,C=US 5 Nov 2026 3 Feb 2027 RSA 2048 SHA256-RSA 5744151843ea1dc683af631aa8f114fd4e2
SANs: *.gaplessly.com, gaplessly.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 gaplessly.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
gaplessly.com. No DS 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=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gaplessly.com/api/mcp Verified 200
http (plaintext) http://gaplessly.com/api/mcp HTTPS enforced 308 https://gaplessly.com/api/mcp
MCP tools · 6 exposed · ~2,430 tokens

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 →

Tool Tokens
find_appointment_times ~618

Free appointment times at one venue for one service, over up to two weeks. For salons, clinics, studios and anywhere a guest books a named service with a provider. Use find_table_times for a restaurant instead. Needs a service id from get_venue. Each returned time has an `at` label to show the guest and a `slotToken`. The token is the booking handle: it is signed, it expires in about 30 minutes, and it is the only way a time can be booked later. Pass it back exactly as given, never edited, and never reuse one from a different venue. An empty `times` array for a day means that day is genuinely unavailable, not that something failed. Each day lists at most 10 times unless `maxPerDay` says otherwise, spread across the day; `omitted` says how many more exist. To answer "around 6pm" or "afternoons", send `near`, `partOfDay`, `notBefore` or `notAfter` instead of asking for everything.

NameTypeReqDescription
daysinteger–How many consecutive days to search from that day, 1 to 14. Defaults to 3.
fromstring–Which day to start from: the word "today", the word "tomorrow", or an exact calendar date as YYYY-MM-DD. Resolved against the venue's own current date, which is often not yours. Do not send a phrase…
maxPerDayinteger–Most times to return per day, 1 to 40. Defaults to 10. Past it, the times are spread across the day (or nearest `near`) and `omitted` says how many were left out.
nearstring–A 24 hour time as HH:MM, for example 19:00 for 7pm. When a day has more times than maxPerDay, keep the ones closest to this.
notAfterstring–Drop times later than this 24 hour HH:MM.
notBeforestring–Drop times earlier than this 24 hour HH:MM.
partOfDaystring–Only times in this part of the day: morning (before 12:00), afternoon (12:00 to 16:59), evening (17:00 on).
serviceIdstringyesOne service id from this venue's get_venue result. Not a service name.
slugstring–The venue's booking slug, exactly as find_venues or get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <…
venuestring–Alias of `slug`, kept for existing clients. Send `slug`.

No output schema declared.

No examples provided.

find_table_times ~629

Free table times at one restaurant or venue for one party size, over up to two weeks. Use find_appointment_times for a salon or clinic instead. Each returned time has an `at` label to show the guest and a `slotToken`. The token is the booking handle: it is signed, it expires in about 30 minutes, and it is the only way a time can be booked later. Pass it back exactly as given, never edited, and never reuse one from a different venue. An empty `times` array for a day means the venue has nothing at that party size that day, which usually means closed or fully booked. Each day lists at most 10 times unless `maxPerDay` says otherwise, spread across the day; `omitted` says how many more exist. To answer "around 7pm" or "lunch", send `near`, `partOfDay`, `notBefore` or `notAfter`. A party above the venue's online limit gets no times: the result carries `groupEnquiry` (a link and any contact details the venue published) to give the guest instead.

NameTypeReqDescription
daysinteger–How many consecutive days to search from that day, 1 to 14. Defaults to 3.
fromstring–Which day to start from: the word "today", the word "tomorrow", or an exact calendar date as YYYY-MM-DD. Resolved against the venue's own current date, which is often not yours. Do not send a phrase…
maxPerDayinteger–Most times to return per day, 1 to 40. Defaults to 10. Past it, the times are spread across the day (or nearest `near`) and `omitted` says how many were left out.
nearstring–A 24 hour time as HH:MM, for example 19:00 for 7pm. When a day has more times than maxPerDay, keep the ones closest to this.
notAfterstring–Drop times later than this 24 hour HH:MM.
notBeforestring–Drop times earlier than this 24 hour HH:MM.
partOfDaystring–Only times in this part of the day: morning (before 12:00), afternoon (12:00 to 16:59), evening (17:00 on).
partySizeintegeryesHow many people are coming, including the person booking.
slugstring–The venue's booking slug, exactly as find_venues or get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <…
venuestring–Alias of `slug`, kept for existing clients. Send `slug`.

No output schema declared.

No examples provided.

find_venues ~246

Search the businesses that take bookings through Gaplessly by name, by suburb or postcode, or by kind, and get back each one's slug, name, kind, address and booking page link. Use this when the guest names a business or an area but you do not have a slug; every other tool needs one. Send at least one of `name`, `location` or `kind`. Only real businesses that have chosen to be found by assistants are searchable here, so an empty result means "not found here", not that the business does not exist or cannot be booked: ask the guest for its booking link, which works with every other tool. Then call get_venue with the slug.

NameTypeReqDescription
kindstring–appointments for salons, clinics and studios; hospitality for restaurants, cafes and bars.
limitinteger–How many venues to return, 1 to 10. Defaults to 5.
locationstring–A suburb, city or postcode, matched against the venue address, for example "Newtown" or "2042".
namestring–Part of the business name, for example "Saltline". Case does not matter.

No output schema declared.

No examples provided.

get_venue ~294

Read a venue's public booking profile: what it is, where it is, what can be booked, and what time it is THERE right now. Call this first once you have a slug (find_venues turns a name or suburb into one): the other tools need it, and appointment searches need a service id from here. A detail the business has not entered (industry, address, phone) is left out and listed under `notProvided`; do not guess it. For a restaurant with an online party limit, `groupEnquiry` is where a larger party goes. Returns `venueClock`, which is the venue's own current date and time. Every date you ask for later is resolved against `venueClock.today`, not against your own today: the two are routinely different days. Times are given as text on purpose and there is no timezone identifier anywhere in the result, because converting them is how a booking ends up hours off.

NameTypeReqDescription
slugstring–The venue's booking slug, exactly as find_venues or get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <…
venuestring–Alias of `slug`, kept for existing clients. Send `slug`.

No output schema declared.

No examples provided.

start_appointment_booking ~333

Turn a time from find_appointment_times into a link the guest taps to finish booking. This does NOT book anything: it returns a short-lived URL on the venue's own booking page, already opened at that service, that staff member and that exact time, where the guest enters their own name, email and phone and confirms. Give the guest the `url` and say plainly that the booking is not made until they open it. Never ask the guest for their contact details to pass here; this tool does not take them, and the page collects them directly. Nothing is reserved in the meantime, so a popular time can still go before they tap.

NameTypeReqDescription
serviceIdstringyesThe same service id passed to find_appointment_times, from get_venue. The link opens on this service.
slotTokenstringyesA `slotToken` from find_appointment_times or find_table_times, copied exactly. It is signed and carries the venue and the time inside the signature, so it cannot be edited, built by hand, or used at…
slugstring–The venue's booking slug, exactly as find_venues or get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <…
venuestring–Alias of `slug`, kept for existing clients. Send `slug`.

No output schema declared.

No examples provided.

start_table_booking ~310

Turn a time from find_table_times into a link the guest taps to finish booking. This does NOT book anything: it returns a short-lived URL on the venue's own booking page, already opened at that party size and that exact sitting, where the guest enters their own details and confirms. The venue holds the table from the moment the guest opens the link, for about ten minutes, which is what gives them time to fill the form in. Until they open it nothing is held, so give them the `url` promptly and say the table is not theirs until they do.

NameTypeReqDescription
partySizeintegeryesThe same party size passed to find_table_times. The link opens on it.
slotTokenstringyesA `slotToken` from find_appointment_times or find_table_times, copied exactly. It is signed and carries the venue and the time inside the signature, so it cannot be edited, built by hand, or used at…
slugstring–The venue's booking slug, exactly as find_venues or get_venue returned it or as it appears in the venue's own booking link: the last path segment of gaplessly.com/book/<slug>, or the first label of <…
venuestring–Alias of `slug`, kept for existing clients. Send `slug`.

No output schema declared.

No examples provided.

Install

How do I install the Gaplessly Booking MCP server?

Gaplessly Booking is a hosted endpoint at https://gaplessly.com/api/mcp, 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 · gaplessly.com

# add to Claude Code
claude mcp add --transport http com-gaplessly-booking 'https://gaplessly.com/api/mcp'
Common questions

What is the Gaplessly Booking MCP server?

Gaplessly Booking is an MCP server listed in the public MCP registry as com.gaplessly/booking. Find free times at Gaplessly businesses on a plan with AI booking, then get a link to book. This page covers its hosted endpoint (https://gaplessly.com/api/mcp).

Is the Gaplessly Booking MCP server safe to use?

Gaplessly Booking scores 85 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 Gaplessly Booking MCP server expose?

Gaplessly Booking exposes 6 tools: find_venues, get_venue, find_appointment_times, find_table_times, start_appointment_booking, start_table_booking. Their descriptions and schemas cost roughly 2,430 tokens of context every time the server is loaded.

Does the Gaplessly Booking MCP server require authentication?

No. We connected to Gaplessly Booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Gaplessly Booking MCP server still maintained?

Gaplessly Booking is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Gaplessly Booking MCP server?

VerifyMCP ran 13 checks on Gaplessly Booking, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.