Israel Flower
REMOTE · ISRAELFLOWER.COM
Send flowers in Israel: browse bouquets, check delivery days, get a quote and place an order in USD.
Available components
Last scanned (10 hours ago)
Scores higher than 76% 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 706 tokens (~117/item across 6 items; 6 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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 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.
- 3 Nov 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.
- 1 Nov 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.
- 30 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.
- 29 Oct 26 0
- Schema quality: pass → fail ▼ functional
- “create_order” reworded the description of “delivery_notes” cosmetic
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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://israelflower.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=israelflower.com | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 6e22ffadaf6d30c819854b4e0b49752a06b |
| SANs: israelflower.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of israelflower.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| israelflower.com. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://israelflower.com/mcp | Verified | 200 | |
| http (plaintext) | http://israelflower.com/mcp | HTTPS enforced | 308 | https://israelflower.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 Place an order ~238
Place an order and get its payment link. The order is held but not taken until the person pays at that link (card, in US dollars, on AllPay's secure page); give them the link and the total. Never pay on their behalf unless they asked you to and gave you the means. Confirm the recipient, address, phone, date and card message with the person first.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street, number, apartment, floor, entrance code. |
| buyer_email | string | yes | Where the receipt and any questions go. |
| buyer_name | string | yes | The person paying. |
| buyer_phone | string | – | – |
| card_message | string | – | Printed on the card with the flowers. |
| city | string | yes | – |
| coupon | string | – | – |
| delivery_date | string | yes | – |
| delivery_notes | string | – | Notes for the team: the florist and the courier. |
| recipient_name | string | yes | – |
| recipient_phone | string | yes | Israeli or international number, digits only. |
| slug | string | yes | – |
| surprise | boolean | – | True: do not contact the recipient before delivery. |
No output schema declared.
No examples provided.
delivery_options Check delivery cities and days ~82
Where and when we deliver: the cities, the delivery price, the next delivery dates with any day surcharge, and the rules (no Shabbat or Jewish festival days, 11:00-19:00 Israel time). Pass a date to check that day.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| date | string | – | A date to check, in Israel. |
No output schema declared.
No examples provided.
get_bouquet Get bouquet details ~40
Everything about one bouquet: description, flowers, colours, occasions, price, all photos.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | From search_bouquets. |
No output schema declared.
No examples provided.
order_status Check order status ~56
The status of an order (awaiting payment, paid, delivered, cancelled), by order number and the buyer's email.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_email | string | yes | The email the order was placed with. |
| order_number | integer | yes | – |
No output schema declared.
No examples provided.
quote Quote an order ~59
The exact total for a bouquet delivered to a city on a date, with any coupon, before placing the order.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| coupon | string | – | – |
| delivery_date | string | yes | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
search_bouquets Search bouquets ~105
List the bouquets for sale, with price in US dollars, photo and page link. Filter by occasion, colour, budget or words. Every bouquet is made by hand by a florist in Tel Aviv.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | – |
| max_price_usd | number | – | Bouquet price, before delivery. |
| occasion | string | – | For example birthday, shabbat, anniversary. |
| text | string | – | Words to look for in the name, description or flowers. |
No output schema declared.
No examples provided.
How do I install the Israel Flower MCP server?
Israel Flower is a hosted endpoint at https://israelflower.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 · israelflower.com
claude mcp add --transport http com-israelflower-flowers 'https://israelflower.com/mcp'
What is the Israel Flower MCP server?
Israel Flower is an MCP server listed in the public MCP registry as com.israelflower/flowers. Send flowers in Israel: browse bouquets, check delivery days, get a quote and place an order in USD. This page covers its hosted endpoint (https://israelflower.com/mcp).
Is the Israel Flower MCP server safe to use?
Israel Flower scores 78 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 Israel Flower MCP server expose?
Israel Flower exposes 6 tools: search_bouquets, get_bouquet, delivery_options, quote, create_order, order_status. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Does the Israel Flower MCP server require authentication?
No. We connected to Israel Flower without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Israel Flower MCP server still maintained?
Israel Flower 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.
What did VerifyMCP test on the Israel Flower MCP server?
VerifyMCP ran 13 checks on Israel Flower, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.