Skip to content

B.R.M Chronographes - Watch Configurator MCP server

com.brm-chronographes/configuratorbrm-chronographes.comstreamable-httpv1.0.0Scanned

Configure, price, render and order a made-to-order B.R.M watch (French manufacture). No auth.

9 tools: 2 can delete or cancel things, 3 change things and 4 only read.

Tools: 2 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the B.R.M Chronographes - Watch Configurator MCP server can do

The B.R.M Chronographes - Watch Configurator MCP server is published by brm-chronographes.com, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (2 tools: submit_request and create_order) and create or change data (3 tools: quote_configuration, render_configuration and create_share_link). 4 tools only read.

1 tool reads private data (get_order_status); 4 tools bring in text other people can write (create_share_link, submit_request, create_order and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 2Claude Code: deny
  • create_orderPrepares an order of this configured watch for the user.Reads text others writeNo findings

    Why it is in this group

    • The name "create_order" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Prepare an order the customer confirms by email
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • submit_requestSends 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_reques…Reads text others writeNo findings

    Why it is in this group

    • The name "submit_request" says "submit": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Ask B.R.M to contact the user
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 3Claude Code: ask
  • quote_configurationPrice 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 b…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Price for a delivery country
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • render_configurationComposes the photographic rendering of the configured watch (JPEG).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Render the watch
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • describe_modelComponents, options (option_id, name, surcharge_eur, is_default), mutual exclusions (exclusive_group) and dependencies (depends_on: the component only exists if one of these option…No findings

    Why it is in this group

    • The name "describe_model" says "describe": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Describe a model's components and options
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_order_statusReturns only the state of the order: awaiting_customer_confirmation, confirming, confirmed_awaiting_payment, paid, expired, cancelled, confirmation_email_failed or needs_assistance…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_order_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Status of an order prepared with create_order
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_modelsReturns the configurable watch models with base price (EUR incl.No findings

    Why it is in this group

    • The name "list_models" says "list": a word for reading.
    Description, as the server wrote it
    Returns the configurable watch models with base price (EUR incl. French VAT), diameter and a rendered picture of the default configuration.

    Annotations the server declares

    • title: List configurable B.R.M models
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_configurationResolves defaults, exclusions and dependencies; returns valid=false with errors (unknown_option, dependency_unmet) and warnings (exclusive_conflict) that can be fixed, plus the res…No findings

    Why it is in this group

    • The name "validate_configuration" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Validate a configuration
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (2 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.brm-chronographes.com/mcp: tools/list returned 9 tools to an anonymous client, including submit_request (destructive), create_order (destructive), quote_configuration (write), render_configuration (write), create_share_link (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http configurator https://api.brm-chronographes.com/mcp
claude mcp add --transport http configurator https://api.brm-chronographes.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__configurator__list_models",
      "mcp__configurator__describe_model",
      "mcp__configurator__validate_configuration",
      "mcp__configurator__get_order_status"
    ],
    "ask": [
      "mcp__configurator__quote_configuration",
      "mcp__configurator__render_configuration",
      "mcp__configurator__create_share_link"
    ],
    "deny": [
      "mcp__configurator__submit_request",
      "mcp__configurator__create_order"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as configurator. Review it before you use it.

Capability tags behind 4 rules
  • mcp__configurator__create_share_link untrusted-input
  • mcp__configurator__submit_request untrusted-input
  • mcp__configurator__create_order untrusted-input
  • mcp__configurator__get_order_status private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.brm-chronographes/configurator/verify?hash=ee9899b5c20db627b2a18533adf147f80a88abae9fddf17a14b0a36df7775724" | jq -e '.changed == false'

Pinned hash ee9899b5c20d, from Nov 12, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.brm-chronographes/configurator/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.brm-chronographes/configurator
[![Anlyon Radar](https://radar.anlyon.com/badge/com.brm-chronographes/configurator.svg)](https://radar.anlyon.com/servers/com.brm-chronographes/configurator)

Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.

B.R.M Chronographes - Watch Configurator MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the B.R.M Chronographes - Watch Configurator MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the B.R.M Chronographes - Watch Configurator MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: submit_request and create_order.

Can the B.R.M Chronographes - Watch Configurator MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the B.R.M Chronographes - Watch Configurator MCP server have?

9 tools: 2 destructive, 3 write, 4 read. submit_request, create_order, quote_configuration, render_configuration, create_share_link, list_models, describe_model, validate_configuration and 1 more.

Does the B.R.M Chronographes - Watch Configurator MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the B.R.M Chronographes - Watch Configurator MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the B.R.M Chronographes - Watch Configurator MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.