agent-bev MCP server

• Registry nameai.agent-bev/bev-doorverified in the MCP registry

The registry name sits under agent-bev.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-13
• Tools9
• Server calls itselfai.agent-bev/bev-door
• Server version0.2.5
• Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 635 ms.

• search_drinks

  Find beers, wines, spirits, ciders and ready-to-drink drinks by name, style, origin or category across every open country node. Returns record ids with each record's CUVEE.

• get_record

  Read one product in full by record_id: every field with its source page, reader and state; its CUVEE; its claim status; the signed record (JWS).

• find_producer

  Find a maker and its products across every open node, with the maker's name as each source wrote it.

• list_nodes

  List the countries on the record: each node's door, languages, state and, for an open node, its counts.

• compare_drinks

  Compare two to ten products side by side, field by field, each value with its source page.

• get_order_route

  Get the maker's or distributor's trade channel to order a product, as the record states it. Never a consumer channel.

• create_order_intent

  Place an order intent for one to ten records (quantity, delivery market, optional date and note, the buyer's organisation and email). The Bourse routes it to each maker; verified makers answer with offers, and a maker's own Brand Agent…

• get_offers

  Read the makers' offers on an order intent, and the order once placed. By the buyer's email given on create_order_intent.

• accept_offer

  Accept one offer and place the order through the Bourse. Accepting is one x402 paid call (HTTP 402 with the payment offer until paid): it settles and signs the order. The goods are paid between the two companies on the offer's own terms.