Smaregi MCP by usefulapi
MCP server · smaregi.usefulapi.io · found in a public list · checked since 2026-10-30
Live, handshake completed · latest check
Reads and manages Smaregi store products, customers, stock and transactions.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Run an online store: Manage your own store or seller account: catalogue, listings, orders, feeds, discounts, ads and sales.
https://smaregi.usefulapi.io/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 494 endpoints from usefulapi.io.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-30 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
smaregi_adjust_stocksmaregi_create_customersmaregi_create_productsmaregi_get_categorysmaregi_get_customersmaregi_get_productsmaregi_get_staffsmaregi_get_storesmaregi_get_transactionsmaregi_list_categoriessmaregi_list_customerssmaregi_list_productssmaregi_list_staffssmaregi_list_stocksmaregi_list_stock_changessmaregi_list_storessmaregi_list_transactionssmaregi_set_stocksmaregi_update_customersmaregi_update_product
- Tools
- 20
- This list since
- 2026-10-30
- First listed to us
- 2026-10-30
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptstools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
smaregi_list_stores fields sort page limitsmaregi_get_store store_id* fieldssmaregi_list_staffs fields sort page limitsmaregi_get_staff staff_id* fieldssmaregi_list_categories fields sort page limitsmaregi_get_category category_id* fieldssmaregi_list_products category_id product_code group_code supplier_product_no display_flag updated_from updated_to fields sort page limitsmaregi_get_product product_id* with_prices with_stores with_reserve_items with_inventory_reservations with_attribute_items with_order_settingsmaregi_list_customers customer_code customer_no customer_id_from customer_id_to updated_from updated_to fields sort page limitsmaregi_get_customer customer_id* with_custom_fields fieldssmaregi_list_stock store_id product_id updated_from updated_to fields sort page limitsmaregi_list_stock_changes product_id* store_id* target_date stock_division fields sort page limit
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Commerce, travel and logistics / Products and shopping / Run an online store (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-30. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 14 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_02c14919e9ee0427