Elastic Path API + MCP by Elastic Path

# Fix list: Elastic Path API + MCP

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/elastic-path, the October 2026 research run, assessed 1 October 2026. Grade D, 50.4 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Elastic Path API + MCP: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 12 out of 100, up to 11 more on the total

Why it scored 12: No x402, MPP or L402 (0). The Entry contract is public at $49,500 a year for up to 15,000 orders or $5M GMV (per the 30 September check), and higher tiers are quoted (7). A free trial with no stated length or card terms (5). Contracts and trials go through a person (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Agent ergonomics, 33 out of 100, up to 10.9 more on the total

Why it scored 33: The MCP server has 95 tools by its own npm description, with no toolsets or filtering documented (5), and JSON:API includes let REST calls size responses a little (3). Filtering is confirmed by changelog entries, pagination wasn't checked (12). Error responses weren't found documented (5). No idempotency keys and no MCP annotations found (0). Official JavaScript SDK (35.1.0 on 25 September 2026) and generated @epcc-sdk packages, one language (8).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 3. Security & auth, 39 out of 100, up to 10.7 more on the total

Why it scored 39: OAuth tokens from Application Keys. client_credentials gives full CRUD, the implicit grant reads the live catalogue only, and custom API role policies can narrow what a key does (24). The implicit token is a read-only path for shopping, but the MCP server runs on client_credentials with full CRUD and documents no read-only mode or confirmation (10). Returns merchant and shopper content with no prompt-injection guidance found (5). No audit log found (0). elasticpath.com/security returns 404, the privacy policy cites no certification, and security.txt couldn't be read per the 30 September check (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Reliability, 68 out of 100, up to 6.4 more on the total

Why it scored 68: Atlassian Statuspage at status.elasticpath.com with Admin API, Shopper API, Commerce Manager and Webhooks components for the EU and US regions, a history link and 90-day uptime bars (20). The 15 days we could read hold two short incidents, US elevated errors for 4 minutes on 21 September and Commerce Manager degraded for 5 minutes on 1 October. Earlier history unchecked, and a clean partial window earns half (15). Published limits of 100 requests a second for production stores and organisations and 50 for development stores (15). A 429 is documented, with advice to wait a few seconds and retry and a JS SDK that retries in the browser, but no Retry-After header or idempotency guidance (8). No SLA found (0). The API and the Composable Commerce MCP server are generally available (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 5. Schema & documentation, 66 out of 100, up to 5.5 more on the total

Why it scored 66: The API reference is generated from OpenAPI documents, and the @epcc-sdk packages are generated too, but we found no downloadable spec file (12). llms.txt with about 950 entries, linking HTML pages rather than Markdown (10). Reference pages say what each endpoint does. We didn't read the 95 MCP tool descriptions, since the source isn't public (10). Typed REST parameters in the reference (11). Examples in the reference, but no error reference found in the llms.txt index (8). Dated changelog tagged MAJOR and MINOR, with deprecations carrying removal dates, such as with_tax filtering deprecated on 22 July and removed on 19 October 2026 (15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Transparency & trust, 64 out of 100, up to 3.2 more on the total

Made of editorial 38, provenance 90.

Why it scored 64: Closed platform. Terms of use dated 2016 per the 30 September check, and the npm package for the MCP server states no licence (10). Privacy policy last updated 29 June 2018, with no retention periods, DPA, subprocessors or data locations (3). Deprecations carry removal dates about three months out, for example cm_search deprecated on 8 July and removed on 6 October 2026 (18). Regions are named in the base URLs (useast, euwest), but there's no subprocessor list (7).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- security.txt: could not be fetched (0 of 10)

## 7. Maintenance & community, 77 out of 100, up to 2 more on the total

Why it scored 77: Changelog entry on 29 September 2026, and MCP 1.11.2 the same day per the 30 September check (30). Ten changelog entries since 3 July (20). Public changelog, support channel not checked (10). @elasticpath/js-sdk 35.1.0 on 25 September 2026 and the MCP on npm. The MCP isn't in the official registry (12). The MCP source isn't public, so its tests and CI can't be seen (5).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: incident history before 17 September 2026
- Whether Elastic Path holds SOC 2, ISO 27001 or PCI DSS certifications. We found no page that says
- The licence of @elasticpath/elasticpath-mcp, which npm doesn't state
- Whether the 95 MCP tools carry readOnlyHint or destructiveHint annotations
- unchecked: error response format and pagination parameters

## Weaknesses

- MCP server exposes 95 tools with full CRUD, no read-only mode and no public source or licence
- No self-serve plan. Contracts start at $49,500 a year
- Privacy policy last updated in 2018, with no DPA or subprocessor list
- No security page, certification claim or disclosure policy found
- No downloadable OpenAPI file found

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Use a client_credentials token server-side only. It has full CRUD on the store
- Pick the base URL for the store's region (useast or euwest), or every call returns 401
- Loading the MCP server costs 95 tool definitions, so enable it only for agents that need the back office
- On a 429, wait a few seconds and retry. No Retry-After header is sent
- Check out a cart with POST /v2/carts/{id}/checkout, then pay the resulting order

## What the review panel asked for

- Publish the tool list
- An error reference page
- read-only MCP mode
- a disclosure policy

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.