Sapo MCP by usefulapi
REMOTE · SAPO.USEFULAPI.IO
Read Sapo store products, orders, customers and stock levels; edit order notes and stock.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “browse_products_variants_and_discount_rules” functional
- New prompt “change_an_order_s_note_or_tags_or_set_a_stock_quantity” functional
- New prompt “find_products_that_are_low_on_stock” functional
- New prompt “look_up_customers_and_how_much_they_spent” functional
- New prompt “review_orders_and_what_is_unpaid” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.9.0 → 1.11.0 functional
- Server version: 1.8.0 → 1.9.0 functional
- Server version: 1.7.2 → 1.8.0 functional
- 30 Oct 26 +1
- Server version: 1.7.1 → 1.7.2 functional
- Server version: 1.7.0 → 1.7.1 functional
- 29 Oct 26 0
- Server version: 1.6.0 → 1.7.0 functional
- Server version: 1.5.0 → 1.6.0 functional
- 28 Oct 26 0
- Server version: 1.3.0 → 1.5.0 functional
- 27 Oct 26 +1
- Server version: 1.2.0 → 1.3.0 functional
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://sapo.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sapo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sapo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/sapo/ |
| http (plaintext) | http://sapo.usefulapi.io/mcp | Inconclusive | 302 | http://sapo.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sapo_count_customers Count customers ~24
Total number of customers. GET /admin/customers/count.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sapo_count_orders Count orders ~329
Number of orders matching the filters. GET /admin/orders/count.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| created_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| financial_status | string | – | Payment status: authorized, pending, paid, refunded, voided, or any. Sapo default when omitted: authorized, pending and paid only (refunded and voided are left out). |
| fulfillment_status | string | – | Fulfillment status (for example unfulfilled, fulfilled, partial). |
| modified_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| modified_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| status | string | – | Order status: open (Sapo default when omitted, so archived orders are left out), closed, or any (all orders). Pass any for date-range totals. |
No output schema declared.
No examples provided.
sapo_count_products Count products ~169
Number of products matching the filters. GET /admin/products/count.json.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | integer | – | Only products in this collection (see sapo_list_custom_collections). |
| created_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| created_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| product_type | string | – | Exact product type. |
| vendor | string | – | Exact vendor (brand) name. |
No output schema declared.
No examples provided.
sapo_get_customer Get customer ~37
One customer by id. GET /admin/customers/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Sapo customer id. |
No output schema declared.
No examples provided.
sapo_get_order Get order ~47
One order by id with line items, addresses, discounts, payment and shipping. GET /admin/orders/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Sapo order id. |
No output schema declared.
No examples provided.
sapo_get_product Get product ~41
One product by id, with variants and images. GET /admin/products/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Sapo product id. |
No output schema declared.
No examples provided.
sapo_get_product_variant Get product variant ~39
One product variant by id. GET /admin/variants/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| variant_id | integer | yes | Sapo variant id. |
No output schema declared.
No examples provided.
sapo_get_store Get store ~38
The Sapo store this login belongs to: name, domain, currency, timezone, plan and other settings. GET /admin/store.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sapo_list_custom_collections List collections ~103
List manual product collections (danh mục thủ công). Paged. GET /admin/custom_collections.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-250 (default 50). |
| name | string | – | Filter by collection name. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| product_id | integer | – | Only collections that contain this product. |
No output schema declared.
No examples provided.
sapo_list_customers List customers ~295
List customers with contact details, addresses, order count and total spent. Paged. GET /admin/customers.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| created_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| limit | integer | – | Results per page, 1-250 (default 50). |
| modified_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| modified_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| since_id | integer | – | Only customers with an id greater than this. |
No output schema declared.
No examples provided.
sapo_list_inventory_items List inventory items ~145
List inventory items (one per variant) by SKU/barcode search, variant or product ids. The id is what stock levels use as inventory_item_id. Paged. GET /admin/inventory_items.json.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these inventory item ids. |
| limit | integer | – | Results per page, 1-250 (default 50). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| product_ids | array | – | Only these product ids. |
| query | string | – | Search by barcode or SKU. |
| variant_ids | array | – | Only these variant ids. |
No output schema declared.
No examples provided.
sapo_list_inventory_levels List inventory levels ~139
Stock per item and location: on_hand, available, committed, incoming, reserved. Filter by inventory item or location ids, or by a minimum/maximum available quantity. Sapo documents no paging for this list, so narrow it with ids. GET /admin/inventory_levels.json.
| Name | Type | Req | Description |
|---|---|---|---|
| available_max | number | – | Only levels with at most this much available. |
| available_min | number | – | Only levels with at least this much available. |
| inventory_item_ids | array | – | Only these inventory item ids (see sapo_list_inventory_items). |
| location_ids | array | – | Only these location ids (see sapo_list_locations). |
No output schema declared.
No examples provided.
sapo_list_locations List locations ~122
List branches, stores and warehouses (id, name, address, whether they track stock). Use the ids for stock levels. Paged. GET /admin/locations.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-250 (default 50). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| query | string | – | Search by name, code or phone. |
| status | string | – | Branch status; Sapo spells the inactive value "expried". |
No output schema declared.
No examples provided.
sapo_list_order_transactions List order transactions ~42
The payment transactions recorded on one order. GET /admin/orders/{order_id}/transactions.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Sapo order id. |
No output schema declared.
No examples provided.
sapo_list_orders List orders ~443
List orders with line items, customer, totals, payment and fulfillment status. Filter by status, tag, customer or dates. Paged: pass next_page as page. GET /admin/orders.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| created_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| customer_id | integer | – | Only orders of this customer. |
| financial_status | string | – | Payment status: authorized, pending, paid, refunded, voided, or any. Sapo default when omitted: authorized, pending and paid only (refunded and voided are left out). |
| fulfillment_status | string | – | Fulfillment status (for example unfulfilled, fulfilled, partial). |
| limit | integer | – | Results per page, 1-250 (default 50). |
| modified_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| modified_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| query | string | – | Search text (order number, customer name, phone, email). |
| status | string | – | Order status: open (Sapo default when omitted, so archived orders are left out), closed, or any (all orders). Pass any for date-range totals. |
| tag | string | – | Only orders with this tag. |
No output schema declared.
No examples provided.
sapo_list_price_rules List price rules ~273
List discount price rules (percentage, fixed amount, fixed price) with validity dates and usage counts. Paged. GET /admin/price_rules.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| created_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| ends_on_max | string | – | Only rules that end on or before this date. |
| ends_on_min | string | – | Only rules that end on or after this date. |
| limit | integer | – | Results per page, 1-250 (default 50). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| starts_on_max | string | – | Only rules that start on or before this date. |
| starts_on_min | string | – | Only rules that start on or after this date. |
| times_used | integer | – | Only rules used exactly this many times. |
No output schema declared.
No examples provided.
sapo_list_product_variants List product variants ~99
The variants (size, color, SKU, barcode, price) of one product. Paged. GET /admin/products/{product_id}/variants.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-250 (default 50). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| product_id | integer | yes | Sapo product id. |
No output schema declared.
No examples provided.
sapo_list_products List products ~380
List products with their variants, prices, SKUs and images. Filter by name, vendor, type, collection or created/modified dates. Paged: pass next_page as page. GET /admin/products.json.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | integer | – | Only products in this collection (see sapo_list_custom_collections). |
| created_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| created_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| ids | array | – | Only these product ids. |
| limit | integer | – | Results per page, 1-250 (default 50). |
| modified_on_max | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| modified_on_min | string | – | ISO 8601 date or date-time (UTC unless it carries an offset), e.g. 2026-10-01 or 2026-10-01T00:00:00Z. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| product_type | string | – | Exact product type. |
| query | string | – | Search by product name. |
| since_id | integer | – | Only products with an id greater than this. |
| vendor | string | – | Exact vendor (brand) name. |
No output schema declared.
No examples provided.
sapo_set_inventory_level Set stock quantity ~148
WRITE: set the physical stock (on_hand) of one inventory item at one location to an exact quantity, with a reason. This OVERWRITES the current number and is recorded as a stock adjustment: read the level first (sapo_list_inventory_levels). PUT /admin/inventory_levels/set.json.
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_item_id | integer | yes | Inventory item id (see sapo_list_inventory_items). |
| location_id | integer | yes | Location id (see sapo_list_locations). |
| on_hand | number | yes | Physical on-hand quantity to set (at most 3 decimals are kept). |
| reason | string | – | Why the stock changes (default: Sapo's own default). |
No output schema declared.
No examples provided.
sapo_update_order Update order note or tags ~122
WRITE: set the note and/or the tags of an order (Sapo only lets an order's items and quantities stay fixed after creation). The value REPLACES the existing note or tags: read the order first to keep what is there. PUT /admin/orders/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | New order note (replaces the old one; empty string clears it). |
| order_id | integer | yes | Sapo order id. |
| tags | array | – | New tag list (replaces all tags; an empty list clears them). |
No output schema declared.
No examples provided.
How do I install the Sapo MCP by usefulapi server?
Sapo MCP by usefulapi is a hosted endpoint at https://sapo.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sapo.usefulapi.io
claude mcp add --transport http io-usefulapi-sapo 'https://sapo.usefulapi.io/mcp'
What is the Sapo MCP by usefulapi server?
Sapo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sapo. Read Sapo store products, orders, customers and stock levels; edit order notes and stock. This page covers its hosted endpoint (https://sapo.usefulapi.io/mcp).
Is the Sapo MCP by usefulapi server safe to use?
Sapo MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sapo MCP by usefulapi server expose?
Sapo MCP by usefulapi exposes 20 tools: sapo_get_store, sapo_list_products, sapo_count_products, sapo_get_product, sapo_list_product_variants, and 15 more. Their descriptions and schemas cost roughly 3,035 tokens of context every time the server is loaded.
Does the Sapo MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Sapo MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Sapo MCP by usefulapi server still maintained?
Sapo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.