Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
JENNi Shop — Local & Nationwide AI Commerce is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search live local & nationwide retail stock, check prices, and run zero-click AI agent checkouts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jenni-shop-local-nationwide-ai-commerce-mcp https://shop.jennipro.com/mcp
# 2 — ask your agent for something these tools do
# search_catalog, find_stores, get_product and 2 more
JENNi Shop — Local & Nationwide AI Commerce costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http jenni-shop-local-nationwide-ai-commerce-mcp https://shop.jennipro.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Complete canonical product facts, read-only. Nullable titles, empty images/offers and unknown stock remain visible. Discovery never authorizes checkout; completion is unavailable. Store filters are rejected; postal context never filters facts. Use search_catalog for product facts without store filters; it does not verify stock, price or delivery. Then call get_buying_options with the exact product
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional title, brand, UPC or GTIN keyword. Omit to enumerate approved root catalog facts. |
| product_id | string | no | — |
| gtin | string | no | — |
| brand | string | no | — |
| store_id | string | no | Unsupported for catalog facts; nonempty store filters are rejected. |
| store_ids | array | no | Empty normalizes to absent; store filtering is unsupported. |
| zip | string | no | Optional echoed caller context only; never filters facts. |
| postal_code | string | no | Optional echoed caller context only; never filters facts. |
| limit | integer | no | — |
| cursor | string | no | Confidential opaque upstream continuation; forward unchanged with the same selectors and limit. |
Read-only shop directory by name. A listing proves no stock, price, delivery or checkout eligibility. Use search_catalog for product facts without store filters; it does not verify stock, price or delivery. Then call get_buying_options with the exact product_id, zip, quantity and fulfillment_mode. After the buyer chooses a returned offer with is_eligible_checkout true, use its store_id with start_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Shop name or part of it, e.g. "Cheeky Monkey". |
| zip | string | no | 5-digit US ZIP code: searches the shops within 15 miles of it first, then the national list. Pass it for any shop outside San Antonio. |
| market | string | no | Market key, e.g. san-antonio-tx. Used when no zip is given. |
| limit | integer | no | Shops to return (default 10). |
Complete canonical product facts, read-only. Nullable titles, empty images/offers and unknown stock remain visible. Discovery never authorizes checkout; completion is unavailable. Store filters are rejected; postal context never filters facts. Use search_catalog for product facts without store filters; it does not verify stock, price or delivery. Then call get_buying_options with the exact product
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | — |
| zip | string | no | Optional echoed caller context only; never filters facts. |
| postal_code | string | no | Optional echoed caller context only; never filters facts. |
Call when the shopper has chosen to buy: the exact product_id (a variant's when it has sizes or colours), the store_id of an offer with is_eligible_checkout true or fulfillment concierge, a quantity and their ZIP. Re-checks the offer at that quantity and returns checkout_url: JENNi checkout with that item added to the shopper's basket, where they enter email, name, address and card and see deliver
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | The exact item: a variant's product_id when it has variants. |
| store_id | string | yes | store_id of an offer with is_eligible_checkout true, or a concierge offer. |
| quantity | integer | yes | How many (default 1). |
| fulfillment_mode | string | yes | Retain the mode chosen from get_buying_options. |
| zip | string | yes | 5-digit US ZIP code the order is delivered to, e.g. 78205. |
Read verified buying options for the exact product, destination, quantity and fulfillment mode. Empty offers mean no options verified for this request, not that the product does not exist. Choose an eligible store, then start_checkout with the same context; the buyer approves and pays in hosted checkout.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | — |
| zip | string | yes | — |
| quantity | integer | yes | — |
| fulfillment_mode | string | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install JENNi Shop — Local & Nationwide AI Commerce or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_catalog | no tags | |
| find_stores | no tags | |
| get_product | no tags | |
| start_checkout | no tags | |
| get_buying_options | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish JENNi Shop — Local & Nationwide AI Commerce can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.