ai.ordercore/ordercore-mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Commerce catalog, order and checkout MCP with read-only sandbox

What we know

Commerce catalog, order and checkout MCP with read-only sandbox. Published by the owner of npm package @ordercore/mcp. Commerce backend for AI agents: catalog, prices, inventory, orders, idempotent checkout.

Maintenance / activity evidence

206 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes. Reported action classes: Update catalog and inventory; Create orders / checkout. Complete write authority is not verified.
Read-only sandbox without key; ORDERCORE_API_KEY for write operations
Sensitive access: Service account information and data accessible by supplied credentials

Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 206 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @ordercore/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @ordercore/mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.

Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
Read-only sandbox without key; ORDERCORE_API_KEY for write operations
Reviewed write actions: Update catalog and inventory; Create orders / checkout
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

206 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/@ordercore/mcp

Exact implementation source: https://www.npmjs.com/package/@ordercore/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@ordercore/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
@ordercore/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
No key is read-only demo sandbox; ORDERCORE_API_KEY enables checkout/write tools. Avoid spending in verification.
publisher documented install or connect · Claude Code only · Publisher instructions
claude mcp add ordercore -- npx -y @ordercore/mcp
Configure / authenticate
MCP100 setup guide
Default package is sandbox/no-key catalog; full checkout requires ORDERCORE_API_KEY and can create/complete real checkout.
Check connection
Suggested check
Use OrderCore sandbox keyless catalog/list tools. Do not create, update or complete checkout sessions.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `ordercore`, run `claude mcp remove ordercore` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: OrderCore demo sandbox requires no credential. Official authentication guide documents live API key list/revoke/rotate lifecycle via /v1/account/api-keys; rotate gives old key a grace period. See linked full API guide before issuing any DELETE/revoke request.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove ordercore

Official Documentation & Sources

What it does

Commerce catalog, order and checkout MCP with read-only sandbox. Published by the owner of npm package @ordercore/mcp. Commerce backend for AI agents: catalog, prices, inventory, orders, idempotent checkout.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Retail & E-commerce
Best fit: Commerce catalog, order and checkout MCP with read-only sandbox

Representative uses

Commerce catalog, order and checkout MCP with read-only sandbox

Limitations

Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Read-only sandbox without key; ORDERCORE_API_KEY for write operations
Permissions: Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.
Data handling: Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.

Access scope and cautions

Write actions: Not verified Update catalog and inventory Create orders / checkout
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: high
Security notes: Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Read-only sandbox without key; ORDERCORE_API_KEY for write operations

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Update catalog and inventory; Create orders / checkout. Recorded permission context: Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes.

What data-handling boundary should I consider?

Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Catalog, order and checkout operations can create commercial obligations; anonymous sandbox is read-only, production ORDERCORE_API_KEY authorizes writes. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.