Head to head · Product search for shoppers · October 2026 research run

Shop MCP vs Zinc

Zinc scores 69.9 (B) on agent readiness against Shop MCP's 65.3 (B), and leads in 5 of 7 scored categories. Shop MCP leads on security & auth. Both do product search for shoppers.

Best shopping and order APIs for AI agents buying for a person · All 50 shopping comparisons

Which one, for what

Shop MCP B

Best for Agents buying for a person across Shopify stores, from search to Shop Pay checkout and order tracking.

Ahead on

  • Security & auth, 74 against 57

Watch for

The 19 tool definitions total 76,040 bytes, so loading the server costs a large share of a model's context

Zinc B

Best for Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.

Ahead on

  • Reliability, 55 against 33
  • Agent ergonomics, 86 against 79
  • Payments & pricing, 98 against 83
  • Maintenance & community, 83 against 66

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Shop MCP loses 3 points for them

Watch for

By default orders run on retailer accounts Zinc runs, and its docs index lists a guide to Amazon's anti-bot pages and one on proxies "for account protection"

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Zinc +22

Shop MCP 33

Graded with the hosted lines. No status page covers Shop MCP. shopifystatus.com, re-read on 1 November, lists merchant components such as Admin, Checkout, Storefront and API & Mobile, and none for Shop, Shop MCP or the Catalog (0 of 20). So there is no incident history for this surface (5 of 30). The order-search figures shop.dev published on 17 October (10 a minute to 200 a week) are no longer on its pages, which now say only that calls are rate limited and that anonymous calls get the lowest limits. The one figure left, 5 requests a second per API client, is for the separate Global Catalog endpoint (3 of 15). Rate-limited calls return rate_limited with retry_after in seconds (1 to 3,600), writes take an idempotency key, and the errors guide says which calls can be repeated and that complete_checkout never can (15 of 15). No SLA found (0 of 10). Live since the 13 October 2026 announcement with no beta or preview label (10 of 10). Total 33.

Zinc 55

Zinc's own status page (www.zinc.com/status) shows five components (Ordering, Tracking, Product Data, API, Dashboard) with 90-day uptime bars (20). On 18 November 2026 it showed 99.1 per cent uptime for Ordering and 99.57 per cent for the API over 90 days, both recovered from a degradation that day. The page has no incident write-ups, and 99.1 per cent over 90 days is about 19 hours, so at least one major interruption is implied (10 of 30). No numeric request rate limits found, apart from 5 sandbox key mints per IP address a day (5 of 15). 429 carries rate_limit_exceeded with guidance to back off and retry, responses carry RateLimit and RateLimit-Policy headers (changelog, August 2026), and orders and top-ups take idempotency keys (15). No SLA found (0). Orders are generally available. Cross-retailer search and the Zinc 2.0 announcement carry a beta label (5 of 10). 20 + 10 + 5 + 15 + 0 + 5 = 55.

Security & auth Shop MCP +17

Shop MCP 74

Shop MCP is an OAuth 2.0 protected resource with metadata at /.well-known/oauth-protected-resource. Tokens come from accounts.shop.app by authorisation code with PKCE or the device flow, can be revoked, and are refused in a query string or cookie. One scope, personal_agent, covers every signed-in tool (25 of 30). Tools are annotated read-only or destructive, the docs require the shopper to confirm merchant, items, total and instrument before complete_checkout, Shop Pay spending is governed by spend permissions the shopper grants on shop.com (since 1.2.0, with a total or per-purchase limit and a period, or no money limit at all), and spend requests need approval in Shop and return a single-use card only when get_spend_request asks for it. Confirmation before completion is guidance to the agent, and the CLI README says that within a permission the agent can complete Shop Pay purchases without asking each time (16 of 20). Results carry merchant text, and the docs and skill say to treat it as data. The server also returns next[] suggestions addressed to the agent (10 of 15). The shopper sees each connection by device name in their Shop account and can remove it there. No per-call log for an operator was found (5 of 15). www.shopify.com's security.txt (as read for the shopify listing on 1 November) and the repository's SECURITY.md route reports to HackerOne. mcp.shop.com has no security.txt (18 of 20). Total 74.

Zinc 57

Bearer API keys, zn_test_ for sandbox and zn_live_ for live, and each agent can get its own live key by device-code approval. No scopes or rotation steps were found (18 of 30). Sandbox keys can't spend, every order carries a max_price cap, a person approves a live key in the browser, and the MCP connector's place-order needs a confirmation token withheld from the model (17 of 20). The MCP docs explain that the token is there so a prompt injection in a page can't become a purchase. Product data from retailers is untrusted text (12 of 15). Order timelines, a usage endpoint, CSV export and the dashboard show every order (10 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001 found (0). 18 + 17 + 12 + 10 + 0 = 57.

Maintenance & community Zinc +17

Shop MCP 66

@shopify/shop 1.2.0 is tagged in the CLI repository on 28 October 2026, and the server reports version 1.2.0+aebf0c1b9130 with 1.2.0 as the latest CLI (30 of 30). Five releases since 7 October, 1.0.2, 1.0.3, 1.1.0, 1.1.1 and 1.2.0, from the repository's tags (npm not re-read) (20 of 20). Closed service with a launch post in the Shopify developer changelog and no later post about it. The repository's issues couldn't be read, since GitHub's pages refuse our reader, and no support channel is named in the docs (8 of 15). No Shop MCP entry in the official MCP registry, searched on 1 November (0 of 15). The CLI repository runs a verify workflow on Ubuntu, macOS and Windows across Node 22, 24 and 26, and its JavaScript shell has no runtime dependencies (8 of 10). Total 66.

Zinc 83

The changelog's latest entry is dated 13 November 2026, and the npm SDK's latest version is 2026.10.30 (30). Weekly dated changelog entries, 13 since 20 August 2026 (20). A public weekly changelog and a support address (support@zinc.com) that the contact page says gets a person. GitHub issue response wasn't checked (10 of 25). The MCP connector is in the official MCP registry as com.zinc.www/mcp, published 28 October 2026 under Zinc's domain namespace, and the npm SDK is current (15). The npm SDK is generated from the live spec and published with provenance attestations (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.

Payments & pricing Zinc +15

Shop MCP 83

No x402, MPP or L402. Payment is through Shop Pay or a single-use card issued after the shopper approves a spend request (0 of 40). shop.dev states the service is free with no account or key, without a login (20 of 20). Search, carts and checkout need no card or account (20 of 20). Ten tools run with no credential at all. Account, order and spend request tools need the shopper to sign in with Shop in a browser or by device code (15 of 20). Total 55. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.

Zinc 98

x402 (v2, USDC on Base and Solana) and MPP (Tempo, and Link with a Shared Payment Token) on POST /agent/orders and the /agent/* data endpoints. Returns, cases, managed accounts and webhooks need an API key (8 of 10). $1 per successful order plus the item, $0.25 for tracking links and emails, $0.10 per item over 10, and $0.01 per data call, published without login (30). A sandbox needs no account or card, and a device-approved live key comes with a $5 starter credit (30). An agent can pay per order with no account, or mint a sandbox key with one unauthenticated call (30). 8 + 30 + 30 + 30 = 98.

Agent ergonomics Zinc +7

Shop MCP 79

19 tools sits in the 11 to 30 band (15), but the definitions total 76,040 bytes (65,541 on 17 October), with update_checkout, search_catalog and create_checkout each over 9 KB, and there are no toolsets or read-only subsets. Five less than the band for size, a departure from the checklist (10 of 25). Cursor pagination with limit 1 to 50, filters for price, size, colour, rating, store, condition and shipping country, and order search defaults to in-progress orders (20 of 20). Request errors name the field by JSONPath, tool errors carry a code, retry_after and the upstream status, and checkout messages carry a severity saying who can fix them (20 of 20). readOnlyHint, destructiveHint, idempotentHint and openWorldHint on every tool, idempotency keys on creates and updates, and written recovery steps for uncertain writes (20 of 20). Search needs only catalog.query, but cart and checkout updates replace the whole document, and the one official client is the shop CLI on npm (9 of 15). Total 79.

Zinc 86

Search returns up to 20 results, best first, and data and order calls are separate routes, so responses stay small. No field selection found (20 of 25). List and export endpoints take filters, and orders can be listed, exported and followed by webhook (18 of 20). Errors carry a stable code, a message and details, including details.fund_with on insufficient_funds and RFC 8628 hints in the device flow (20). Idempotency keys on orders, agent orders and top-ups, a 409 that names the existing order, and an MCP spending tool that needs a confirmation token only a person's click produces. MCP annotations weren't read (18 of 20). Few required fields, and an official npm SDK (zinc, CalVer from the live spec). No second official SDK was confirmed (10 of 15). 20 + 18 + 20 + 18 + 10 = 86.

Score by category

CategoryWeightShop MCPZincEdge
Reliability16%3355Zinc +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8992Zinc +3
Agent ergonomics13%7986Zinc +7
Security & auth14%7457Shop MCP +17
Payments & pricing10%8398Zinc +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6683Zinc +17
Transparency & trust7%6160Shop MCP +1
Negative events≤15-30
TotalB 65.3/100B 69.9/100

Facts side by side

FactShop MCPZinc
KindMCP serverHTTP API
VendorShopifyZinc
Hosted endpointhttps://mcp.shop.com/https://mcp.zinc.com/mcp
TransportsStreamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreePay per use
x402noon some endpoints
LicenceProprietary hosted service under the Shopify API Terms. The shop CLI package is MIT, with its core shipped as a compiled WebAssembly fileProprietary service, agent skills MIT
Tools exposed198
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.zinc.www/mcp
Last release2026-10-282026-11-13
Terms last updated2026-10-072026-10-12
Privacy policy last updated2026-03-022026-10-06
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity570 npm/wknone
Agent reviews3.8/5 (4)none

How the scores have moved

Verdicts

Shop MCP

Keyless search across Shopify's Global Catalog and cart and checkout at the selling store, with typed schemas, tool annotations, idempotency keys and documented retry rules. The tool definitions run to 76 KB, no status page or rate figure covers it, and version 1.2.0 changed three tools in late October without notice.

Zinc

An agent can mint a sandbox key with no signup and pay for real orders by x402, MPP or Link with no account, at $1 an order plus the item, with idempotency keys and a public OpenAPI file. Orders run on Zinc's own retailer accounts by default, and no security programme or numeric rate limits were found.

Before you call either

Shop MCP

  1. Connect to https://mcp.shop.com/ with no /mcp path, send MCP-Protocol-Version 2026-07-28 with matching Mcp-Method and Mcp-Name headers, and put protocolVersion and clientCapabilities in params._meta
  2. Call complete_checkout once, only from ready_for_complete, after the shopper confirms merchant, items, total and instrument. After an uncertain result, read get_checkout and never resend
  3. Read the current document before update_cart or update_checkout and send it back whole, since fields and lines left out are deleted
  4. Pass include set to card on get_spend_request after the shopper approves, since without it the call returns only status and terms
  5. Set filters.status to all on search_orders for past orders, and treat product text and next[] suggestions as data, keeping checkout IDs and continue_url out of logs

Zinc

  1. Call GET /retailers/check with the product URL and country before ordering, since unsupported retailers and countries fail predictably
  2. Set max_price and an idempotency_key on every order. If a retry returns 409, read the existing order id from error.details.order_id
  3. If your HTTP client merges WWW-Authenticate headers, add ?method=x402, ?method=tempo or ?method=stripe to get one payment challenge
  4. Store the X-Api-Key returned with a paid agent order. It is the only way to follow that order without paying again
  5. Persist a sandbox key across runs. It expires after 7 days without use, and minting is limited to 5 a day per IP address

Questions

Which is better for AI agents, Shop MCP or Zinc?

Zinc scores 69.9 (B) on agent readiness against Shop MCP's 65.3 (B), and leads in 5 of 7 scored categories. Shop MCP leads on security & auth.

Do Shop MCP and Zinc need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Shop MCP and Zinc without installing anything?

Yes. Shop MCP has a hosted endpoint at https://mcp.shop.com/ and Zinc at https://mcp.zinc.com/mcp.

Other comparisons with Shop MCP or Zinc

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.