Lacquer nail salon booking
REMOTE · LACQUER.BEAUTY
Find US nail salons and book confirmed appointments: menus, prices, hours, live open times.
Available components
Last scanned (25 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
Recent critical change
Authorization (16 Oct 2026). See the changelog before you install this server.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (book_appointment). See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 776 tokens (~194/item across 4 items; 4 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://lacquer.beauty/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lacquer.beauty | CN=YR1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | RSA 2048 | SHA256-RSA | 57a1cc3a1f7d940e24bd7eb3db9c5024957 |
| SANs: lacquer.beauty | ||||||
| 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 lacquer.beauty. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| beauty. | present | 6827, 52406 | 8, 8 | Verified |
| lacquer.beauty. | 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=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://vioafxderpkasovjyetm.supabase.co; media-src 'self' https://vioafxderpkasovjyetm.supabase.co; font-src 'self' data:; connect-src 'self' https://vioafxderpkasovjyetm.supabase.co; worker-src 'self'; manifest-src 'self'; frame-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lacquer.beauty/mcp | Verified | 200 | |
| http (plaintext) | http://lacquer.beauty/mcp | HTTPS enforced | 308 | https://lacquer.beauty/mcp |
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 →
book_appointment Book an appointment ~176
Books an appointment. Real and immediate: the salon holds the time and the customer gets a confirmation text. It can't be cancelled or changed online, only by calling the salon. Repeating the same call returns the same booking, never a second one.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Name of the AI assistant making the booking, e.g. "Claude". The salon sees "Booked by <agent_name>". |
| customer_name | string | yes | The customer's name, as the salon should greet them. |
| customer_phone | string | yes | The customer's mobile number; the confirmation text goes here. |
| service_id | string | yes | The service's id on the salon's menu. |
| slug | string | yes | The salon's slug. |
| start_at | string | yes | ISO start time of an open slot for this salon and service. |
No output schema declared.
No examples provided.
check_availability Open appointment times ~105
Open start times for one service with any technician, each as an ISO start_at and a local label. Searches from now when no date is given; up to 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD in the salon's local time. |
| days | integer | – | How many days from date. Default 1. |
| service_id | string | yes | The service's id on the salon's menu. |
| slug | string | yes | The salon's slug. |
No output schema declared.
No examples provided.
find_salons Find nail salons ~214
Nail salons on Lacquer in a US city + state or ZIP code, optionally narrowed by salon name. Up to 20 per call; "total" says how many match, and "offset" pages through the rest. Salons that take online bookings ("books_online": true) come first; a salon with books_online false has no open times online and is listed with its phone number. Within that, Lacquer partner salons ("partner": true) come first; the rest rotate daily, and the order says nothing about quality.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City, e.g. "Santa Monica". Used together with state. |
| limit | integer | – | – |
| name | string | – | Part of the salon's name. |
| offset | integer | – | Number of results to skip; a result's next_offset gives the next page. |
| state | string | – | US state, "CA" or "California". |
| zip | string | – | 5-digit ZIP code. Used instead of city/state when given. |
No output schema declared.
No examples provided.
get_salon Salon details and menu ~41
A salon's address, phone, weekly hours and full service menu (service_id, price, duration).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The salon's slug. |
No output schema declared.
No examples provided.
How do I install the Lacquer nail salon booking MCP server?
Lacquer nail salon booking is a hosted endpoint at https://lacquer.beauty/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 · lacquer.beauty
claude mcp add --transport http beauty-lacquer-booking 'https://lacquer.beauty/mcp'
What is the Lacquer nail salon booking MCP server?
Lacquer nail salon booking is an MCP server listed in the public MCP registry as beauty.lacquer/booking. Find US nail salons and book confirmed appointments: menus, prices, hours, live open times. This page covers its hosted endpoint (https://lacquer.beauty/mcp).
Is the Lacquer nail salon booking MCP server safe to use?
Lacquer nail salon booking scores 75 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 Lacquer nail salon booking MCP server expose?
Lacquer nail salon booking exposes 4 tools: find_salons, get_salon, check_availability, book_appointment. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
Does the Lacquer nail salon booking MCP server require authentication?
No. We connected to Lacquer nail salon booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lacquer nail salon booking MCP server still maintained?
Lacquer nail salon booking is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.