Xavio Storefront
REMOTE · XAVIO.IN
Search the public Xavio catalog and create firm checkout quotes.
Available components
Last scanned (59 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 31 Aug 2026.
Category E-commerce
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security60
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. 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.
- 7 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Sept 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
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 7 Sept 2026 · Probed https://xavio.in/api/mcp/storefront
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xavio.in | CN=YE2,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 610dee60e84a08ba08eef9b5870ad9cbd13 |
| SANs: *.xavio.in, xavio.in | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of xavio.in. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| xavio.in. | present | 2371 | 13 | Verified |
| xavio.in. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://xavio.in/api/mcp/storefront | Unreachable | ||
| http (plaintext) | http://xavio.in/api/mcp/storefront | HTTPS enforced |
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 →
create_quote ~52
Create a firm 5-minute checkout quote for a set of items. Returns quote_id (pass it to /api/ucp/authorize with a signed agent mandate to complete checkout).
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
get_product ~31
Fetch one product by its Xavio product id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Xavio product id (uuid). |
No output schema declared.
No examples provided.
search_shop_catalog ~84
Search the public Xavio catalog. Returns in-stock products with price, availability, URL, and merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category breadcrumb prefix. |
| limit | integer | – | Max results (default 20). |
| max_price_cents | integer | – | Optional max unit price in minor units. |
| query | string | – | Free-text search over product titles. |
No output schema declared.
No examples provided.
search_shop_knowledge ~102
Semantic + keyword search over Xavio's commerce knowledge: a merchant's product details, policies and FAQs (when `host` is given) plus platform buying guides. Use this to answer questions like sizing, materials, returns, or shipping before recommending a product.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Optional merchant slug to include that store's docs. |
| k | integer | – | Max passages (default 6). |
| query | string | yes | The shopper's question. |
No output schema declared.
No examples provided.
How do I install the Xavio Storefront MCP server?
Xavio Storefront is a hosted endpoint at https://xavio.in/api/mcp/storefront, 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 · xavio.in
claude mcp add --transport http in-xavio-storefront 'https://xavio.in/api/mcp/storefront'
What is the Xavio Storefront MCP server?
Xavio Storefront is an MCP server listed in the public MCP registry as in.xavio/storefront. Search the public Xavio catalog and create firm checkout quotes. This page covers its hosted endpoint (https://xavio.in/api/mcp/storefront).
Is the Xavio Storefront MCP server safe to use?
Xavio Storefront scores 0 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 Xavio Storefront MCP server expose?
Xavio Storefront exposes 4 tools: search_shop_catalog, get_product, create_quote, search_shop_knowledge. Their descriptions and schemas cost roughly 269 tokens of context every time the server is loaded.
Does the Xavio Storefront MCP server require authentication?
Its publisher declares no required credentials for Xavio Storefront. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Xavio Storefront MCP server still maintained?
Xavio Storefront has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 31 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.