myonlinestore MCP server

None of its 20 tools are described as changing anything. For 20 the reading was uncertain, so no mark is shown.

• myonlinestore_get_store

  “Get the shop's own details: name, primary domain, currency, default and active languages, prices-include-tax setting and business models.”

  Publisher declares: read-only yes

  1 input

  • languagestring“Language for translated fields (default: the shop language).”
• myonlinestore_list_shipping_methods

  “List the shipping methods the shop offers: display name, countries served, default flag and the free-shipping threshold.”

  Publisher declares: read-only yes

  Takes no inputs.

• myonlinestore_list_articles

  “List the shop's articles (products) with name, SKU, price and stock.”

  Publisher declares: read-only yes

  9 inputs

  • languagestring“Language for translated fields (default: the shop language).”
  • limitinteger“Maximum number of results.”
  • offsetinteger“Number of results to skip (paging).”
  • idsstring“Comma-separated article ids.”
  • uuidsstring“Comma-separated article uuids.”
  • created_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • created_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • changed_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • changed_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
• myonlinestore_get_article

  “Get one article (product) by its id.”

  Publisher declares: read-only yes

  3 inputs, 1 required

  • article_idstringrequired“The article id (from myonlinestore_list_articles).”
  • use_url_idboolean“True when the id is the one from the article page URL (default false).”
  • languagestring“Language for translated fields (default: the shop language).”
• myonlinestore_count_articles

  “Count the shop's articles, optionally within a created or changed date range.”

  Publisher declares: read-only yes

  5 inputs

  • languagestring“Language for translated fields (default: the shop language).”
  • created_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • created_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • changed_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • changed_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
• myonlinestore_list_categories

  “List the shop's categories with title, parent, visibility and sort order.”

  Publisher declares: read-only yes

  9 inputs

  • languagestring“Language for translated fields (default: the shop language).”
  • limitinteger“Maximum number of results.”
  • offsetinteger“Number of results to skip (paging).”
  • as_treeboolean“Return the nested category tree (default false).”
  • max_depthinteger“Tree depth limit when as_tree is true.”
  • created_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • created_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • changed_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • changed_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
• myonlinestore_get_category

  “Get one category by id: title, content, SEO fields, parent and sorting.”

  Publisher declares: read-only yes

  2 inputs, 1 required

  • category_idstringrequired“The category id (from myonlinestore_list_categories).”
  • languagestring“Language for translated fields (default: the shop language).”
• myonlinestore_list_category_articles

  “List the articles that belong to one category.”

  Publisher declares: read-only yes

  4 inputs, 1 required

  • category_idstringrequired“The category id.”
  • languagestring“Language for translated fields (default: the shop language).”
  • limitinteger“Maximum number of results.”
  • offsetinteger“Number of results to skip (paging).”
• myonlinestore_list_customers

  “List the shop's customers.”

  Publisher declares: read-only yes

  2 inputs

  • qstring“Search text (name, email or similar).”
  • embedstring“Include related data: address.”
• myonlinestore_get_customer

  “Get one customer by id.”

  Publisher declares: read-only yes

  1 input, 1 required

  • customer_idstringrequired“The customer id (from myonlinestore_list_customers).”
• myonlinestore_list_customer_addresses

  “List the saved addresses of one customer.”

  Publisher declares: read-only yes

  1 input, 1 required

  • customer_idstringrequired“The customer id.”
• myonlinestore_list_orders

  “List orders with status, date, currency, discount code and payment status.”

  Publisher declares: read-only yes

  11 inputs

  • languagestring“Language for translated fields (default: the shop language).”
  • limitinteger“Maximum number of results.”
  • offsetinteger“Number of results to skip (paging).”
  • start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • end_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • status_idinteger“Filter by order status id.”
  • status_changed_start_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • status_changed_end_datestring“Date filter as the API expects it (for example 2026-01-31).”
  • debtor_emailstring“Filter by customer email.”
  • debtor_idstring“Filter by customer id.”
  • archivedboolean“Include or filter archived orders.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.