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.
| Evidence field | Financial DatasetsWatchlist candidate | Shopify Storefront MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP github:financial-datasets · 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 details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Official hosted service supports OAuth 2.1 or API-key authentication. | Shopify documents no authentication requirement for the Storefront MCP endpoint. Some stores may restrict access. UCP catalog requests include an agent-profile reference. |
| Cost | Financial Datasets subscription/API limits may apply. | Shopify documents no separate Storefront MCP fee. Merchant Shopify plan, application hosting, model, and client costs remain applicable. |
| Permissions | Read/data access only from the reviewed MCP evidence; do not describe this as a trading/execution MCP. | 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 handling | Financial query inputs and returned market/company data transit the hosted service and 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 |
|
|
| Risk context | MCP-specific adoption, service limits and operational maturity still need stronger Selected-grade evidence. | 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 review | 2026-09-13T00:00:00Z | 2026-09-05 |
| Candidate evidence | 2026-09-13T00:00:00Z | 2026-09-05T00:00:00.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →