Belcome
REMOTE · BELCOME.APP
Find salons, barbershops, spas and med spas on Belcome, see services, prices and open times.
Available components
Last scanned (18 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category E-commerce
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1342 tokens (~122/item across 11 items; 11 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 Management87
- Stability observed for 26 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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 →
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.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 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.
- 1 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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1145 → 1342 ▼ functional
- New tool “list_addons” functional
- “find_slots” added an optional parameter “start_time_before” cosmetic
- “find_slots” added an optional parameter “start_time_from” cosmetic
- 27 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 932 → 1145 ▼ functional
- New tool “get_about” functional
- New tool “list_gallery” 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 7 Nov 2026 · Probed https://belcome.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=belcome.app | CN=YE2,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6460981d8dbf3ae03d1e2e290893ae96be1 |
| SANs: belcome.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of belcome.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| belcome.app. | 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=31536000 |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://belcome.app/mcp | Verified | 200 | |
| http (plaintext) | http://belcome.app/mcp | HTTPS enforced | 301 | https://belcome.app/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 →
find_business Find a salon or spa ~108
Find salons, barbershops, spas and studios that take online bookings on Belcome, by name, service or city. Returns up to 10 businesses with their locations and booking page.
| Name | Type | Req | Description |
|---|---|---|---|
| near | string | – | City, state or ZIP code to narrow the search, e.g. "Orlando" or "02601". |
| query | string | yes | Business name, service or kind of place, e.g. "balayage", "barber", "Cape Cod Nails". |
No output schema declared.
No examples provided.
find_slots Find open times ~260
Find open times for one service at a business, up to 14 days. Each time comes with a booking_url that opens the business's booking page with the service, professional and time already chosen; give that link to the person to confirm with their name and phone.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id returned by find_business. |
| from | string | – | First day, YYYY-MM-DD in the location's timezone. Defaults to today. |
| location_id | string | – | Location id. Defaults to the first location. |
| service_id | string | yes | Service id from list_services. |
| staff_id | string | – | Only this professional. Leave out for anyone available. |
| start_time_before | string | – | Optional latest start time, exclusive, HH:MM (24-hour) in the location timezone on every searched day. Must be later than start_time_from if both are given. Filters appointment starts, not end times. |
| start_time_from | string | – | Optional earliest start time, inclusive, HH:MM (24-hour) in the location timezone on every searched day. For afternoon use 12:00. |
| through | string | – | Last day, YYYY-MM-DD, at most 13 days after from. Defaults to a week. |
No output schema declared.
No examples provided.
get_about About the business ~103
What the business says about itself on its booking page: tagline, "about us" story, studio policies (late arrival, parking, what to bring) and extra text blocks. Use it for "what is this place like?" or "what should I know before I go?".
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
get_booking_policy Booking, cancellation and deposit rules ~97
Cancellation window, whether the business approves bookings, how far ahead one can book, deposit or prepayment and late-cancel or no-show fees. Use it for "can I cancel?", "do I pay a deposit?" before handing over booking_url.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
get_business Business details and hours ~94
Opening hours, phone, address, map point, languages, rating, links and frequently asked questions of one business location. Use it for "is it open on Sunday?" or "what is the phone number?" before or after find_slots.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
list_addons Add-ons and extras ~97
Add-ons a business offers online at one location (a treatment extra, a longer session): name, duration, price and the services each one can be added to. They are picked on the booking page together with the main service, never booked alone.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
list_gallery Photo gallery ~102
The photos the business shows on its booking page (its work: cuts, colour, nails, tattoos...), each with the service it is tagged to and a booking link for that service. Use it for "can I see their work?" or "do they do this style?".
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
list_offers Packages, memberships and gift cards ~83
Session packages and memberships a business sells online, and whether it sells gift cards, with prices. Give the person shop_url to buy: payment happens there, never in the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
list_reviews Client reviews ~75
The average rating and the latest client reviews of a business location, as shown on its booking page. Empty when the business does not collect reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
list_services List services and prices ~77
List the services a business offers online at one location: name, duration, price and the professionals who do each one. Use the ids with find_slots.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
list_team Meet the team ~87
The professionals who take online bookings at a business location: name, role, short bio, the services each one does and their rating. Use the staff_id with find_slots to book with a specific person.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | The business id ("business" field) returned by find_business. |
| location_id | string | – | Location id from find_business. Defaults to the first location. |
No output schema declared.
No examples provided.
How do I install the Belcome MCP server?
Belcome is a hosted endpoint at https://belcome.app/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 · belcome.app
claude mcp add --transport http app-belcome-booking 'https://belcome.app/mcp'
What is the Belcome MCP server?
Belcome is an MCP server listed in the public MCP registry as app.belcome/booking. Find salons, barbershops, spas and med spas on Belcome, see services, prices and open times. This page covers its hosted endpoint (https://belcome.app/mcp).
Is the Belcome MCP server safe to use?
Belcome scores 86 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 Belcome MCP server expose?
Belcome exposes 11 tools: find_business, list_services, find_slots, get_business, list_team, and 6 more. Their descriptions and schemas cost roughly 1,183 tokens of context every time the server is loaded.
Does the Belcome MCP server require authentication?
No. We connected to Belcome without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Belcome MCP server still maintained?
Belcome is still listed as active in the MCP registry. We last reached this channel on 7 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 Belcome MCP server?
VerifyMCP ran 13 checks on Belcome, 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.