Loox MCP by usefulapi
REMOTE · LOOX.USEFULAPI.IO
Read Loox product and store reviews, reviewer details and rating summaries. Read-only.
Available components
Last scanned (49 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 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 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 Usability79
- 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 1240 tokens (~177/item across 7 items; 7 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.2.3 functional
- 24 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://loox.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 loox.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://loox.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://loox.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://loox.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://loox.usefulapi.io/mcp |
| Authorisation server | https://loox.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loox.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/loox/ |
| http (plaintext) | http://loox.usefulapi.io/mcp | Inconclusive | 302 | http://loox.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 →
loox_get_product_rating Get product rating ~79
Review count and average star rating of ONE product (published reviews; 0 when it has none). Public Storefront API. GET /storefront/v1/store/{id}/product-reviews/bottomline/{productId}.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | Shopify product id (digits, e.g. 7891234567890). |
No output schema declared.
No examples provided.
loox_get_product_review Get product review ~90
One product review by id, any moderation status (published, unpublished or pending), with full reviewer details. Merchant data: includes the reviewer's name, email, Shopify customer id and order id. GET /api/v1/store/{id}/product-reviews/{reviewId}.
| Name | Type | Req | Description |
|---|---|---|---|
| review_id | string | yes | Loox review id (the `id` of a review from a list tool). |
No output schema declared.
No examples provided.
loox_get_product_reviews_summary Get product reviews summary ~64
Overall rating of the store's published product reviews: total count, average stars and how many reviews per star (1-5). Public Storefront API, published reviews only. GET /storefront/v1/store/{id}/product-reviews/bottomline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
loox_get_store_review Get store review ~85
One store-level review by id, any moderation status, with full reviewer details. Merchant data: includes the reviewer's name, email, Shopify customer id and order id. GET /api/v1/store/{id}/store-reviews/{reviewId}.
| Name | Type | Req | Description |
|---|---|---|---|
| review_id | string | yes | Loox review id (the `id` of a review from a list tool). |
No output schema declared.
No examples provided.
loox_get_store_reviews_summary Get store reviews summary ~62
Overall rating of the store-level reviews: total count, average stars and how many reviews per star (1-5). Public Storefront API, published reviews only. GET /storefront/v1/store/{id}/store-reviews/bottomline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
loox_list_product_reviews List product reviews ~325
List product reviews of the store, newest or best first, with rating, text, photos/videos, merchant reply, product, verified-purchase flag, AI highlights, country and moderation status. Merchant data: includes the reviewer's name, email, Shopify customer id and order id. Filter by product, star rating, status (default: published only; use pending to find reviews awaiting approval) and date range. Real time. GET /api/v1/store/{id}/product-reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default desc). With sort=rating, desc = highest first. |
| from_date | string | – | Only reviews dated on or after this day (yyyy-mm-dd, inclusive). |
| limit | integer | – | Reviews per page, 1-250 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| product_id | string | – | Only reviews of this Shopify product id. |
| rating | array | – | Only reviews with one of these star ratings (1-5), e.g. [1,2] for the unhappy ones. |
| sort | string | – | Sort order (default featured: pinned, then photo/video reviews, then date). ai needs Smart Visual Sorting (Convert plan). |
| status | string | – | Moderation status filter. Default published. pending = awaiting publishing, unpublished = hidden, all = every status. |
| to_date | string | – | Only reviews dated on or before this day (yyyy-mm-dd, inclusive). |
No output schema declared.
No examples provided.
loox_list_store_reviews List store reviews ~276
List store-level reviews (about the shop, not one product) with rating, text, merchant reply and moderation status. Merchant data: includes the reviewer's name, email, Shopify customer id and order id. Filter by star rating, status (default published) and date range (applied to createdAt). GET /api/v1/store/{id}/store-reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default desc). With sort=rating, desc = highest first. |
| from_date | string | – | Only reviews created on or after this day (yyyy-mm-dd, inclusive). |
| limit | integer | – | Reviews per page, 1-250 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| rating | array | – | Only reviews with one of these star ratings (1-5), e.g. [1,2] for the unhappy ones. |
| sort | string | – | Sort order (default featured: highest-quality reviews first, then date). |
| status | string | – | Moderation status filter. Default published. pending = awaiting publishing, unpublished = hidden, all = every status. |
| to_date | string | – | Only reviews created on or before this day (yyyy-mm-dd, inclusive). |
No output schema declared.
No examples provided.
How do I install the Loox MCP by usefulapi server?
Loox MCP by usefulapi is a hosted endpoint at https://loox.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 · loox.usefulapi.io
claude mcp add --transport http io-usefulapi-loox 'https://loox.usefulapi.io/mcp'
What is the Loox MCP by usefulapi server?
Loox MCP by usefulapi is listed in the public MCP registry as io.usefulapi/loox. Read Loox product and store reviews, reviewer details and rating summaries. Read-only. This page covers its hosted endpoint (https://loox.usefulapi.io/mcp).
Is the Loox MCP by usefulapi server safe to use?
Loox 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 Loox MCP by usefulapi server expose?
Loox MCP by usefulapi exposes 7 tools: loox_list_product_reviews, loox_get_product_review, loox_list_store_reviews, loox_get_store_review, loox_get_product_reviews_summary, and 2 more. Their descriptions and schemas cost roughly 981 tokens of context every time the server is loaded.
Does the Loox MCP by usefulapi server require authentication?
Yes. Loox 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 Loox MCP by usefulapi server still maintained?
Loox 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.