Skip to content

SendaMeal Storefront MCP server

com.sendameal/storefrontsendameal.comstreamable-httpv1.0.0Scanned

Search gift meals and send them as gifts. Live catalog, cart, and guest checkout for SendaMeal.

6 tools: 1 can delete or cancel things, 3 change things and 2 only read.

Tools: 1 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 4 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SendaMeal Storefront MCP server can do

The SendaMeal Storefront MCP server is published by sendameal.com, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: remove_item_from_cart) and create or change data (3 tools: add_item_to_cart, create_checkout_url and update_cart_item). 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 4 findings, 1 of them high severity (long-description and model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Deletes or cancels 1Claude Code: deny
  • remove_item_from_cartRemove an item from the shopping cart.No findings

    Why it is in this group

    • The name "remove_item_from_cart" says "remove": a word for removing or ending something.
    Description, as the server wrote it
    Remove an item from the shopping cart. This tool removes the item completely. To lower the quantity, use the 'update_cart_item' tool. Steps 1. Call the 'add_item_to_cart' tool to put items in the cart. 2. Call this tool to remove an item. 3. Call the 'create_checkout_url' tool to get a checkout URL. Rules A cart with items must exist. Send 'item_id' to select the cart item to remove. It is the 'entityId' of that item in the cart that the last cart tool call returned, for example 'add_item_to_cart'. It is not 'productEntityId' or 'variantEntityId'.
Changes things 3Claude Code: ask
  • add_item_to_cartAdd one or more items to the shopping cart.1 finding

    Why it is in this group

    • The name "add_item_to_cart" says "add": a word for a change.

    Findings

    • Info

      The description is 4,853 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...that you did not send, or a value that does not belong to the option, causes it."

      What this check looks for
    Description, as the server wrote it
    Add one or more items to the shopping cart. If no cart exists, this tool makes a new cart. This tool adds products and gift certificates. Steps 1. Call the 'search_products' tool to find a product. 2. Call the 'get_product_details' tool to get the variants and the modifier options. 3. Call this tool to add the item. 4. Call the 'create_checkout_url' tool to get a checkout URL. The response returns the whole cart. Each item in 'cart.lineItems' has an 'entityId'. Use it as 'line_item_id' in the 'update_cart_item' tool. Use it as 'item_id' in the 'remove_item_from_cart' tool. Rules Send 'quantity' and 'productEntityId' for each item. If the configuration that the user chose has a variant, send 'variantEntityId'. Send 'variantEntityId' as null only for a configuration with no variant. See "Configurations with no variant" for when this is allowed. Modifier options A modifier option is a product choice that is not a variant. Examples are an engraving message and a nicotine strength. The 'get_product_details' tool returns these options in 'modifierOptions'. If the product has no 'modifierOptions' and you send a variant, do not send 'selectedOptions'. If you send a variant in 'variantEntityId', do not send a variant option in 'selectedOptions'. The variant sets those options. An option is required if 'isRequired' is 'true'. Send each required option. If you do not send a required option, the server does not add the item. To send an option: 1. Read the bucket name from 'selectedOptionsKey'. 2. Add the option to 'item.selectedOptions' in that bucket. 3. Send the 'optionEntityId' of the option. 4. For a choice option, send 'optionValueEntityId'. Its number is the 'valueEntityId' of the value that the user selected. Send only the buckets that you need. Example. A required choice option has a 'selectedOptionsKey' of "multipleChoices", an 'optionEntityId' of 108, and a selected value with a 'valueEntityId' of 251: { "item": { "quantity": 1, "productEntityId": 88, "variantEntityId": 67, "selectedOptions": { "multipleChoices": [ { "optionEntityId": 108, "optionValueEntityId": 251 } ] } } } A free-entry bucket takes a typed value in place of an ID. 'textFields' and 'multiLineTextFields' take "text". 'numberFields' takes "number". 'dateFields' takes "date". Obey the 'constraints' of the option. If a required option has more than one value, ask the user to select one value. Do not select a value yourself. Do not use the default value. If 'unsupported' is 'true', you cannot send the option. If such an option is also required, tell the user to buy the product on the website. Configurations with no variant A variant option value can have no variant. The default value, such as "None", is often one. The 'get_product_details' tool lists every value in 'variantOptions'. A value with 'hasVariant' of 'false' is used by no variant that can be bought. It has no variant, or its variants are not on sale now, for example because they are out of stock. Send 'variantEntityId' as null only if all of these are true: - The user chose a value with 'hasVariant' of 'false'. - 'variants' is not empty. If it is empty, every value has 'hasVariant' of 'false', and the product may not be on sale. Do not add the product. Tell the user. If every value that the user chose has 'hasVariant' of 'true', and no variant in 'variants' matches all of the values, that configuration does not exist. Do not add the base product in its place. Tell the user that the configuration is not available. If the store has no variant for the configuration, it adds the base product. If a variant exists but cannot be bought, the server rejects the item. Give that reason to the user. To add it: 1. Send 'variantEntityId' as null. 2. Send every variant option of the product in 'item.selectedOptions.multipleChoices'. Send the 'optionEntityId' of the option and the 'optionValueEntityId' of the value that the user selected. Send the options that have a variant too, not only the value that has none. 3. Send each required modifier option as usual. Example. Variant option 81 has the value 899, which has no variant. Required modifier option 108 has the value 251: { "item": { "quantity": 1, "productEntityId": 88, "variantEntityId": null, "selectedOptions": { "multipleChoices": [ { "optionEntityId": 81, "optionValueEntityId": 899 }, { "optionEntityId": 108, "optionValueEntityId": 251 } ] } } } If you leave out a variant option, the server rejects the item with the message "This product has options, variant ID is required". The message is misleading. A variant option that you did not send, or a value that does not belong to the option, causes it.
  • create_checkout_urlCreateResult a checkout URL for a cart assigned to a current session Arguments: None, but requires a cart to be present in the current session.No findings

    Why it is in this group

    • The name "create_checkout_url" says "create": a word for a change.
    Description, as the server wrote it
    CreateResult a checkout URL for a cart assigned to a current session Arguments: None, but requires a cart to be present in the current session. Returns: - checkoutURL - the URL to redirect the user to for checkout - errors - any errors encountered during the process (like, cart not found, etc.) Flow: - Call 'manage_cart' with 'create_cart' operation to create a new cart. - Call this tool to create a checkout URL for the cart assigned to the current session.
  • update_cart_itemChange an item that is already in the shopping cart.No findings

    Why it is in this group

    • The name "update_cart_item" says "update": a word for a change.
    Description, as the server wrote it
    Change an item that is already in the shopping cart. Use this tool to change the quantity, the variant, or the modifier options of one cart item. A cart must exist and must have items. Steps 1. Call the 'add_item_to_cart' tool to put an item in the cart. 2. Call this tool to change the item. 3. Call the 'create_checkout_url' tool to get a checkout URL. Rules Send 'line_item_id' to select the cart item to change. It is the 'entityId' of that item in the cart that the last cart tool call returned, for example 'add_item_to_cart'. It is not 'productEntityId' or 'variantEntityId'. Send 'quantity' and 'productEntityId' in 'item'. If the configuration that the user chose has a variant, send 'variantEntityId'. If it has no variant, see "Configurations with no variant" in the 'add_item_to_cart' tool. The same rules apply here, including when to send 'variantEntityId' as null. Modifier options 'item.selectedOptions' works as it works in the 'add_item_to_cart' tool. The 'get_product_details' tool returns these options in 'modifierOptions'. If the product has required modifier options, send them again in this request. If you do not send them, the server does not change the item. Send only the buckets that you need.
Only reads 2Show 2 read-only tools
  • get_product_detailsGet the details of one or more products.2 findings

    Why it is in this group

    • The name "get_product_details" says "get": a word for reading.

    Findings

    • High

      The description contains "do not tell the user", an instruction to keep something from the user.

      Matched text

      description: "...ants exist than the tool returned. Then do not tell the user that a variant does not exist. You did..."

      What this check looks for
    • Info

      The description is 5,851 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...exist. If a product has required modifier options, you must send those options."

      What this check looks for
    Description, as the server wrote it
    Get the details of one or more products. The details are the variants, the options, and the images. Arguments productIds - The list of product IDs. Get these IDs from the 'search_products' tool. Request only the products that the user needs. The server has a maximum count of IDs. The default maximum is 20. If you send too many IDs, the server returns an error. Then send fewer IDs. option_values - The option IDs and the value IDs of one variant. Use this argument with one product ID only. This argument applies to the B2C catalog. For a B2B buyer, the tool returns all the variants. Then select one variant. channelId - Optional. This argument selects the B2B catalog. The default is the channel of the request. variantCursor - Optional. This argument gets the next page of variants. Use this argument with one product ID only. Take the value from 'nextVariantCursor' in the previous result. If 'nextVariantCursor' is absent, or is null, or is the text "null", do not send this argument. Results The tool returns a list of products in 'products'. The output schema gives all the fields. A product has 'modifierOptions' only if the product has modifier options. A product has 'variantOptions' only if the product has variant options. A variant has a price, an inventory level, a purchase flag, and bulk prices only for a B2B buyer. If the tool does not find a product, the list does not include that product. Modifier options A modifier option is a product choice that is not a variant. Examples are an engraving message and a gift note. A variant option is never a modifier option. If a product has no 'modifierOptions', add the product to the cart without 'selectedOptions'. An option is required if 'isRequired' is 'true'. Send each required option to the 'add_item_to_cart' tool. If you do not send a required option, the server does not add the item. A variant selection does not replace a required option. Each option has 'optionEntityId', 'displayName', and 'selectedOptionsKey'. 'selectedOptionsKey' is the name of the field to send the option in. A choice option has 'values'. Each value has 'valueEntityId' and 'label'. A free-entry option has 'constraints' in place of 'values'. If 'unsupported' is 'true', you cannot send the option. A file upload is one example. If such an option is also required, tell the user to buy the product on the website. Variant options A variant option is a product choice that selects a variant. Examples are a size and a colour. The tool returns these options in 'variantOptions'. Each option has 'optionEntityId', 'displayName', 'isRequired', and 'values'. Each value has 'valueEntityId' and 'label'. The default value has 'isDefault'. A variant lists only the values that it uses. A value can have no variant. The default value, such as "None", is often one. 'variantOptions' lists every value, so use it to find a value that no variant lists. 'hasVariant' tells you if a variant in the list uses the value. The tool sets 'hasVariant' only if it returned the whole list of variants. That is when 'hasMoreVariants' is absent and you sent no 'option_values' and no 'variantCursor'. For a B2B buyer the tool always returns the whole list, and the list includes variants that cannot be bought. If 'hasVariant' is 'false', no variant that can be bought uses the value. The value has no variant, or its variants are not on sale now. If the list of variants is empty, every value has 'hasVariant' of 'false'. If 'hasVariant' is absent, you do not know. 'hasVariant' is about one value. If the product has more than one variant option, a combination of values can have no variant even if each value has one. Variant pages The list of variants can be one page of a longer list. The server sets the page size. If 'hasMoreVariants' is 'true', more variants exist than the tool returned. Then do not tell the user that a variant does not exist. You did not receive all the variants. To get the next page, call this tool again. Send the same product ID, and only that product ID. Send 'variantCursor' with the value of 'nextVariantCursor'. A filter is better than a page walk. If the user named the variant, send 'option_values' instead. One filtered call is cheaper than many pages. Do not change 'option_values' between pages. The cursor is a position in the list of the previous call. A different filter gives the wrong variants. Stock Each product has 'inStock'. It tells you if the store has units in stock. It does not tell you if the user can buy the product. If 'inStock' is 'false', do not refuse the request. Many stores accept orders for products that are not in stock. Tell the user that the product is not in stock, and that delivery can take more time. Then add the product if the user agrees. If the store blocks the purchase, the 'add_item_to_cart' tool fails and gives a reason. Give that reason to the user. If 'inStock' is 'true', the store reports no out-of-stock condition. A store that does not count stock reports 'true' for all products. Therefore do not tell the user a quantity. 'inventoryLevel' is present only if the store publishes stock counts. If 'inventoryLevel' is absent, the count is unknown. The count is not zero. Each variant has its own 'inStock'. Use the value of the variant if you add one variant. Steps 1. Call the 'search_products' tool to get the product IDs. 2. Call this tool with the product IDs. 3. Call the 'add_item_to_cart' tool with the results of step 1 and step 2. If the configuration that the user chose has a variant, you must tell the 'add_item_to_cart' tool which variant to add. If it has no variant, see "Configurations with no variant" in the 'add_item_to_cart' tool. Do not use that path for a configuration that does not exist. If a product has required modifier options, you must send those options.
  • search_productsSearch products by a term Arguments: term - the search term to look for products.1 finding

    Why it is in this group

    • The name "search_products" says "search": a word for reading.

    Findings

    • Info

      The description is 2,390 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...product to the cart. - [IMPORTANT] If product has variants ask user to pick"

      What this check looks for
    Description, as the server wrote it
    Search products by a term Arguments: term - the search term to look for products. It should be at least 3 characters long. cursor - optional, used for pagination. If provided, it will return the next page of results after. Pagination: Supports pagination with 'cursor' arguments. If 'cursor' is not provided, it will return the first page of results. Value for 'cursor' can be obtained from the 'nextCursor' field in the response. If 'nextCursor' is null, it means there are no more results to fetch. If value of cursor is null (or a string representation of 'null') dont send it in the payload. Results: Each product includes 'requiresFileUpload'. When true, the product has a required file-upload option (e.g. "upload your design") and shouldn't be added to cart through this assistant. Do not attempt to purchase it — tell the user it must be ordered on the website. Stock: Each product carries 'inStock'. It reports whether the store has units on hand. It does NOT report whether the item can be bought. - false does NOT mean the purchase will fail. Many stores accept orders for out-of-stock items - backorder, pre-order, or made-to-order goods that are fabricated after ordering. Whether a given store does is not exposed by this API. So: tell the user the item is out of stock and may take longer to arrive, then ADD IT if they still want it. Do not refuse on 'inStock: false' alone. - If the store really does block it, 'add_item_to_cart' fails and returns the reason. Relay that reason to the user. Attempting the add is the only reliable way to find out. - true only means no out-of-stock condition is reported. A store that does not track inventory reports true for every product, so never state or imply a quantity. - 'inventoryLevel' appears only on stores that publish stock figures; absent means undisclosed, not zero. Flow: - Call this tool with a 'term' argument and optionally with 'cursor' to search for products. - if you find a matching product, call 'get_product_details' with the product ID to get its variants and options (if any). - if 'requiresFileUpload' is true, inform the user the product needs a file upload and cannot be purchased here. - Call 'add_item_to_cart' with results of 'search_products' and 'get_product_details' (variant) tools to add the product to the cart. - [IMPORTANT] If product has variants ask user to pick

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://store-odebi8ye4k-1.mybigcommerce.com/api/mcp: tools/list returned 6 tools to an anonymous client, including remove_item_from_cart (destructive), add_item_to_cart (write), create_checkout_url (write), update_cart_item (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high3 info
  • The description contains "do not tell the user", an instruction to keep something from the user.

    Matched text

    description: "...ants exist than the tool returned. Then do not tell the user that a variant does not exist. You did..."

    What this check looks for
  • The description is 4,853 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...that you did not send, or a value that does not belong to the option, causes it."

    What this check looks for
  • The description is 5,851 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...exist. If a product has required modifier options, you must send those options."

    What this check looks for
  • The description is 2,390 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...product to the cart. - [IMPORTANT] If product has variants ask user to pick"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http storefront https://store-odebi8ye4k-1.mybigcommerce.com/api/mcp
claude mcp add --transport http storefront https://store-odebi8ye4k-1.mybigcommerce.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__storefront__get_product_details",
      "mcp__storefront__search_products"
    ],
    "ask": [
      "mcp__storefront__add_item_to_cart",
      "mcp__storefront__create_checkout_url",
      "mcp__storefront__update_cart_item"
    ],
    "deny": [
      "mcp__storefront__remove_item_from_cart"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as storefront. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.sendameal/storefront/verify?hash=fcf1f0d6ccb532e703d6bad55f9a366fbd9827e9b8ca0a19c9a65b8b3c67e722" | jq -e '.changed == false'

Pinned hash fcf1f0d6ccb5, from Nov 14, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.sendameal/storefront/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.sendameal/storefront
[![Anlyon Radar](https://radar.anlyon.com/badge/com.sendameal/storefront.svg)](https://radar.anlyon.com/servers/com.sendameal/storefront)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

SendaMeal Storefront MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SendaMeal Storefront MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 4 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SendaMeal Storefront MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: remove_item_from_cart.

Can the SendaMeal Storefront MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SendaMeal Storefront MCP server have?

6 tools: 1 destructive, 3 write, 2 read. remove_item_from_cart, add_item_to_cart, create_checkout_url, update_cart_item, get_product_details and search_products.

Does the SendaMeal Storefront MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SendaMeal Storefront MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SendaMeal Storefront MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.