B.R.M Chronographes - Watch Configurator
REMOTE · API.BRM-CHRONOGRAPHES.COM
Configure, price, render and order a made-to-order B.R.M watch (French manufacture). No auth.
Available components
Last scanned (5 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 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 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 (submit_request). 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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1262 tokens (~140/item across 9 items; 9 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 Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 7% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 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.
- 25 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.
- 23 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.
- 21 Oct 26 +1
- Tool “create_order” rewrote its description, which is the text the model reads security
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://api.brm-chronographes.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.brm-chronographes.com | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6457fa2b50d22ad09df66498879b327a9eb |
| SANs: api.brm-chronographes.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 api.brm-chronographes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| brm-chronographes.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' https://js.stripe.com https://*.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' https: data: blob:; connect-src 'self' https://api.brm-chronographes.com https://hub.brm-chronographes.com https://club.brm-chronographes.com https://api.stripe.com https://*.stripe.com; font-src 'self' https://fonts.gstatic.com data:; frame-ancestors 'self'; frame-src 'self' blob: https://js.stripe.com https://hooks.stripe.com https://*.stripe.com; object-src 'none'; base-uri 'self'; form-action 'self' https://*.stripe.com; |
| 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://api.brm-chronographes.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.brm-chronographes.com/mcp | HTTPS enforced | 301 | https://api.brm-chronographes.com/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 →
create_order Prepare an order the customer confirms by email ~293
Prepares an order of this configured watch for the user. ONLY call it when the user explicitly asked you to order it and agreed to share their name, email and delivery address with B.R.M (user_consent=true). B.R.M then emails the user a summary with a 'Confirm my order' button; the order is placed ONLY after the user confirms it there (link valid 72 h), choosing card, interest-free instalments (Alma under EUR 2,000, Pledg from EUR 2,000, where available), a 20% deposit (watch from EUR 3,000) or bank transfer (EUR only), and pays B.R.M himself on B.R.M's secure payment page — no card or bank details go through this tool, and you never pay or commit the user. Relay message_for_user to the user. Do NOT say the order is placed, do NOT ask for payment details, NEVER promise a delivery date. The price is computed by B.R.M for the delivery country (currency and VAT follow the delivery country). Limited to a few orders per day per email. Pass an idempotency_key to make retries safe.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | yes | – |
| customer | object | yes | – |
| idempotency_key | string | – | – |
| lang | string | – | – |
| shipping_address | object | yes | – |
| user_consent | boolean | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation | object | – | – |
| created_at | string | – | – |
| duplicate | boolean | – | – |
| expires_at | string | – | Deadline for the user's confirmation. |
| explanation | string | – | – |
| idempotent_replay | boolean | – | – |
| indicative_price | object | – | – |
| is_order | – | – | Always false here: the order exists only after the user's confirmation. |
| is_paid | boolean | – | – |
| lead_time | object | – | No firm number of weeks is given by this API: show `url` (the delivery page of brm-chronographes.com, in the user's language) for lead times. |
| message_for_user | string | – | Relay this to the user. |
| order_id | string | – | – |
| rules_for_agent | string | – | – |
| status | string | – | – |
No examples provided.
create_share_link Create a link that reopens this watch ~100
Returns configurator_url (opens this exact watch in the configurator on brm-chronographes.com, where the user can adjust it and add it to the basket; this is the link meant for the user) and preview_url (a public presentation page with rotation, shared by every identical configuration). Idempotent. Sharing is not ordering.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | yes | – |
| lang | string | – | – |
| view | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| configurator_url | string | – | Reopens this exact watch on brm-chronographes.com. |
| image_url | string|null | – | – |
| is_order | – | – | – |
| note | string | – | – |
| preview_url | string|null | – | Public page shared by every identical configuration; carries no user data. |
| total_price_eur | number | – | – |
No examples provided.
describe_model Describe a model's components and options ~79
Components, options (option_id, name, surcharge_eur, is_default), mutual exclusions (exclusive_group) and dependencies (depends_on: the component only exists if one of these options is selected). option_id values are opaque identifiers; name is the label to use with the user.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| model | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| base_price_eur | number | – | – |
| components | array | – | – |
| diameter_mm | integer|null | – | – |
| lang | string | – | – |
| model_id | string | – | – |
| name | string | – | – |
| rules | object | – | – |
No examples provided.
get_order_status Status of an order prepared with create_order ~83
Returns only the state of the order: awaiting_customer_confirmation, confirming, confirmed_awaiting_payment, paid, expired, cancelled, confirmation_email_failed or needs_assistance. No customer data. Pass the order_id returned by create_order, or the idempotency_key you used.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | – |
| order_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | – | – |
| expires_at | string | – | Deadline for the user's confirmation. |
| explanation | string | – | – |
| is_paid | boolean | – | – |
| lead_time | object | – | No firm number of weeks is given by this API: show `url` (the delivery page of brm-chronographes.com, in the user's language) for lead times. |
| order_id | string | – | – |
| status | string | – | – |
No examples provided.
list_models List configurable B.R.M models ~33
Returns the configurable watch models with base price (EUR incl. French VAT), diameter and a rendered picture of the default configuration.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | – | – |
| currency_of_prices | – | – | – |
| lead_time | object | – | No firm number of weeks is given by this API: show `url` (the delivery page of brm-chronographes.com, in the user's language) for lead times. |
| models | array | – | – |
| notes | string | – | – |
| prices_include_french_vat | boolean | – | – |
No examples provided.
quote_configuration Price for a delivery country ~111
Price in the billing currency of the DELIVERY country (the currency cannot be chosen), with the tax regime: French VAT inside the EU, 0% VAT outside the EU (duties payable by the buyer). Indicative and non-binding; the checkout on brm-chronographes.com is authoritative.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | yes | – |
| country | string | yes | ISO-3166 alpha-2, e.g. 'US'. |
| display_currency | string | – | – |
| lang | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| billing_currency | string | – | – |
| binding | – | – | – |
| catalogue_price_eur_incl_fr_vat | number | – | – |
| delivery_country | string | – | – |
| display_only | object | – | – |
| lead_time | object | – | No firm number of weeks is given by this API: show `url` (the delivery page of brm-chronographes.com, in the user's language) for lead times. |
| legal_notice | string|null | – | – |
| model_id | string | – | – |
| note | string | – | – |
| price | number | – | – |
| price_formatted | string | – | – |
| rounding | string | – | – |
| shipping | – | – | – |
| tax_regime | object | – | – |
No examples provided.
render_configuration Render the watch ~67
Composes the photographic rendering of the configured watch (JPEG). view 0 is the three-quarter view; 30 views (0-29) rotate the watch by 12° each.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | yes | – |
| view | integer | – | – |
| width | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| image_url | string | – | – |
| mime_type | – | – | – |
| note | string | – | – |
| view | integer | – | – |
| views_available | integer | – | – |
| width | integer | – | – |
No examples provided.
submit_request Ask B.R.M to contact the user ~181
Sends the user's request to the B.R.M team: 'appointment' (private visit of the manufacture — a booking link is returned), 'quote' (personalised quote by email), or 'special_request' (anything the configurator does not offer; the workshop checks feasibility). Requires the user's explicit agreement to share their email and be contacted (user_consent=true). The message cannot be recalled once sent. Never an order, never a payment. Limited to a few requests per day.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | – | – |
| contact | object | yes | – |
| country | string | – | – |
| idempotency_key | string | – | – |
| kind | string | yes | – |
| lang | string | – | – |
| message | string | yes | What the user wants, in their words, precise enough for the workshop. |
| user_consent | boolean | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate | boolean | – | – |
| idempotent_replay | boolean | – | – |
| is_order | – | – | – |
| kind | string | – | – |
| next_step | object | – | – |
| privacy | string | – | – |
| request_id | string | – | – |
| status | – | – | – |
No examples provided.
validate_configuration Validate a configuration ~66
Resolves defaults, exclusions and dependencies; returns valid=false with errors (unknown_option, dependency_unmet) and warnings (exclusive_conflict) that can be fixed, plus the resolved list of selections and total EUR price.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | yes | – |
| lang | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | – | – |
| is_order | – | – | – |
| resolved | object | – | – |
| valid | boolean | – | – |
| warnings | array | – | – |
No examples provided.
How do I install the B.R.M Chronographes - Watch Configurator MCP server?
B.R.M Chronographes - Watch Configurator is a hosted endpoint at https://api.brm-chronographes.com/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.brm-chronographes.com
claude mcp add --transport http com-brm-chronographes-configurator 'https://api.brm-chronographes.com/mcp'
What is the B.R.M Chronographes - Watch Configurator MCP server?
B.R.M Chronographes - Watch Configurator is an MCP server listed in the public MCP registry as com.brm-chronographes/configurator. Configure, price, render and order a made-to-order B.R.M watch (French manufacture). No auth. This page covers its hosted endpoint (https://api.brm-chronographes.com/mcp).
Is the B.R.M Chronographes - Watch Configurator MCP server safe to use?
B.R.M Chronographes - Watch Configurator scores 74 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 B.R.M Chronographes - Watch Configurator MCP server expose?
B.R.M Chronographes - Watch Configurator exposes 9 tools: list_models, describe_model, validate_configuration, quote_configuration, render_configuration, and 4 more. Their descriptions and schemas cost roughly 1,013 tokens of context every time the server is loaded.
Does the B.R.M Chronographes - Watch Configurator MCP server require authentication?
No. We connected to B.R.M Chronographes - Watch Configurator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the B.R.M Chronographes - Watch Configurator MCP server still maintained?
B.R.M Chronographes - Watch Configurator 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.