Jithox Commerce Preflight
REMOTE · COMMERCE.MCP.JITHOX.COM
Read-only commerce/checkout preflight (UCP/ACP). Returns evidence, never places orders.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Unreachable for 4 days in a row. Last reached 1 Nov 2026.
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Retired 2026-09-23. commerce.mcp.jithox.com answers no tool; current Jithox tools: https://jithox.com/tools.
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- 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 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 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.
- 5 Nov 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://commerce.mcp.jithox.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of commerce.mcp.jithox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jithox.com. | absent | 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 |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://commerce.mcp.jithox.com/mcp | Unreachable | ||
| http (plaintext) | http://commerce.mcp.jithox.com/mcp | 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 →
build_affiliate_buy_link Build an official buy link for a human ~137
Return the provider's OFFICIAL product link for a record — no network call, nothing ordered, never a checkout-completion URL. A HUMAN clicks it; any commission accrues at the provider's own partner programme, never through this server. 'ready' when the provider publishes a link; 'unsupported' when it does not; truthful 'not_configured' (costs nothing) without a provider. Preflight evidence only — this server never places, modifies or cancels an order and never touches a payment; the merchant stays merchant of record.
| Name | Type | Req | Description |
|---|---|---|---|
| publicRecordId | string | yes | The public record id to link to. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
compare_product_offers Compare offers as a value table ~181
Compare current offers for 2–5 EANs as a VALUE TABLE ordered by a stated criterion (price ascending). One unreadable offer makes the whole table 'unavailable' — no partial table is sold as a comparison. A table, never a ranking sold as advice, never a 'best product'. Answers come from the queried source at the stated retrieval time — a UCP or ACP merchant, a partner catalog source, or a clearly-labelled synthetic fixture in dev/test; provenance.sourceAuthority names which, and every answer carries the markets that source declares. Preflight evidence only — this server never places, modifies or cancels an order and never touches a payment; the merchant stays merchant of record.
| Name | Type | Req | Description |
|---|---|---|---|
| eans | array | yes | EANs to compare; a comparison needs at least 2 (fewer returns 'insufficient_identifiers'). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
get_commerce_readiness Commerce readiness snapshot ~108
One plain state of THIS server: which commerce provider is configured, which protocols this deployment speaks (UCP profile discovery + negotiation; the ACP REST checkout format), what each protocol still needs before live evidence exists, and the affiliate state. 'ready' / 'not_configured'. Truthful self-description, never a claim about any merchant. Preflight evidence only — this server never places, modifies or cancels an order and never touches a payment; the merchant stays merchant of record.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
get_product_offer Get one product's current offer or checkout evidence ~384
Report one product's current offer from the queried source (price in integer minor units, availability, provenance) — or, given a merchant host plus the merchant's own itemId, prepare/re-check NORMALIZED CHECKOUT EVIDENCE over the merchant's declared UCP/ACP checkout data: items, currency, subtotal, discount, tax, fees, shipping, total, fulfillment, policy links, expiry and an evidence hash, with bounded truth states 'verified' / 'changed' / 'unsupported' / 'unavailable' / 'unverified'. Pass priorEvidence (component hashes from an earlier answer) to detect price/stock/shipping/terms changes between preparation and re-check. 'verified' means fetched, parsed and internally consistent — never 'safe', never 'approved', never a guarantee the merchant honors the quote. A price is never guessed. Answers come from the queried source at the stated retrieval time — a UCP or ACP merchant, a partner catalog source, or a clearly-labelled synthetic fixture in dev/test; provenance.sourceAuthority names which, and every answer carries the markets that source declares. Preflight evidence only — this server never places, modifies or cancels an order and never touches a payment; the merchant stays merchant of record.
| Name | Type | Req | Description |
|---|---|---|---|
| ean | string | – | EAN/GTIN of the product. |
| itemId | string | – | The merchant's own item id (required with merchant). |
| merchant | string | – | A merchant hostname for checkout evidence (must be on this deployment's allowlist or served by a configured provider). |
| priorEvidence | object | – | componentHashes from a prior evidence answer — presence turns this call into a re-check with per-component change detection. |
| publicRecordId | string | – | A public record id from a prior search. |
| quantity | integer | – | Quantity for the checkout evidence quote (default 1). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
search_retail_products Search retail products ~221
Search the queried retail source by free text or EAN. Returns CANDIDATE public records with deterministic match kinds and visible ambiguity: 'exact_public_record' / 'possible_match' / 'multiple_matches' / 'no_match_in_queried_source' — a no-match is never 'not sold', only 'not in the source we queried'. A provider without a search surface → 'unsupported'; outage → 'unavailable'; unconfigured source → 'not_configured' (costs nothing). Answers come from the queried source at the stated retrieval time — a UCP or ACP merchant, a partner catalog source, or a clearly-labelled synthetic fixture in dev/test; provenance.sourceAuthority names which, and every answer carries the markets that source declares. Preflight evidence only — this server never places, modifies or cancels an order and never touches a payment; the merchant stays merchant of record.
| Name | Type | Req | Description |
|---|---|---|---|
| ean | string | – | EAN/GTIN for an exact lookup. |
| query | string | – | Free-text search (title/brand). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
How do I install the Jithox Commerce Preflight MCP server?
Jithox Commerce Preflight is a hosted endpoint at https://commerce.mcp.jithox.com/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 · commerce.mcp.jithox.com
claude mcp add --transport http com-jithox-be-commerce-preflight 'https://commerce.mcp.jithox.com/mcp'
What is the Jithox Commerce Preflight MCP server?
Jithox Commerce Preflight is an MCP server listed in the public MCP registry as com.jithox/be-commerce-preflight. Read-only commerce/checkout preflight (UCP/ACP). Returns evidence, never places orders. This page covers its hosted endpoint (https://commerce.mcp.jithox.com/mcp).
Is the Jithox Commerce Preflight MCP server safe to use?
Jithox Commerce Preflight scores 15 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 Jithox Commerce Preflight MCP server expose?
Jithox Commerce Preflight exposes 5 tools: search_retail_products, get_product_offer, compare_product_offers, build_affiliate_buy_link, get_commerce_readiness. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.
Does the Jithox Commerce Preflight MCP server require authentication?
Its publisher declares no required credentials for Jithox Commerce Preflight. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Jithox Commerce Preflight MCP server still maintained?
Jithox Commerce Preflight is marked deprecated in the MCP registry. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.