Bronjoy Marketplace
REMOTE · API.BRONJOY.COM · SCANNED SEP 27
Search and book appointments at service businesses across Uzbekistan.
Available components
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 not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1739 tokens (~289/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 Management67
- Stability observed for 20 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 Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do NOT tell the user", at byte 676 of that field. See how to fix → Fail
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Bronjoy Marketplace MCP server?
Bronjoy Marketplace is a hosted endpoint at https://api.bronjoy.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 · api.bronjoy.com
claude mcp add --transport http com-bronjoy-marketplace 'https://api.bronjoy.com/api/mcp'
{
"mcpServers": {
"com-bronjoy-marketplace": {
"url": "https://api.bronjoy.com/api/mcp"
}
}
} {
"servers": {
"com-bronjoy-marketplace": {
"type": "http",
"url": "https://api.bronjoy.com/api/mcp"
}
}
} [mcp_servers.com-bronjoy-marketplace] url = "https://api.bronjoy.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bronjoy-marketplace": {
"type": "remote",
"url": "https://api.bronjoy.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-bronjoy-marketplace --url 'https://api.bronjoy.com/api/mcp' --transport streamable-http
mcp_servers:
com-bronjoy-marketplace:
url: "https://api.bronjoy.com/api/mcp" {
"McpServers": {
"com-bronjoy-marketplace": {
"Transport": "http",
"Url": "https://api.bronjoy.com/api/mcp"
}
}
} assistant mcp add com-bronjoy-marketplace -t streamable-http -u 'https://api.bronjoy.com/api/mcp'
{
"mcpServers": {
"com-bronjoy-marketplace": {
"type": "http",
"url": "https://api.bronjoy.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 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.
- 26 Sept 26 0
- Endpoint reachability: not serving MCP → reachable ▲ functional
- 25 Sept 26 +48
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 22 Sept 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.
- 20 Sept 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.
- 18 Sept 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.
- 16 Sept 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.
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 27 Sept 2026 · Probed https://api.bronjoy.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=bronjoy.com | CN=WE1,O=Google Trust Services,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 25ee3c2ad57e33fd13241377ff599167 |
| SANs: bronjoy.com, *.bronjoy.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.bronjoy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bronjoy.com. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline' https://fonts.bunny.net; img-src 'self' data: blob: https://cdn.bronjoy.com; font-src 'self' data: https://fonts.bunny.net; connect-src 'self' https://cdn.bronjoy.com; media-src 'self' https://cdn.bronjoy.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| 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://api.bronjoy.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.bronjoy.com/api/mcp | HTTPS enforced | 301 | https://api.bronjoy.com/api/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 ~294
Book a slot, using the code the user received from request-booking-code. WHEN TO USE: last step, once the user has confirmed the venue, service and exact time AND has read you their 6-digit code. Requires the same contact the code was sent to. The booking is created as "pending": the business still confirms it, so tell the user it is requested and they will hear back — not that it is guaranteed. If the venue takes prepayment, the response carries a link the user must open to pay; the slot is not held indefinitely. Only works for venues with `is_bookable: true`.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The email the code was sent to, if that is the channel used. | |
| name | string | yes | The user's name, as the business should see it. |
| notes | string | – | Anything the business should know, max 500 characters. |
| phone | string | – | The phone the code was sent to, if that is the channel used. |
| service_id | integer | yes | Service id from check-availability. |
| slug | string | yes | The venue slug. |
| start_time | string | yes | Exact `start_time` value from a check-availability slot. Do not invent or round times. |
| verification_code | string | yes | The 6-digit code the user received. Ask them for it — you never see it yourself. |
No output schema declared.
No examples provided.
check-availability Check venue availability ~191
Bookable services and open time slots for a venue on a given date. WHEN TO USE: the user has picked a venue with `is_bookable: true` and wants a time. Call without `service_id` first to see the services and their prices, then again with one to get its slots. Returns an explicit refusal for venues that are not set up for online booking — do not try to work around it, offer the phone number instead. Slot times are in the venue's timezone and are exactly the values book-appointment expects.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Day to check, Y-m-d. Today or later, at most 30 days ahead. |
| service_id | integer | – | Which service to check. Omit on the first call to list the services with their ids, durations and prices. |
| slug | string | yes | The venue slug from search-venues. |
No output schema declared.
No examples provided.
get-venue Venue profile ~164
Full public profile for one venue: address, opening hours, what it offers, amenities, payment methods, website and whether it can be booked online. WHEN TO USE: after search-venues, when the user asks anything about a specific place — "are they open on Sunday", "do they do colouring", "where exactly is it", "how much". This is the right tool for the ~99% of the catalogue that is not bookable: it carries everything needed to answer a question or send the user there in person. The phone number is masked here — call reveal-phone only when the user actually wants to ring them.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The venue slug from search-venues, e.g. "demo-barber". |
No output schema declared.
No examples provided.
request-booking-code Send booking confirmation code ~217
Send the user a 6-digit confirmation code, which book-appointment then requires. WHEN TO USE: the user has chosen a venue, a service and a slot, and has given you their email address or phone number. Call this before book-appointment — a booking without a code is rejected. YOU DO NOT RECEIVE THE CODE. It goes to the user's own inbox or phone; ask them to read it back to you. That is the point: it proves the contact belongs to the person booking, so a business does not get appointments from numbers nobody answers. The code lasts 5 minutes and covers one booking. Only a few codes may be sent to one contact — do not loop.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The user's email address. Give this or phone. | |
| phone | string | – | The user's phone in international format, e.g. +998901234567. Preferred when the venue will need to call them. |
| slug | string | yes | The venue slug the user is booking. |
No output schema declared.
No examples provided.
reveal-phone Reveal venue phone ~111
The venue's real phone number. WHEN TO USE: the user wants to call — typically because the venue is not bookable online, or they want to ask something no profile field answers. Deliberately a separate call from get-venue, which returns a masked number. Reveals are rate limited per caller: request them one at a time, for a venue the user has actually chosen, never in bulk across search results.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The venue slug from search-venues. |
No output schema declared.
No examples provided.
search-venues Search venues ~321
Search Bronjoy's catalogue of service businesses in Uzbekistan by keyword, city and category. WHEN TO USE: the user is looking for a place ("barbershop in Tashkent", "dentist near Chilanzar", "car wash open now"). Start here — every other tool takes the `slug` this returns. Results are ranked, compact, and include `is_bookable`, which decides what you can offer next: bookable venues can go through check-availability → request-booking-code → book-appointment, the rest can only be described and phoned. Names and addresses come back in Russian or Uzbek; quote them as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| bookable_only | boolean | – | Return only venues that can take an online booking. Set this when the user wants to book rather than to be told about places — most of the catalogue cannot be booked, and without this the bookable on… |
| category | string | – | Category slug, e.g. "barber", "dental", "car-wash". Use the slug from a previous result when narrowing. |
| city | string | – | City slug or name, e.g. "tashkent", "samarkand", "Бухара". |
| limit | integer | – | How many venues to return, 1-20. Default 5 — prefer a small number and refine. |
| query | string | – | Free text: a business name, a service ("стрижка", "haircut"), or a landmark. Matches across Latin and Cyrillic. |
No output schema declared.
No examples provided.
What is the Bronjoy Marketplace MCP server?
Bronjoy Marketplace is an MCP server listed in the public MCP registry as com.bronjoy/marketplace. Search and book appointments at service businesses across Uzbekistan. This page covers its hosted endpoint (https://api.bronjoy.com/api/mcp).
Is the Bronjoy Marketplace MCP server safe to use?
Bronjoy Marketplace scores 72 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 Bronjoy Marketplace MCP server expose?
Bronjoy Marketplace exposes 6 tools: search-venues, get-venue, reveal-phone, check-availability, request-booking-code, book-appointment. Their descriptions and schemas cost roughly 1,298 tokens of context every time the server is loaded.
Does the Bronjoy Marketplace MCP server require authentication?
No. We connected to Bronjoy Marketplace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bronjoy Marketplace MCP server still maintained?
Bronjoy Marketplace is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.