Hiboutik MCP by usefulapi
REMOTE · HIBOUTIK.USEFULAPI.IO
Read Hiboutik products, stock, customers, sales and turnover; edit customers and sale comments.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3932 tokens (~126/item across 31 items; 31 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
- 25 Oct 26 62
First indexed and scored.
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 25 Oct 2026 · Probed https://hiboutik.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 hiboutik.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://hiboutik.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://hiboutik.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://hiboutik.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://hiboutik.usefulapi.io/mcp |
| Authorisation server | https://hiboutik.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hiboutik.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/hiboutik/ |
| http (plaintext) | http://hiboutik.usefulapi.io/mcp | Inconclusive | 302 | http://hiboutik.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 →
hiboutik_create_customer Create customer ~166
WRITE: create a customer in Hiboutik. Needs at least a last name, first name, company or email. Returns the new customer id. POST /customers/.
| Name | Type | Req | Description |
|---|---|---|---|
| customers_birth_date | string | – | Birth date yyyy-mm-dd. |
| customers_company | string | – | Company. |
| customers_country | string | – | Country code (ISO alpha-3, e.g. FRA). |
| customers_email | string | – | Email address. |
| customers_first_name | string | – | First name. |
| customers_last_name | string | – | Last name. |
| customers_misc | string | – | Free-text note. |
| customers_phone_number | string | – | Phone number. |
| customers_ref_ext | string | – | External reference. |
| customers_tax_number | string | – | Tax / VAT number. |
No output schema declared.
No examples provided.
hiboutik_find_product_by_barcode Find product by barcode ~44
Find the product (and variant) with this barcode. GET /products/search/barcode/{barcode}/.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | yes | Product barcode. |
No output schema declared.
No examples provided.
hiboutik_get_customer Get customer ~34
One customer with full details. GET /customer/{customers_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customers_id | integer | yes | Customer id. |
No output schema declared.
No examples provided.
hiboutik_get_product Get product ~35
One product with its full details. GET /products/{product_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Product id. |
No output schema declared.
No examples provided.
hiboutik_get_sale Get sale ~41
One sale with its header, totals, payment and line items. GET /sales/{sale_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| sale_id | integer | yes | Sale id. |
No output schema declared.
No examples provided.
hiboutik_list_brands List brands ~121
List product brands (newest id first). GET /brands.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
No output schema declared.
No examples provided.
hiboutik_list_categories List categories ~160
List product categories (newest id first) with parent id and flags. GET /categories.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| order_by | string | – | Field to order by, e.g. product_id or product_model. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| sort | string | – | Sort direction: asc or desc. |
No output schema declared.
No examples provided.
hiboutik_list_closed_sales List closed sales ~207
List the closed (completed) sales of a store for one day, or for a whole month when day is omitted. GET /closed_sales/{store_id}/{year}/{month}[/{day}].
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | Day of the month 1-31. Omit for the whole month. |
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| month | integer | yes | Month 1-12. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| store_id | integer | yes | Store id. |
| year | integer | yes | Year, e.g. 2026. |
No output schema declared.
No examples provided.
hiboutik_list_customer_sales List sales of a customer ~139
List the sales made to one customer (newest first). GET /customer/{customers_id}/sales/.
| Name | Type | Req | Description |
|---|---|---|---|
| customers_id | integer | yes | Customer id. |
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
No output schema declared.
No examples provided.
hiboutik_list_customers List customers ~143
List customers (newest id first) with name, email, phone, country, loyalty points and store credit. Personal data of the shop's customers. GET /customers/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
No output schema declared.
No examples provided.
hiboutik_list_open_sales List open sales ~174
List the sales not yet closed in a store (newest first). GET /open_sales/{store_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| order_by | string | – | Field to order by, e.g. product_id or product_model. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| sort | string | – | Sort direction: asc or desc. |
| store_id | integer | yes | Store id. |
No output schema declared.
No examples provided.
hiboutik_list_payment_types List payment types ~58
List the payment types enabled in a store (cash, card, cheque...) with currency and flags. GET /payment_types/{store_id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| store_id | integer | yes | Store id (hiboutik_list_stores). |
No output schema declared.
No examples provided.
hiboutik_list_products List products ~178
List products (default newest id first) with model, barcode, price, supply price, brand, category, supplier and stock management flag. 250 per page. GET /products/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| order_by | string | – | Field to order by, e.g. product_id or product_model. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| sort | string | – | Sort direction: asc or desc. |
No output schema declared.
No examples provided.
hiboutik_list_size_types List variant types ~42
List the variant (size) types, such as clothing sizes or colours. Use an id with hiboutik_list_sizes. GET /size_types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hiboutik_list_sizes List variants of a type ~68
List the variants (sizes) of one variant type: size_id and name. The size_id identifies a variant of a product in stock and sales. GET /sizes/{size_type_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| size_type_id | integer | yes | Variant type id (hiboutik_list_size_types). |
No output schema declared.
No examples provided.
hiboutik_list_stock_orders List stock orders (inventory inputs) ~121
List the stock orders / goods receipts. GET /inventory_inputs/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
No output schema declared.
No examples provided.
hiboutik_list_stores List stores ~51
List the shops (stores) of the account: id, name, warehouse id, currency, time zone, address. Use store ids for sales, payment types and reports. GET /stores.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hiboutik_list_suppliers List suppliers ~85
List the suppliers with id, name and contact details. GET /suppliers/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from (default 0). Continue with the previous reply's next_offset. |
No output schema declared.
No examples provided.
hiboutik_list_taxes List taxes ~34
List the tax (VAT) rates with id, name, value and default flag. GET /taxes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hiboutik_list_users List users (vendors) ~54
List the Hiboutik users (staff, sales vendors): id, name, email, access level. The id is the vendor_id of a sale. Passwords and keys are never returned. GET /users.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hiboutik_list_warehouses List warehouses ~36
List warehouses (stock locations) with id and name. Use the ids for stock levels. GET /warehouses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hiboutik_report_products_sold Products sold report ~173
Products sold in a store during one month: quantities and revenue per product. GET /reports/products/{store_id}/{year}/{month}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| month | integer | yes | Month 1-12. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| store_id | integer | yes | Store id. |
| year | integer | yes | Year, e.g. 2026. |
No output schema declared.
No examples provided.
hiboutik_report_turnover Turnover report ~114
Sales total (turnover) of a store for one day, or per day for a whole month when day is omitted. GET /reports/turnover/{store_id}/{year}/{month}[/{day}].
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | Day of the month 1-31. Omit for the whole month. |
| month | integer | yes | Month 1-12. |
| store_id | integer | yes | Store id. |
| year | integer | yes | Year, e.g. 2026. |
No output schema declared.
No examples provided.
hiboutik_search_customers Search customers ~299
Search customers by last name, first name, email, phone, VAT number, country, customer code or external reference (each text value needs at least 3 characters). Dates: yyyy-mm-dd, or prefix with > < >= <= to compare. GET /customers/search/.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country code (ISO 3166 alpha-3, e.g. FRA). |
| customers_code | string | – | Customer code. |
| customers_ref_ext | string | – | External reference. |
| string | – | Email address. | |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| last_order_date | string | – | Last order date yyyy-mm-dd, optionally prefixed with > < >= <=. |
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| loyalty_points | string | – | Loyalty points: a number, or prefixed with > < >= <=. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| phone | string | – | Phone number. |
| vat | string | – | VAT number. |
No output schema declared.
No examples provided.
hiboutik_search_products Search products by filters ~281
Search products by model, category, brand, supplier, archived state, supplier or external reference. GET /products/search/.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| order_by | string | – | Field to order by, e.g. product_id or product_model. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| product_arch | – | – | 1 = archived products only, 0 = active only. |
| product_brand | integer | – | Only products of this brand id (hiboutik_list_brands). |
| product_category | integer | – | Only products of this category id (hiboutik_list_categories). |
| product_model | string | – | Model (name) to match. |
| product_supplier | integer | – | Only products of this supplier id (hiboutik_list_suppliers). |
| product_supplier_reference | string | – | Supplier reference. |
| products_ref_ext | string | – | External reference. |
| sort | string | – | Sort direction: asc or desc. |
No output schema declared.
No examples provided.
hiboutik_search_products_by_name Search products by name ~143
Find products whose model (name) matches the text. GET /products/search/name/{q}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from inside the vendor page (default 0). Continue with the previous reply's next_offset. |
| page | integer | – | Vendor page number from 1 (default 1); a page holds up to 250 rows. Continue with the previous reply's next_page. |
| q | string | yes | Text to look for in the product name. |
No output schema declared.
No examples provided.
hiboutik_set_sale_comment Set sale comment ~55
WRITE: add or replace the comment of a sale (it overwrites any existing comment). POST /sales/comments/.
| Name | Type | Req | Description |
|---|---|---|---|
| comments | string | yes | The comment text. |
| sale_id | integer | yes | Sale id. |
No output schema declared.
No examples provided.
hiboutik_stock_all_warehouses Stock in all warehouses ~201
Available stock per product and variant across warehouses, optionally filtered by category, brand, supplier or archived state. GET /stock_available/all_wh.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from (default 0). Continue with the previous reply's next_offset. |
| product_arch | – | – | 1 = archived products only, 0 = active only. |
| product_brand | integer | – | Only products of this brand id (hiboutik_list_brands). |
| product_category | integer | – | Only products of this category id (hiboutik_list_categories). |
| product_supplier | integer | – | Only products of this supplier id (hiboutik_list_suppliers). |
| product_supplier_reference | string | – | Supplier reference. |
| products_ref_ext | string | – | External reference. |
No output schema declared.
No examples provided.
hiboutik_stock_by_product Stock of one product ~48
Available stock of one product per variant and warehouse, with the inventory alert level. GET /stock_available/product_id/{product_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Product id. |
No output schema declared.
No examples provided.
hiboutik_stock_by_warehouse Stock in one warehouse ~214
Available stock per product and variant in one warehouse, optionally filtered. GET /stock_available/warehouse_id/{warehouse_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows returned per call, 1-250 (default 50). Large replies are cut by the server, so keep it small. |
| offset | integer | – | Row to start from (default 0). Continue with the previous reply's next_offset. |
| product_arch | – | – | 1 = archived products only, 0 = active only. |
| product_brand | integer | – | Only products of this brand id (hiboutik_list_brands). |
| product_category | integer | – | Only products of this category id (hiboutik_list_categories). |
| product_supplier | integer | – | Only products of this supplier id (hiboutik_list_suppliers). |
| product_supplier_reference | string | – | Supplier reference. |
| products_ref_ext | string | – | External reference. |
| warehouse_id | integer | yes | Warehouse id (hiboutik_list_warehouses). |
No output schema declared.
No examples provided.
hiboutik_update_customer Update a customer attribute ~143
WRITE: change ONE attribute of a customer (it overwrites the current value). Attributes: gender (0 unknown, 1 male, 2 female), last_name, first_name, email, company, phone, vat, country, date_of_birth, customers_code, comments, validity, customers_ref_ext, customers_misc. PUT /customer/{customers_id}/.
| Name | Type | Req | Description |
|---|---|---|---|
| customers_attribute | string | yes | The attribute to change. |
| customers_id | integer | yes | Customer id. |
| new_value | string | yes | The new value (for gender: 0, 1 or 2; for dates: yyyy-mm-dd). An empty string clears the attribute. |
No output schema declared.
No examples provided.
How do I install the Hiboutik MCP by usefulapi server?
Hiboutik MCP by usefulapi is a hosted endpoint at https://hiboutik.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 · hiboutik.usefulapi.io
claude mcp add --transport http io-usefulapi-hiboutik 'https://hiboutik.usefulapi.io/mcp'
What is the Hiboutik MCP by usefulapi server?
Hiboutik MCP by usefulapi is listed in the public MCP registry as io.usefulapi/hiboutik. Read Hiboutik products, stock, customers, sales and turnover; edit customers and sale comments. This page covers its hosted endpoint (https://hiboutik.usefulapi.io/mcp).
Is the Hiboutik MCP by usefulapi server safe to use?
Hiboutik MCP by usefulapi scores 62 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 Hiboutik MCP by usefulapi server expose?
Hiboutik MCP by usefulapi exposes 31 tools: hiboutik_list_stores, hiboutik_list_warehouses, hiboutik_list_users, hiboutik_list_taxes, hiboutik_list_payment_types, and 26 more. Their descriptions and schemas cost roughly 3,662 tokens of context every time the server is loaded.
Does the Hiboutik MCP by usefulapi server require authentication?
Yes. Hiboutik MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Hiboutik MCP by usefulapi server still maintained?
Hiboutik MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.