# Pinflower — flowers in Prague (remote · pinflower.cz)

Order bouquets from independent Prague florists: live prices, delivery times, pay on pinflower.cz.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `pinflower.cz`: 80/100 (this document), [markdown](https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp.md), [page](https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp)

## Channel facts

- Endpoint: `https://pinflower.cz/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (pinflower_cancel_order).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3382 tokens (~307/item across 11 items; 9 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Pinflower — flowers in Prague MCP server?

Pinflower — flowers in Prague is a hosted endpoint at https://pinflower.cz/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.

### Claude

```bash
claude mcp add --transport http cz-pinflower-flowers 'https://pinflower.cz/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cz-pinflower-flowers": {
      "url": "https://pinflower.cz/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cz-pinflower-flowers": {
      "type": "http",
      "url": "https://pinflower.cz/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cz-pinflower-flowers]
url = "https://pinflower.cz/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cz-pinflower-flowers": {
      "type": "remote",
      "url": "https://pinflower.cz/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cz-pinflower-flowers --url 'https://pinflower.cz/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cz-pinflower-flowers:
    url: "https://pinflower.cz/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cz-pinflower-flowers": {
      "Transport": "http",
      "Url": "https://pinflower.cz/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cz-pinflower-flowers -t streamable-http -u 'https://pinflower.cz/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cz-pinflower-flowers": {
      "type": "http",
      "url": "https://pinflower.cz/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-11 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 79, −1)

- [functional] Stability: pass → 0.97

### 2026-11-07 (score 80, 0)

- [security] Tool “pinflower_create_order” rewrote its description, which is the text the model reads
- [security] Tool “pinflower_quote_order” rewrote its description, which is the text the model reads

### 2026-11-06 (score 80, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-10-30 (score 80, 0)

- [cosmetic] “pinflower_search_bouquets” added an optional parameter “flowers”

### 2026-10-25 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-10-18 (score 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-17 (score 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “pinflower_cancel_order” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good

## MCP tools (9)

### `pinflower_cancel_order` (~156 tokens)

Cancel an order

Use this when the buyer explicitly asks to cancel an order placed here. The website's rules apply: free while the florist has not confirmed, and for a later-day order until the cut-off before its time window; a paid amount is refunded in full. Two steps: order_ref with confirm=true sends a 6-digit code to the e-mail the order was placed with; order_ref with that code then cancels. It cancels eligible orders; changing items, delivery details or the delivery time is not supported.

Input parameters:

- `code` (string): The 6-digit code from the e-mail (second call).
- `confirm` (boolean, required): true = the buyer confirmed they want to cancel.
- `order_ref` (string, required)

Output parameters:

- `cancelled` (boolean)
- `code_sent_to` (string)
- `order_ref` (string)
- `refunded_czk` (number|null)

### `pinflower_check_delivery` (~180 tokens)

Check delivery to a place

Use this when the buyer asks whether Pinflower delivers to a place in Prague, how much delivery costs, how soon it can arrive, or whether flowers can come tonight — before choosing a bouquet. Takes the place as the buyer said it. Bouquet search results already include this for their place.

Input parameters:

- `date` (string): Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
- `locale` (string): The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
- `where` (string, required): Where the flowers go, as the buyer said it: a Prague district ('Praha 5'), a quarter ('Vinohrady', 'Smíchov') or a street address. Omit when unknown.

Output parameters:

- `can_deliver` (boolean)
- `delivery_fee_from_czk` (number|null)
- `earliest` (object|null)
- `florists` (integer)
- `night_delivery` (boolean)
- `place` (string)

### `pinflower_create_order` (~789 tokens)

Order bouquets (pay on pinflower.cz)

Use this when the buyer has agreed to the quoted total: it creates the order exactly like the website's checkout and returns the secure payment link on pinflower.cz. Takes the quote's details plus terms_accepted, confirmed_total_czk (the agreed total) and order_intent; if the total has changed meanwhile, nothing is created and it returns the new breakdown instead. Takes: the bouquet(s) (bouquet_id from search; several bouquets of ONE florist with quantities in items); delivery or pickup; for delivery the street address with house number in Prague; the recipient's name and phone when someone else receives the flowers; the date and a time (one of the bouquet's offered times, or 'asap'); the buyer's name, e-mail and phone (+420…); an optional card message and note for the florist; the buyer's promo code if they have one. Above 10 000 Kč the buyer's billing address is required. Also on offer: address_mode 'ask_recipient' when the florist should agree the address with the recipient by phone — a surprise (the recipient's name and phone are then required); time 'agree_with_recipient' when the florist should agree the time with the recipient by phone (the recipient's name and phone are then required); add-ons per bouquet (listed in the bouquet details); recipient.care_reminder=true — the free (0 Kč) care reminder for the recipient, offered once when someone else receives the flowers; company details (IČO) for a purchase by a company. Nothing is charged here and the florist is not told until the buyer pays.

Input parameters:

- `address` (string): Delivery to a known address: street and house number in Prague.
- `address_mode` (string): ask_recipient = the courier/florist agrees the address with the recipient by phone (a surprise); no address needed, delivery priced at the whole-city rate.
- `billing_address` (string): The buyer's billing address — required by Czech tax rules when the order is over 10 000 Kč (unless buying for a company).
- `bouquet_id` (string): One bouquet (shortcut for items with a single line).
- `buyer` (object, required)
- `card_message` (string)
- `company` (object): Buying for a company — the invoice is issued to it.
- `confirmed_total_czk` (integer, required): The quoted total_czk the buyer agreed to — a different total refuses the order.
- `courier_note` (string): Bell name, entrance, gate code.
- `date` (string, required): 'today', 'tomorrow' or YYYY-MM-DD.
- `florist_id` (string): The florist — required when the order is a custom bouquet alone.
- `florist_note` (string)
- `fulfilment` (string)
- `items` (array): Several bouquets from the SAME florist, with quantities.
- `locale` (string)
- `marketing_opt_in` (boolean): true = the buyer asked for news and offers.
- `order_intent` (string, required): The quote's order_intent. The same order_intent always returns the same order (a lost answer is safe to retry); each quote issues a new one.
- `promo_code` (string): The buyer's promo code, if they have one — works for guests and signed-in buyers alike; the checkout checks it.
- `recipient` (object): Who receives the flowers, when it is someone else than the buyer — the courier calls them.
- `terms_accepted` (boolean, required): true = the buyer agreed to the terms.
- `time` (string, required): HH:MM from the offered times, or 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only).
- `unit` (string): Apartment, floor, company at the door.

Output parameters:

- `order_number` (integer|null)
- `order_ref` (string)
- `pay_url` (string)
- `total_czk` (number)

### `pinflower_get_bouquet` (~232 tokens)

Bouquet details and times

Use this when the buyer is interested in one bouquet from the search results: what is inside, its size, photos, the florist's rating, the price with delivery (exact for a street address — delivery_fee_exact says so; otherwise the shop's typical fee) and every time it can arrive on a given day. Needs a bouquet_id as search results show it. Covers one bouquet at a time.

Input parameters:

- `bouquet_id` (string, required)
- `date` (string): Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
- `fulfilment` (string): delivery (default) or pickup at the florist's shop.
- `locale` (string): The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
- `where` (string): Where the flowers go, as the buyer said it: a Prague district ('Praha 5'), a quarter ('Vinohrady', 'Smíchov') or a street address. Omit when unknown.

Output parameters:

- `bouquet_id` (string)
- `name` (string)
- `slots` (object)

### `pinflower_get_order_status` (~96 tokens)

Order status

Use this when the buyer asks what is happening with an order placed here — whether it is paid, confirmed by the florist, on the way or delivered. Needs the order_ref returned when the order was created. Read-only: it changes nothing.

Input parameters:

- `locale` (string): The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
- `order_ref` (string, required)

Output parameters:

- `order_ref` (string)
- `paid` (boolean)
- `step` (string)

### `pinflower_new_pay_link` (~79 tokens)

Payment link again

Use this when the buyer has not paid yet and the order's payment link expired or got lost: it returns the order's payable link on pinflower.cz — the same one while it is still open (one order, one payable link). Needs the order_ref. Not for paid or cancelled orders.

Input parameters:

- `order_ref` (string, required)

Output parameters:

- `order_ref` (string)
- `pay_url` (string)

### `pinflower_quote_order` (~684 tokens)

Price the order

Use this when the buyer has chosen what to order and you have the details: it prices the order exactly as the checkout will charge it — the bouquet(s), add-ons, the shop's launch discount or the buyer's promo code, the delivery fee — and checks the time, without creating anything. Takes: the bouquet(s) (bouquet_id from search; several bouquets of ONE florist with quantities in items); delivery or pickup; for delivery the street address with house number in Prague; the recipient's name and phone when someone else receives the flowers; the date and a time (one of the bouquet's offered times, or 'asap'); the buyer's name, e-mail and phone (+420…); an optional card message and note for the florist; the buyer's promo code if they have one. Above 10 000 Kč the buyer's billing address is required. Also on offer: address_mode 'ask_recipient' when the florist should agree the address with the recipient by phone — a surprise (the recipient's name and phone are then required); time 'agree_with_recipient' when the florist should agree the time with the recipient by phone (the recipient's name and phone are then required); add-ons per bouquet (listed in the bouquet details); recipient.care_reminder=true — the free (0 Kč) care reminder for the recipient, offered once when someone else receives the flowers; company details (IČO) for a purchase by a company. Returns the breakdown, the total, the terms link and an order_intent; it creates nothing. The total is valid for exactly these details.

Input parameters:

- `address` (string): Delivery to a known address: street and house number in Prague.
- `address_mode` (string): ask_recipient = the courier/florist agrees the address with the recipient by phone (a surprise); no address needed, delivery priced at the whole-city rate.
- `billing_address` (string): The buyer's billing address — required by Czech tax rules when the order is over 10 000 Kč (unless buying for a company).
- `bouquet_id` (string): One bouquet (shortcut for items with a single line).
- `buyer` (object, required)
- `card_message` (string)
- `company` (object): Buying for a company — the invoice is issued to it.
- `courier_note` (string): Bell name, entrance, gate code.
- `date` (string, required): 'today', 'tomorrow' or YYYY-MM-DD.
- `florist_note` (string)
- `fulfilment` (string)
- `items` (array): Several bouquets from the SAME florist, with quantities.
- `locale` (string)
- `marketing_opt_in` (boolean): true = the buyer asked for news and offers.
- `promo_code` (string): The buyer's promo code, if they have one — works for guests and signed-in buyers alike; the checkout checks it.
- `recipient` (object): Who receives the flowers, when it is someone else than the buyer — the courier calls them.
- `time` (string, required): HH:MM from the offered times, or 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only).
- `unit` (string): Apartment, floor, company at the door.

Output parameters:

- `delivery_fee_czk` (number)
- `discount` (object)
- `goods_czk` (number)
- `next_step` (string)
- `terms_url` (string)
- `total_czk` (number)

### `pinflower_search_bouquets` (~612 tokens)

Find bouquets

Use this when the buyer wants flowers delivered in Prague (or picked up there) and you need concrete bouquets: it returns only bouquets that can really arrive at the given place and time, with price, delivery fee, total and the earliest delivery time, in the storefront's recommended order. Takes what the buyer said: free text, occasion, budget, where, date and a deliver-by time; without date and deliver_by every result carries its earliest time. Each call displays its results to the buyer as a carousel. Not for general flower advice or for orders outside Prague.

Input parameters:

- `budget_max_czk` (number): Bouquet price limit in CZK (delivery not included).
- `budget_min_czk` (number)
- `category` (string): A category slug as results show it (e.g. roses, tulips).
- `currency` (string): Add an approximate EUR/USD preview for a buyer abroad (default czk). The charge is always in CZK.
- `date` (string): Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
- `deliver_by` (string): HH:MM (24 h): must arrive by then. Without date it means today.
- `detail` (string): full adds composition and a short description (default short).
- `flowers` (array): Plant ids the bouquet must hold ANY of, as results show them under `flowers` (e.g. ["rosa"], ["rosa", "hydrangea"]). A plant covers its forms (spray roses are roses).
- `free_delivery` (boolean): Only bouquets whose delivery can be free: free for the address's zone when a place is given; before one, bouquets with a free path at some zone (the result's free_delivery says whether it IS free).
- `fulfilment` (string): delivery (default) or pickup at the florist's shop.
- `limit` (integer): How many results (default 6).
- `locale` (string): The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
- `occasion` (string): The occasion the buyer named.
- `query` (string): Free text in any language: flower, colour or bouquet name, e.g. 'red roses', 'tulipány', 'пионы'.
- `ready_now` (boolean): Only bouquets already made and waiting (fastest).
- `sort` (string): recommended (default, the storefront's order), cheapest, most expensive, or soonest arrival.
- `style` (string): as_pictured = looks like the photo; florists_style = composed fresh by the florist in that spirit.
- `where` (string): Where the flowers go, as the buyer said it: a Prague district ('Praha 5'), a quarter ('Vinohrady', 'Smíchov') or a street address. Omit when unknown.

Output parameters:

- `currency` (string)
- `empty` (object)
- `interpreted` (object)
- `results` (array)
- `total_found` (integer)

### `pinflower_store_info` (~104 tokens)

How Pinflower works

Use this when the buyer asks how ordering works: payment and when the card is charged, delivery area and fees, anonymous delivery and the card message, what happens if nobody is home, returns and complaints, or how to contact Pinflower. Answers come from the shop's own pages, with links. Does not cover bouquet availability.

Input parameters:

- `locale` (string): The buyer's language for names, texts and links: cs, en, ru or uk (default cs).

Output parameters:

- `facts` (object)
- `faq` (array)
- `links` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 80
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 80
- 2026-11-16: 80
- 2026-11-15: 80
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 80
- 2026-11-11: 80
- 2026-11-10: 79
- 2026-11-09: 80
- 2026-11-08: 80
- 2026-11-07: 80
- 2026-11-06: 80
- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79

## Common questions

### What is the Pinflower — flowers in Prague MCP server?

Pinflower — flowers in Prague is an MCP server listed in the public MCP registry as cz.pinflower/flowers. Order bouquets from independent Prague florists: live prices, delivery times, pay on pinflower.cz. This page covers its hosted endpoint (https://pinflower.cz/api/mcp).

### Is the Pinflower — flowers in Prague MCP server safe to use?

Pinflower — flowers in Prague scores 80 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 Pinflower — flowers in Prague MCP server expose?

Pinflower — flowers in Prague exposes 9 tools: pinflower_cancel_order, pinflower_check_delivery, pinflower_create_order, pinflower_get_bouquet, pinflower_get_order_status, and 4 more. Their descriptions and schemas cost roughly 2,932 tokens of context every time the server is loaded.

### Does the Pinflower — flowers in Prague MCP server require authentication?

No. We connected to Pinflower — flowers in Prague without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pinflower — flowers in Prague MCP server still maintained?

Pinflower — flowers in Prague is still listed as active in the MCP registry. We last reached this channel on 21 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 Pinflower — flowers in Prague MCP server?

VerifyMCP ran 14 checks on Pinflower — flowers in Prague, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.

## Links

- Remote endpoint: https://pinflower.cz/api/mcp
- Website: https://pinflower.cz/
- Changelog RSS feed: https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cz-pinflower-flowers/api-mcp
