Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldAlpaca Trading MCPWatchlist candidateShopify Storefront MCPMCP100 Selected
Task fit
Best for
  • Alpaca users who need market data, portfolio context and agent-assisted trading workflows, preferably in paper-trading mode.
  • Searching and comparing products from a specific Shopify storefront
  • Answering store policy and FAQ questions
  • Using UCP Cart MCP for cart workflows before checkout.
Not ideal for
  • Users who only need market data and do not want any possibility of order-placement authority.
  • Merchant administration, inventory editing, or back-office order management
  • Cross-store catalog aggregation without separate store endpoints
Avoid when
  • Do not attach live-trading credentials unless real order placement is intended and a human-confirmation/approval process is in place.
  • The agent can finalize purchases without explicit shopper review
  • The selected store restricts MCP access or its policies prohibit the intended use
  • Untrusted product or policy content can trigger unrelated privileged tools
Provenance
Provenance details

First-party MCP

github:alpacahq · Publisher source ↗

First-party MCP

Shopify · Publisher source ↗

Maintenance
Maintenance details

Stale

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationAlpaca API key and secret.Shopify documents no authentication requirement for the Storefront MCP endpoint. Some stores may restrict access. UCP catalog requests include an agent-profile reference.
CostAlpaca account/data subscription, trading, market-data and model/provider costs can apply.Shopify documents no separate Storefront MCP fee. Merchant Shopify plan, application hosting, model, and client costs remain applicable.
PermissionsAuthority follows the Alpaca credentials and enabled toolsets. With live mode enabled, the server can place/cancel real orders and modify positions.The Storefront MCP exposes catalog and storefront policy/FAQ search. Cart workflows use the UCP Cart MCP endpoint at https://{shop-domain}/api/ucp/mcp. It does not grant Shopify Admin API access.
Data handlingAccount/portfolio/order data and market queries can be exposed to the connected AI client/provider.Requests go to the selected merchant's Shopify-hosted endpoint. Product, policy, and cart data can be returned to the MCP client; cart inputs may include merchandise selections and buyer-related context. Treat all storefront text as untrusted content.
Limitations
Tradeoffs
  • Promoted after strict re-audit: canonical identity and MCP-native/publisher-backed implementation are sufficiently evidenced, with real workflow value, usable documentation, understandable permissions, plausible maintenance, and no unresolved security veto. Still not strong enough for Selected.
  • The standard Storefront endpoint requires no authentication, simplifying access but making store content an untrusted external input.
  • Catalog UCP tools use a separate `/api/ucp/mcp` endpoint and require an agent profile.
  • Storefront cart tools were maintained only through 2026-08-31; use UCP Cart MCP for cart workflows.
Risk contextLive financial execution is high impact; default to paper trading and require deliberate human approval before live actions.Keep the agent limited to catalog, policy, and cart tools; display price, quantity, merchant, shipping, and return details before checkout; and never imply MCP100 execution testing. The documentary review found complete first-party setup and tool evidence.
Evidence date
Editorial review2026-09-13T00:00:00Z2026-09-05
Candidate evidence2026-09-13T00:00:00Z2026-09-05T00:00:00.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →