Twice Commerce MCP by usefulapi
REMOTE · TWICE-COMMERCE.USEFULAPI.IO
Read orders, customers, catalog, stock and availability; add order comments in Twice Commerce.
Available components
Last scanned (13 hours 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 65
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 5 Nov 2026 · Probed https://twice-commerce.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 twice-commerce.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | 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://twice-commerce.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/twice-commerce/ |
| http (plaintext) | http://twice-commerce.usefulapi.io/mcp | Inconclusive | 302 | http://twice-commerce.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 →
twicecommerce_add_order_comment Add a comment to an order ~83
WRITE: add a comment to an order (needs a key with Write access to Order details). Each call adds a new comment; do not repeat a call that succeeded. Admin API: POST /v1/admin/orders/{orderId}/comments.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The comment text. |
| order_id | string | yes | The order id (uuid). |
No output schema declared.
No examples provided.
twicecommerce_check_availability Check availability for a period ~151
Check whether one catalog item can be booked for a date-time window (before you create an order). Dates are ISO 8601 date-times in UTC, for example 2026-11-05T09:00:00Z. Admin API: GET /v1/admin/availability/{catalogItemId}/period.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_item_id | string | yes | The catalog item id. |
| from | string | yes | Start date-time, ISO 8601 UTC (example 2026-11-05T09:00:00Z). |
| location_ids | array | – | Only check these service location ids. |
| to | string | yes | End date-time, ISO 8601 UTC. |
No output schema declared.
No examples provided.
twicecommerce_get_catalog_item Get a catalog item ~61
Get one catalog item by id: name, status, variants, rules and pricing links. Admin API: GET /v1/admin/catalog/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_item_id | string | yes | The catalog item id (from twicecommerce_list_catalog_items). |
No output schema declared.
No examples provided.
twicecommerce_get_customer Get a customer ~57
Get one customer by id: contact details, addresses and type. Admin API: GET /v1/admin/customers/{customerId}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id (uuid, from twicecommerce_list_customers). |
No output schema declared.
No examples provided.
twicecommerce_get_customer_orders Get customer orders ~47
List the orders of one customer. Admin API: GET /v1/admin/customers/{customerId}/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id (uuid). |
No output schema declared.
No examples provided.
twicecommerce_get_merchant Get merchant profile ~46
Get the merchant account: name, country, currency, timezone, languages, plan and enabled features. Good first call. Admin API: GET /v1/admin/merchant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
twicecommerce_get_order Get an order ~64
Get one order by id: status, customers, line items, stock items, comments, totals and pricing. Admin API: GET /v1/admin/orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (uuid, from twicecommerce_list_orders). |
No output schema declared.
No examples provided.
twicecommerce_get_order_invoices Get order invoices ~82
List the invoices of one order, optionally with the upcoming scheduled subscription invoices (needs a key with the Payments area). Admin API: GET /v1/admin/orders/{orderId}/invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| include_scheduled | boolean | – | Also list scheduled (upcoming) subscription invoices. |
| order_id | string | yes | The order id (uuid). |
No output schema declared.
No examples provided.
twicecommerce_get_order_payments Get order payments ~56
List the payment transactions of one order (needs a key with the Payments area). Admin API: GET /v1/admin/orders/{orderId}/payments.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The order id (uuid). |
No output schema declared.
No examples provided.
twicecommerce_get_sku Get a SKU ~51
Get one SKU by id. Admin API: GET /v1/admin/skus/{skuId}.
| Name | Type | Req | Description |
|---|---|---|---|
| sku_id | string | yes | The SKU id (uuid, from twicecommerce_list_skus). |
No output schema declared.
No examples provided.
twicecommerce_get_stock_item Get a stock item ~60
Get one stock item by id: SKU, condition, quantity, location and status. Admin API: GET /v1/admin/articles/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| stock_item_id | string | yes | The stock item id (from twicecommerce_list_stock_items). |
No output schema declared.
No examples provided.
twicecommerce_list_catalog_items List catalog items ~106
List catalog items (the listings customers rent, buy or subscribe to), with an optional name search and paging. Admin API: GET /v1/admin/catalog/.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Only listings whose name contains this text. |
| page | integer | – | Page number (default 1). |
| size | integer | – | Rows per page (default 25, max 100). |
| sort_by | string | – | – |
| sort_direction | string | – | Sort direction. |
No output schema declared.
No examples provided.
twicecommerce_list_customers List customers ~100
List customers, with an optional text search over name and email and paging. Admin API: GET /v1/admin/customers.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| search | string | – | Text to search for (contains match). |
| size | integer | – | Rows per page (default 25, max 100). |
| sort_by | string | – | – |
| sort_direction | string | – | Sort direction. |
No output schema declared.
No examples provided.
twicecommerce_list_discount_codes List discount codes ~77
List discount codes with usage and validity, with paging. Admin API: GET /v1/admin/discount-codes.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| search | string | – | Text to search for. |
| size | integer | – | Rows per page (default 25, max 100). |
No output schema declared.
No examples provided.
twicecommerce_list_orders List orders ~109
List orders with status, customers, line items, totals and dates. The API does not paginate this list, so the result is cut to `limit` rows (newest as returned by the API); the full count is in totalCount. Narrow it with location_ids. Admin API: GET /v1/admin/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (default 50, max 200). |
| location_ids | array | – | Only orders at these service location ids. |
No output schema declared.
No examples provided.
twicecommerce_list_service_locations List locations ~56
List pickup and return locations (service locations). Use the ids to filter orders and stock items. Admin API: GET /v1/admin/service-locations/.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | Which locations to list (default active). |
No output schema declared.
No examples provided.
twicecommerce_list_skus List SKUs ~69
List SKUs (the product definitions that stock items belong to), with paging. Admin API: GET /v1/admin/skus.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| size | integer | – | Rows per page (default 25, max 100). |
No output schema declared.
No examples provided.
twicecommerce_list_stock_items List stock items ~90
List stock items (the physical units, called articles in the API), with paging. Narrow by location ids. Admin API: GET /v1/admin/articles/.
| Name | Type | Req | Description |
|---|---|---|---|
| location_ids | array | – | Only stock items at these service location ids. |
| page | integer | – | Page number (default 1). |
| size | integer | – | Rows per page (default 25, max 100). |
No output schema declared.
No examples provided.
twicecommerce_list_tags List tags ~45
List tags used on inventory, catalog, customers or orders. Admin API: GET /v1/admin/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | yes | Which area's tags to list. |
No output schema declared.
No examples provided.
twicecommerce_list_taxes List taxes ~32
List the tax rates set up for the merchant. Admin API: GET /v1/admin/taxes/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Twice Commerce MCP by usefulapi server?
Twice Commerce MCP by usefulapi is a hosted endpoint at https://twice-commerce.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 · twice-commerce.usefulapi.io
claude mcp add --transport http io-usefulapi-twice-commerce 'https://twice-commerce.usefulapi.io/mcp'
What is the Twice Commerce MCP by usefulapi server?
Twice Commerce MCP by usefulapi is listed in the public MCP registry as io.usefulapi/twice-commerce. Read orders, customers, catalog, stock and availability; add order comments in Twice Commerce. This page covers its hosted endpoint (https://twice-commerce.usefulapi.io/mcp).
Is the Twice Commerce MCP by usefulapi server safe to use?
Twice Commerce 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 Twice Commerce MCP by usefulapi server expose?
Twice Commerce MCP by usefulapi exposes 20 tools: twicecommerce_get_merchant, twicecommerce_list_service_locations, twicecommerce_list_taxes, twicecommerce_list_tags, twicecommerce_list_orders, and 15 more. Their descriptions and schemas cost roughly 1,442 tokens of context every time the server is loaded.
Does the Twice Commerce MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Twice Commerce 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 Twice Commerce MCP by usefulapi server still maintained?
Twice Commerce 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.
What did VerifyMCP test on the Twice Commerce MCP by usefulapi server?
VerifyMCP ran 4 checks on Twice Commerce MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Twice Commerce MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.