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.

JENNi Shop Local

REMOTE · SHOP.JENNIPRO.COM

Search local-shop and ship-to-home products by US ZIP and get a JENNi checkout link.

64 Trust /100

Last scanned (8 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 25 Oct 2026.

Category E-commerce

Recent critical change

Authorization (23 Oct 2026). See the changelog before you install this server.

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 Security60
Transport & Reachability100
Schema Quality & AI Usability77
  • 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 1624 tokens (~147/item across 11 items; 8 tools + 3 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 Management0
  • Stability check failed: schema churn in the 5 days we've observed: 1 tool removals, 2 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% 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 8 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
Capabilities73
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
  • Supports UI / widget rendering.Pass
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.

  • 25 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “start_checkout” rewrote its description, which is the text the model reads security
    • “start_checkout” added an optional parameter “items” cosmetic
    • “start_checkout” added an optional parameter “quantity” cosmetic
    • “start_checkout” added an optional parameter “zip” cosmetic
    • “start_checkout” made “delivery_address” optional cosmetic
    • “start_checkout” made “product_id” optional cosmetic
  • 24 Oct 26 0
    • Resource “product-widget” now points somewhere else: ui://jenni/product-v1 → ui://jenni/product-v2 security
    • Resource “results-widget” now points somewhere else: ui://jenni/results-v1 → ui://jenni/results-v2 security
    • Resource “stores-widget” now points somewhere else: ui://jenni/stores-v1 → ui://jenni/stores-v2 security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • “search_catalog” added an optional parameter “max_price” cosmetic
  • 23 Oct 26 −4
    • Authorization: partial → fail ▼ critical
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • Tool “find_stores” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “complete_checkout”, which the server declares destructive security
    • Tool “get_buying_options” rewrote its description, which is the text the model reads security
    • Tool “get_order_status” rewrote its description, which is the text the model reads security
    • Tool “get_product” rewrote its description, which is the text the model reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • Tool coverage: 74% → 55% ▼ functional
    • Schema quality: 181 → 125 ▲ functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • New resource “product-widget” functional
    • New resource “results-widget” functional
    • New resource “stores-widget” functional
    • New tool “create_checkout” functional
    • New tool “update_checkout” functional
    • “search_catalog” added an optional parameter “fulfillment_mode” cosmetic
    • “search_catalog” added an optional parameter “page” cosmetic
    • “start_checkout” reworded the description of “fulfillment_mode” cosmetic
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_stores” rewrote its description, which is the text the model reads security
    • Tool “get_buying_options” rewrote its description, which is the text the model reads security
    • Tool “get_order_status” rewrote its description, which is the text the model reads security
    • Tool “get_product” rewrote its description, which is the text the model reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • Tool “start_checkout” rewrote its description, which is the text the model reads security
    • “start_checkout” added a required parameter “delivery_address”, so existing callers break ▼ functional
    • “start_checkout” dropped the required parameter “quantity” ▼ functional
    • “start_checkout” dropped the required parameter “zip” ▼ functional
    • Schema quality: 277 → 181 ▲ functional
    • Server version: 1.1.0 → 2.0.0 functional
    • “find_stores” reworded the description of “zip” cosmetic
    • “get_product” reworded the description of “zip” cosmetic
    • “start_checkout” reworded the description of “fulfillment_mode” cosmetic
    • “start_checkout” dropped the optional parameter “store_id” cosmetic
  • 21 Oct 26 +1
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.1.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_stores” rewrote its description, which is the text the model reads security
    • Tool “get_product” rewrote its description, which is the text the model reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • Tool “start_checkout” rewrote its description, which is the text the model reads security
    • “search_catalog” made “query” required, so existing callers break ▼ functional
    • Tool coverage: 65% → 76% ▲ functional
    • New tool “get_order_status” functional
    • “get_product” added an optional parameter “market” cosmetic
    • “search_catalog” added an optional parameter “market” cosmetic
    • “get_product” reworded the description of “zip” cosmetic
    • “search_catalog” reworded the description of “limit” cosmetic
    • “search_catalog” reworded the description of “query” cosmetic
    • “search_catalog” reworded the description of “zip” cosmetic
    • “start_checkout” reworded the description of “store_id” cosmetic
    • “get_product” dropped the optional parameter “postal_code” cosmetic
    • “search_catalog” dropped the optional parameter “brand” cosmetic
    • “search_catalog” dropped the optional parameter “cursor” cosmetic
    • “search_catalog” dropped the optional parameter “gtin” cosmetic
    • “search_catalog” dropped the optional parameter “postal_code” cosmetic
    • “search_catalog” dropped the optional parameter “product_id” cosmetic
    • “search_catalog” dropped the optional parameter “store_id” cosmetic
    • “search_catalog” dropped the optional parameter “store_ids” cosmetic
    • “start_checkout” made “store_id” optional cosmetic
    • Tool “find_stores” changed its title: Find a shop → Find a shop by name cosmetic
    • Tool “search_catalog” changed its title: Search local shops → Search products cosmetic
  • 20 Oct 26 67

    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 25 Oct 2026 · Probed https://shop.jennipro.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=shop.jennipro.com CN=YR2,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 RSA 2048 SHA256-RSA 55771df706e59d67c3576113ed6e6a90a54
SANs: shop.jennipro.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 secure

Validation of shop.jennipro.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jennipro.com. present 14926 8 Verified
shop.jennipro.com. Verified address RRset verified with the apex keys
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://shop.jennipro.com/mcp Verified 200
http (plaintext) http://shop.jennipro.com/mcp HTTPS enforced 301 https://shop.jennipro.com/mcp
MCP tools · 8 exposed · ~1,193 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
complete_checkout ~113

Place the order. Only after the shopper has approved the total from update_checkout. Pays with the shopper's Stripe shared payment token (spt_...), issued for at least the order total. Never send card numbers. Delivered by JENNi.

NameTypeReqDescription
checkout_idstringyes–
idempotency_keystring–Optional. Reuse the same value to retry safely; the retry returns the first result instead of acting twice.
payment_tokenstringyesStripe shared payment token, starting spt_.
NameTypeReqDescription
checkout_idstring|nullyes–
continue_urlstring–Present when the shopper should finish on JENNi instead.
currencystring––
expires_atstring|null––
fulfilled_bystringyes–
fulfillment_optionsarrayyes–
line_itemsarray––
messagesarrayyes–
next_stepstringyes–
order_idstring|null––
reason_codestring––
selected_fulfillment_modestring|null––
statusstringyesincomplete, ready_for_complete, requires_escalation, completed or canceled.
totalsobjectyes–

No examples provided.

create_checkout ~127

Start an order JENNi will deliver, without leaving the chat. Give the exact product_id, the delivery address and the shopper's contact details. Returns the delivery options and the order total. Nothing is charged until complete_checkout. Delivered by JENNi.

NameTypeReqDescription
buyerobjectyes–
delivery_addressobjectyes–
idempotency_keystring–Optional. Reuse the same value to retry safely; the retry returns the first result instead of acting twice.
product_idstringyes–
quantityinteger–How many (default 1).
NameTypeReqDescription
checkout_idstring|nullyes–
continue_urlstring–Present when the shopper should finish on JENNi instead.
currencystring––
expires_atstring|null––
fulfilled_bystringyes–
fulfillment_optionsarrayyes–
line_itemsarray––
messagesarrayyes–
next_stepstringyes–
order_idstring|null––
reason_codestring––
selected_fulfillment_modestring|null––
statusstringyesincomplete, ready_for_complete, requires_escalation, completed or canceled.
totalsobjectyes–

No examples provided.

get_buying_options ~80

Price, delivery promise and total before tax for one product_id, ZIP, quantity and mode (local_delivery or ship_to_home). Call it when the shopper picks a product, before quoting a total.

NameTypeReqDescription
fulfillment_modestringyes–
product_idstringyes–
quantityintegeryes–
zipstringyes–
NameTypeReqDescription
availablebooleanyesTrue when this mode can be ordered for this product, ZIP and quantity.
delivery_promisestring–Local delivery: "Get it today" or "We'll deliver by <Month D>". Ship-to-home: "Ships to you".
fulfillment_modestringyes–
notestring––
pricingobject–unit_price x quantity + fee = total_before_tax. Sales tax is added at checkout.
product_idstringyes–
reason_codestring–Why this mode cannot be bought here now.
titlestring––
unit_pricestring––

No examples provided.

get_order_status ~88

Read where a JENNi order stands: status, delivery ETA when known, courier tracking and whether the card was charged. Requires the private order_token from the shopper’s JENNi order page (starts jos1_). Read-only; it shows no personal details.

NameTypeReqDescription
order_tokenstringyesThe order token from the shopper's JENNi order page, starting jos1_.
NameTypeReqDescription
etastring|nullyesDelivery estimate when JENNi has one; null means not known yet.
itemsarrayyes–
next_stepstringyes–
order_statestring|nullyes–
paymentobjectyes–
refund_statestringyes–
statusstringyes–
trackingarrayyes–
updated_atstring|null––

No examples provided.

get_product ~85

Details for one product_id: description, images, sizes and colours, and its price and delivery at the ZIP.

NameTypeReqDescription
marketstring–Market key, e.g. san-antonio-tx. Used when no zip is given.
product_idstringyes–
zipstring–5-digit US ZIP code, for local prices and delivery options.
NameTypeReqDescription
productobjectyes–

No examples provided.

search_catalog ~332

Search in-stock products JENNi can deliver to a 5-digit US ZIP: local delivery first, then ship-to-home. Every product returned can be ordered; price is per unit, before the delivery or shipping fee. A product with variants and no price is a size or colour family: buy one of its variants. Sized goods are often listed one size per product: put the size in the query and match it against size or title. Put a price limit in max_price, not the query; keep the query to brand, product type and size. If it returns product_not_found, search once more with fewer words before telling the shopper nothing matched. Pass fulfillment_mode to search one mode. More results: call again with page+1 while page < paging.total_pages.

NameTypeReqDescription
fulfillment_modestring–Search one mode only. Omit to list local delivery first, filled with ship-to-home.
limitinteger–Products to return (default 10).
marketstring–Market key, e.g. san-antonio-tx. Used when no zip is given.
max_pricenumber–Highest price the shopper will pay, in US dollars, e.g. 120. Put a price limit here, not in the query.
pageinteger–1-based results page; call again with page+1 while page < paging.total_pages.
querystringyesWhat the shopper wants, e.g. "running shoes".
zipstring–5-digit US ZIP code the shopper is in, e.g. 78205.
NameTypeReqDescription
notestring–What could not be checked (for example local delivery): that availability is unknown, not unavailable.
pagingobject––
productsarrayyes–
reason_codestring–Present only when products is empty.

No examples provided.

start_checkout ~245

Returns a hosted checkout_url for an exact product and selected fulfillment mode using the delivery ZIP or address. For several products, pass items instead of product_id: one checkout_url puts them all in one basket. JENNi selects the source internally. The buyer reviews delivery, tax and the total, enters payment details, and places the order on the hosted page. This read-only tool creates no order, reservation or charge. The final checkout page verifies current price and availability.

NameTypeReqDescription
delivery_addressobject–Delivery destination. Address details are not placed in the checkout URL.
fulfillment_modestringyesSelected fulfillment mode: local_delivery arrives on the delivery date the buying-options read returns (delivery_promise / deliver_by); ship_to_home ships to the delivery address.
itemsarray–Several products in one link, instead of product_id. Same fulfillment_mode and ZIP for all.
product_idstring–The exact item: a variant's product_id when it has variants.
quantityinteger–How many of product_id (default 1).
zipstring–5-digit US delivery ZIP code, when no delivery_address is given.
NameTypeReqDescription
checkout_urlstringyes–
delivery_promisestring–Local delivery: "Get it today" or "We'll deliver by <Month D>". Ship-to-home: "Ships to you".
fulfillment_modestring––
itemstring––
itemsarray––
next_stepstringyes–
pricingobject–unit_price x quantity + fee = total_before_tax. Sales tax is added at checkout.
product_idstring––
quantityinteger––
reason_codestring–Machine-readable reason, alongside the prose note.
unit_pricestring––

No examples provided.

update_checkout ~123

Choose local_delivery or ship_to_home, or change the quantity, address or contact details of an order started with create_checkout. Call with only checkout_id to re-read it. Returns the order total once a delivery option is chosen.

NameTypeReqDescription
buyerobject––
checkout_idstringyes–
delivery_addressobject––
fulfillment_modestring––
idempotency_keystring–Optional. Reuse the same value to retry safely; the retry returns the first result instead of acting twice.
quantityinteger––
NameTypeReqDescription
checkout_idstring|nullyes–
continue_urlstring–Present when the shopper should finish on JENNi instead.
currencystring––
expires_atstring|null––
fulfilled_bystringyes–
fulfillment_optionsarrayyes–
line_itemsarray––
messagesarrayyes–
next_stepstringyes–
order_idstring|null––
reason_codestring––
selected_fulfillment_modestring|null––
statusstringyesincomplete, ready_for_complete, requires_escalation, completed or canceled.
totalsobjectyes–

No examples provided.

Install

How do I install the JENNi Shop Local MCP server?

JENNi Shop Local is a hosted endpoint at https://shop.jennipro.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 · shop.jennipro.com

# add to Claude Code
claude mcp add --transport http com-jennipro-shop-shop-local 'https://shop.jennipro.com/mcp'
Common questions

What is the JENNi Shop Local MCP server?

JENNi Shop Local is an MCP server listed in the public MCP registry as com.jennipro.shop/shop-local. Search local-shop and ship-to-home products by US ZIP and get a JENNi checkout link. This page covers its hosted endpoint (https://shop.jennipro.com/mcp).

Is the JENNi Shop Local MCP server safe to use?

JENNi Shop Local scores 64 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 JENNi Shop Local MCP server expose?

JENNi Shop Local exposes 8 tools: search_catalog, get_product, start_checkout, get_buying_options, get_order_status, and 3 more. Their descriptions and schemas cost roughly 1,193 tokens of context every time the server is loaded.

Does the JENNi Shop Local MCP server require authentication?

No. We connected to JENNi Shop Local without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the JENNi Shop Local MCP server still maintained?

JENNi Shop Local is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.