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.

The Flowers Directory

REMOTE · WWW.THEFLOWERSDIRECTORY.COM

Send flowers in the US: search arrangements, same-day florist delivery by ZIP, checkout links

0 this week 77 Trust /100

Last scanned (23 hours ago)

Scores higher than 67% 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
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2122 tokens (~235/item across 9 items; 9 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% 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
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 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
  • 28 Oct 26 0
    • Tool “check_delivery” rewrote its description, which is the text the model reads security
    • Tool “search_arrangements” rewrote its description, which is the text the model reads security
    • Schema quality: 211 → 235 ▼ functional
    • Tool “check_delivery” now declares an output schema ▲ functional
    • Tool “create_prefilled_checkout” now declares an output schema ▲ functional
    • Tool “find_local_florists” now declares an output schema ▲ functional
    • Tool “get_arrangement_details” now declares an output schema ▲ functional
    • Tool “get_checkout_link” now declares an output schema ▲ functional
    • Tool “get_delivery_location_guidance” now declares an output schema ▲ functional
    • Tool “get_order_status” now declares an output schema ▲ functional
    • Tool “next_available_delivery” now declares an output schema ▲ functional
    • Tool “search_arrangements” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • “search_arrangements” added an optional parameter “arrangement_type” cosmetic
    • “search_arrangements” added an optional parameter “size” cosmetic
    • “search_arrangements” reworded the description of “flower_types” cosmetic
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 0
    • Tool “check_delivery” rewrote its description, which is the text the model reads security
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Tool “get_delivery_location_guidance” rewrote its description, which is the text the model reads security
    • “create_prefilled_checkout” reworded the description of “code” cosmetic
    • “get_arrangement_details” reworded the description of “code” cosmetic
    • “get_checkout_link” reworded the description of “code” cosmetic
  • 20 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_delivery” rewrote its description, which is the text the model reads security
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Tool “search_arrangements” rewrote its description, which is the text the model reads security
    • Schema quality: 254 → 216 ▲ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “create_prefilled_checkout” functional
    • New tool “find_local_florists” functional
    • New tool “get_arrangement_details” functional
    • New tool “get_delivery_location_guidance” functional
    • New tool “get_order_status” functional
    • New tool “next_available_delivery” functional
    • “search_arrangements” reworded the description of “query” cosmetic
    • Tool “check_delivery” changed its title: Check delivery availability → Check delivery on a date cosmetic
  • 28 Sept 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
  • 25 Sept 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
  • 24 Sept 26 0

    First indexed and scored.

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://www.theflowersdirectory.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.theflowersdirectory.com CN=WR1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 SHA256-RSA f57b11a1695890030ee0006ab2efe2d6
SANs: www.theflowersdirectory.com
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.theflowersdirectory.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
theflowersdirectory.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.theflowersdirectory.com/mcp Verified 200
http (plaintext) http://www.theflowersdirectory.com/mcp Inconclusive 405
MCP tools · 9 exposed · ~1,851 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
check_delivery ~121

Check whether florist delivery is available to a US ZIP code on one specific date. Availability is per ZIP and date, not per arrangement. Same-day delivery requires ordering before 1:00 PM in the recipient's local time zone, Monday through Saturday. When a date is unavailable, the result includes a reason (Sunday, past date or past the same-day cutoff) when one is known.

NameTypeReqDescription
datestringyesRequested delivery date, YYYY-MM-DD, in the recipient's local date.
zipstringyesRecipient 5-digit US ZIP code.
NameTypeReqDescription
availablebooleanyes–
datestringyes–
notestringyes–
reasonobject––
same_day_cutoffstringyes–
zipstringyes–

No examples provided.

create_prefilled_checkout ~320

Save delivery details for one arrangement on theflowersdirectory.com for 24 hours and return a checkout link that opens with the arrangement in the cart and those details filled in, plus the price breakdown (exact total when a ZIP is given). Takes the recipient's name, venue, room or unit, card message and special instructions, with the ZIP and delivery date. It does not place an order or take payment: the customer adds the street address and phone numbers, checks the details, pays and places the order on the site.

NameTypeReqDescription
card_messagestring–Message printed on the enclosure card, including who it is from.
clientstring–Name of the assistant or app making the request (used only for attribution, e.g. "chatgpt").
codestringyesArrangement product code, e.g. T163-1A.
datestring–Requested delivery date, YYYY-MM-DD. Requires zip. Selected at checkout if available.
recipient_namestring–Recipient's full name (for a funeral, e.g. "Family of Jane Smith").
room_or_unitstring–Apartment, suite, floor or hospital room number.
special_instructionsstring–Notes for the florist, e.g. the deceased's name and service time for a funeral.
venue_namestring–Funeral home, hospital, church or business name, if delivering to one.
zipstring–Recipient ZIP code; fills the ZIP field and gives an exact total including tax.
NameTypeReqDescription
checkout_urlstringyes–
deliveryobject––
expires_in_hoursnumberyes–
how_to_orderstringyes–
prefilled_fieldsarrayyes–
pricingobjectyes–
productobjectyes–
product_urlstringyes–

No examples provided.

find_local_florists ~146

List florists located in a US city from The Flowers Directory's city pages, with addresses, phone numbers when listed, and the date each listing was last verified. These are directory listings: an order placed through The Flowers Directory is made and delivered by a florist in the Florist One network, which may or may not be one of the listed shops.

NameTypeReqDescription
citystring–City name, e.g. "Worcester".
limitinteger––
statestring–State name or 2-letter code, e.g. "MA".
zipstring–ZIP code; used to find the city when no city is given.
NameTypeReqDescription
citystringyes–
city_pagestring|nullyes–
floristsarrayyes–
location_notestring––
notestringyes–
statestringyes–
total_listedintegeryes–

No examples provided.

get_arrangement_details ~91

Return full details for one arrangement by product code: all photos, size (height x width when the florist network publishes it), full description, flowers and colors, occasions it suits, price and total before tax, the substitution policy, and delivery terms. Use it to show a customer exactly what they are buying.

NameTypeReqDescription
codestringyesArrangement product code, e.g. T163-1A.
NameTypeReqDescription
attributesobject––
best_forstring––
categoriesarrayyes–
codestring––
colorsarray––
deliveryobjectyes–
delivery_feenumberyes–
descriptionstring––
flower_typesarray––
imagestring|null––
imagesarrayyes–
notestring––
occasionsarray––
pricenumberyes–
product_urlstring––
sizestring––
substitution_policystringyes–
titlestring––
total_before_taxnumberyes–
urlstring––

No examples provided.

get_checkout_link ~165

Return the purchase link for an arrangement plus a price breakdown. With a recipient ZIP the breakdown includes the exact delivery fee, tax and order total; with a ZIP and date it also confirms delivery availability. Opening the link adds the arrangement to the cart and opens the cart panel; the customer clicks Checkout and enters the recipient address, delivery date, card message and payment there.

NameTypeReqDescription
clientstring–Name of the assistant or app making the request (used only for attribution, e.g. "chatgpt").
codestringyesArrangement product code, e.g. T163-1A.
datestring–Requested delivery date, YYYY-MM-DD. Requires zip.
zipstring–Recipient ZIP code, for an exact total including tax.
NameTypeReqDescription
checkout_urlstringyes–
deliveryobject––
how_to_orderstringyes–
pricingobjectyes–
productobjectyes–

No examples provided.

get_delivery_location_guidance ~227

Return practical guidance for sending flowers to a specific kind of place: funeral_home, place_of_worship, hospital, residence, business, senior_living. Covers which arrangement types are appropriate and which to avoid, venue rules (such as hospital units that do not allow flowers), what details the florist needs, which checkout field each detail goes in, timing, and suggested search filters. With a city and state or ZIP, also lists funeral homes (for funeral_home) or hospitals (for hospital) in that city from the directory, with addresses.

NameTypeReqDescription
citystring–City name, for local venue listings.
limitinteger–Maximum venue listings to return.
location_typestringyesOne of: funeral_home, place_of_worship, hospital, residence, business, senior_living. Common words such as church, nursing home, office or home are accepted.
statestring–State name or 2-letter code, used with city.
zipstring–ZIP code; used to find the city when no city is given.
NameTypeReqDescription
appropriatearray––
avoidarray––
budget_notestring––
checkout_fieldsobject––
collectarray––
guidesarray––
labelstringyes–
local_venuesobject––
location_typestringyes–
suggested_searchesarray––
timingstring––

No examples provided.

get_order_status ~118

Look up an existing order placed on The Flowers Directory, using the order number from the confirmation email and the email address used at checkout. Returns the items, scheduled delivery date, delivery city and whether that date is upcoming, today or past. It does not provide live courier tracking; for delivery confirmation, changes or cancellations it returns the order-help phone and text numbers.

NameTypeReqDescription
emailstringyesEmail address the purchaser used at checkout.
order_numberstringyesOrder number from the confirmation email, e.g. 123456789.
NameTypeReqDescription
itemsarrayyes–
order_helpobjectyes–
order_numberstringyes–
order_totalnumber|nullyes–
trackingstringyes–

No examples provided.

next_available_delivery ~74

List up to 14 upcoming delivery dates available to a US ZIP code, with the earliest date, whether same-day delivery is still possible right now in the recipient's local time (1:00 PM cutoff), and how long is left before the cutoff.

NameTypeReqDescription
zipstringyesRecipient 5-digit US ZIP code.
NameTypeReqDescription
available_datesarrayyes–
delivery_daysstring––
delivery_feenumber––
earliest_datestring|nullyes–
earliest_labelstring|null––
notestringyes–
recipient_local_timestring|null––
same_dayobject––
statestring|nullyes–
zipstringyes–

No examples provided.

search_arrangements ~589

Search The Flowers Directory catalog of fresh flower arrangements and plants for US florist delivery, by occasion (birthday, sympathy/funeral, get well, anniversary, romance, new baby, thank you and more), color, flower type, arrangement type (vase, basket, standing spray, wreath, casket spray and more), size, budget and free text. Every result includes the product code used by the other tools, the arrangement price, a photo URL, total_before_tax (price plus the flat $19.99 delivery fee) and, when known, structured attributes: arrangement type, size tier, height and width in inches, stem count, container and who it suits (sender_fit). Returns up to 20 matches, best match first.

NameTypeReqDescription
arrangement_typestring–One of: vase_arrangement, basket, floor_basket, table_arrangement, centerpiece, plant, dish_garden, wreath, standing_spray, standing_heart, standing_cross, casket_spray, casket_adornment, urn_tribute…
budgetnumber–Maximum all-in amount in USD before tax (arrangement price + $19.99 delivery). Use this for "around $110"-style requests.
colorsarray–Colors that should appear in the arrangement (any match). Known values: red, pink, white, yellow, purple, lavender, orange, blue, green, cream, peach, coral, burgundy, gold, mixed.
flower_typesarray–Flower types that should appear (any match). Known values: roses, lilies, tulips, sunflowers, orchids, carnations, daisies, hydrangeas, alstroemeria, chrysanthemums, gerberas, lisianthus, snapdragons…
limitinteger––
min_pricenumber–Minimum arrangement price in USD.
occasionstring–One of: sympathy, birthday, romance, anniversary, get_well, new_baby, thank_you, mothers_day, congratulations, wedding, just_because. "funeral" is accepted as sympathy.
querystring–Free-text keywords matched against the title and description, e.g. "blue hydrangea in a vase" or "standing spray".
sizestring–One of: small (under 14 in), medium (14 to 22 in), large (over 22 in), tribute (easel, casket and floor pieces for funerals).
NameTypeReqDescription
countintegeryes–
currencystringyes–
delivery_feenumberyes–
filtersobjectyes–
notestring––
productsarrayyes–
total_matchesintegeryes–

No examples provided.

Install

How do I install the The Flowers Directory MCP server?

The Flowers Directory is a hosted endpoint at https://www.theflowersdirectory.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 · www.theflowersdirectory.com

# add to Claude Code
claude mcp add --transport http com-theflowersdirectory-flowers 'https://www.theflowersdirectory.com/mcp'
Common questions

What is the The Flowers Directory MCP server?

The Flowers Directory is an MCP server listed in the public MCP registry as com.theflowersdirectory/flowers. Send flowers in the US: search arrangements, same-day florist delivery by ZIP, checkout links. This page covers its hosted endpoint (https://www.theflowersdirectory.com/mcp).

Is the The Flowers Directory MCP server safe to use?

The Flowers Directory scores 77 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 The Flowers Directory MCP server expose?

The Flowers Directory exposes 9 tools: search_arrangements, get_arrangement_details, check_delivery, next_available_delivery, get_checkout_link, and 4 more. Their descriptions and schemas cost roughly 1,851 tokens of context every time the server is loaded.

Does the The Flowers Directory MCP server require authentication?

No. We connected to The Flowers Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Flowers Directory MCP server still maintained?

The Flowers Directory 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 The Flowers Directory MCP server?

VerifyMCP ran 12 checks on The Flowers Directory, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about The Flowers Directory: HTTPS. 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.