ittems product directory
REMOTE · ITTEMS.COM
Merchant product catalogs for AI agents: price, availability, specs, variants, buy links. Read-only.
Available components
Last scanned (1 hour ago)
Scores higher than 43% of remote servers
Unreachable for 4 days in a row. Last reached 19 Oct 2026.
Category E-commerce
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 not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
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.
- 23 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Oct 26 0
- Server version: 0.5.0 → 0.5.2 functional
- 18 Oct 26 +1
- Server version: 0.4.3 → 0.5.0 functional
- 16 Oct 26 +3
- HSTS header: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.3 → 0.4.3 functional
- 15 Oct 26 66
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 23 Oct 2026 · Probed https://ittems.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of ittems.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| ittems.com. | Error no A/AAAA/CNAME RRset answered for the name |
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://ittems.com/mcp | Unreachable | ||
| http (plaintext) | http://ittems.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 →
get_merchant_policies Merchant shipping, returns and payment terms ~38
Shipping, processing, returns, payment and identity facts of one merchant, each with its source URL.
| Name | Type | Req | Description |
|---|---|---|---|
| merchant | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product Get one product in full ~58
Full detail for one product: specs, variants with price and availability, images, merchant policies, and page URLs (metadata.pages) for the compact markdown view.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | – | – | – |
| id | string | – | – |
| meta | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_merchants List merchants ~32
Merchants in the directory with product counts, domains, index URLs and their shipping, returns and payment terms.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
lookup_catalog Look up products by id ~59
Fetch up to 50 products by id ('ittems:<merchant>:<id>', '<merchant>/<slug>' or SKU). Unknown ids yield fewer products plus an info message.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | – | – | – |
| ids | – | – | – |
| meta | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
quick_search Compact search (names, prices, page links) ~53
Smaller answer than search_catalog: name, brand, price, availability, buy URL and the markdown page URL per hit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| merchant | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_catalog Search products ~125
Search products across all merchants (or one merchant) by free text, with optional brand, category and in-stock filters. UCP callers may pass the whole request under `catalog` and their profile under `meta`. Returns {ucp, products[], pagination{cursor, has_next_page, total_count}, policies[]}.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| catalog | – | – | – |
| category | – | – | – |
| cursor | – | – | – |
| in_stock | – | – | – |
| limit | integer | – | – |
| merchant | – | – | – |
| meta | – | – | – |
| query | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the ittems product directory MCP server?
ittems product directory is a hosted endpoint at https://ittems.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 · ittems.com
claude mcp add --transport http com-ittems-catalog 'https://ittems.com/mcp'
What is the ittems product directory MCP server?
ittems product directory is an MCP server listed in the public MCP registry as com.ittems/catalog. Merchant product catalogs for AI agents: price, availability, specs, variants, buy links. Read-only. This page covers its hosted endpoint (https://ittems.com/mcp).
Is the ittems product directory MCP server safe to use?
ittems product directory scores 42 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 ittems product directory MCP server expose?
ittems product directory exposes 6 tools: search_catalog, lookup_catalog, get_product, list_merchants, get_merchant_policies, quick_search. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.
Does the ittems product directory MCP server require authentication?
Its publisher declares no required credentials for ittems product directory. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ittems product directory MCP server still maintained?
ittems product directory is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.