Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pinflower — flowers in Prague

REMOTE · PINFLOWER.CZ

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

Available components

0 this week 80 Trust /100

Last scanned (21 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • 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 security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 0
    • “pinflower_search_bouquets” added an optional parameter “flowers” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 25 Oct 26 +1
    • Stability: 0.97 → pass security
  • 18 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 17 Oct 26 0
    • 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 security
    • Schema quality: excellent → good functional
Diagnostics

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 21 Nov 2026 · Probed https://pinflower.cz/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pinflower.cz CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 95b6687b93c5bfb50eaa8629ba9aa07e
SANs: pinflower.cz, www.pinflower.cz, *.www.pinflower.cz
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 pinflower.cz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cz. DS published 20237 13 Verified
pinflower.cz. No DS 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=15552000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pinflower.cz/api/mcp Verified 200
http (plaintext) http://pinflower.cz/api/mcp HTTPS enforced 301 https://pinflower.cz/api/mcp
MCP tools · 9 exposed · ~2,932 tokens

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 →

Tool Tokens
pinflower_cancel_order ~156

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.

NameTypeReqDescription
codestring–The 6-digit code from the e-mail (second call).
confirmbooleanyestrue = the buyer confirmed they want to cancel.
order_refstringyes–
NameTypeReqDescription
cancelledbooleanyes–
code_sent_tostring––
order_refstringyes–
refunded_czknumber|null––

No examples provided.

pinflower_check_delivery ~180

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.

NameTypeReqDescription
datestring–Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
localestring–The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
wherestringyesWhere 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.
NameTypeReqDescription
can_deliverbooleanyes–
delivery_fee_from_czknumber|null––
earliestobject|null––
floristsinteger––
night_deliveryboolean––
placestring––

No examples provided.

pinflower_create_order ~789

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.

NameTypeReqDescription
addressstring–Delivery to a known address: street and house number in Prague.
address_modestring–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_addressstring–The buyer's billing address — required by Czech tax rules when the order is over 10 000 Kč (unless buying for a company).
bouquet_idstring–One bouquet (shortcut for items with a single line).
buyerobjectyes–
card_messagestring––
companyobject–Buying for a company — the invoice is issued to it.
confirmed_total_czkintegeryesThe quoted total_czk the buyer agreed to — a different total refuses the order.
courier_notestring–Bell name, entrance, gate code.
datestringyes'today', 'tomorrow' or YYYY-MM-DD.
florist_idstring–The florist — required when the order is a custom bouquet alone.
florist_notestring––
fulfilmentstring––
itemsarray–Several bouquets from the SAME florist, with quantities.
localestring––
marketing_opt_inboolean–true = the buyer asked for news and offers.
order_intentstringyesThe 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_codestring–The buyer's promo code, if they have one — works for guests and signed-in buyers alike; the checkout checks it.
recipientobject–Who receives the flowers, when it is someone else than the buyer — the courier calls them.
terms_acceptedbooleanyestrue = the buyer agreed to the terms.
timestringyesHH:MM from the offered times, or 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only).
unitstring–Apartment, floor, company at the door.
NameTypeReqDescription
order_numberinteger|null––
order_refstringyes–
pay_urlstringyes–
total_czknumberyes–

No examples provided.

pinflower_get_bouquet ~232

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.

NameTypeReqDescription
bouquet_idstringyes–
datestring–Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
fulfilmentstring–delivery (default) or pickup at the florist's shop.
localestring–The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
wherestring–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.
NameTypeReqDescription
bouquet_idstringyes–
namestringyes–
slotsobject––

No examples provided.

pinflower_get_order_status ~96

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.

NameTypeReqDescription
localestring–The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
order_refstringyes–
NameTypeReqDescription
order_refstringyes–
paidbooleanyes–
stepstringyes–

No examples provided.

pinflower_new_pay_link ~79

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.

NameTypeReqDescription
order_refstringyes–
NameTypeReqDescription
order_refstringyes–
pay_urlstringyes–

No examples provided.

pinflower_quote_order ~684

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.

NameTypeReqDescription
addressstring–Delivery to a known address: street and house number in Prague.
address_modestring–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_addressstring–The buyer's billing address — required by Czech tax rules when the order is over 10 000 Kč (unless buying for a company).
bouquet_idstring–One bouquet (shortcut for items with a single line).
buyerobjectyes–
card_messagestring––
companyobject–Buying for a company — the invoice is issued to it.
courier_notestring–Bell name, entrance, gate code.
datestringyes'today', 'tomorrow' or YYYY-MM-DD.
florist_notestring––
fulfilmentstring––
itemsarray–Several bouquets from the SAME florist, with quantities.
localestring––
marketing_opt_inboolean–true = the buyer asked for news and offers.
promo_codestring–The buyer's promo code, if they have one — works for guests and signed-in buyers alike; the checkout checks it.
recipientobject–Who receives the flowers, when it is someone else than the buyer — the courier calls them.
timestringyesHH:MM from the offered times, or 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only).
unitstring–Apartment, floor, company at the door.
NameTypeReqDescription
delivery_fee_czknumberyes–
discountobject––
goods_czknumberyes–
next_stepstringyes–
terms_urlstringyes–
total_czknumberyes–

No examples provided.

pinflower_search_bouquets ~612

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.

NameTypeReqDescription
budget_max_czknumber–Bouquet price limit in CZK (delivery not included).
budget_min_czknumber––
categorystring–A category slug as results show it (e.g. roses, tulips).
currencystring–Add an approximate EUR/USD preview for a buyer abroad (default czk). The charge is always in CZK.
datestring–Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
deliver_bystring–HH:MM (24 h): must arrive by then. Without date it means today.
detailstring–full adds composition and a short description (default short).
flowersarray–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_deliveryboolean–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).
fulfilmentstring–delivery (default) or pickup at the florist's shop.
limitinteger–How many results (default 6).
localestring–The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
occasionstring–The occasion the buyer named.
querystring–Free text in any language: flower, colour or bouquet name, e.g. 'red roses', 'tulipány', 'пионы'.
ready_nowboolean–Only bouquets already made and waiting (fastest).
sortstring–recommended (default, the storefront's order), cheapest, most expensive, or soonest arrival.
stylestring–as_pictured = looks like the photo; florists_style = composed fresh by the florist in that spirit.
wherestring–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.
NameTypeReqDescription
currencystring––
emptyobject––
interpretedobjectyes–
resultsarrayyes–
total_foundintegeryes–

No examples provided.

pinflower_store_info ~104

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.

NameTypeReqDescription
localestring–The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
NameTypeReqDescription
factsobject––
faqarrayyes–
linksobjectyes–

No examples provided.

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.

remote · pinflower.cz

# add to Claude Code
claude mcp add --transport http cz-pinflower-flowers 'https://pinflower.cz/api/mcp'
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.