ittems product directory

com.ittemsPublished by ittems.comOfficial publisherv0.2.3Updated Oct 24, 2026

Merchant product catalogs for AI agents: price, availability, specs, variants, buy links. Read-only.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant look up merchant product catalogs — prices, availability, specs, variants and buy links — through a read-only remote endpoint.

What you can do
This remote MCP server exposes merchant product catalog data to AI agents. According to its description, it covers price, availability, specs, variants and buy links, and it is described as read-only. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when an assistant needs to answer product questions such as current pricing, stock status, specifications, variant options or where to buy, and when a read-only catalog lookup is enough.
Requirements
Nothing is declared: no packages, no authentication, no environment variables and no headers. It runs as a remote streamable HTTP endpoint at the provider's site, so network access to that endpoint is required.
Before you install
The manifest declares no authentication and no credentials, so no secrets are requested. Product data comes from a third party and may be incomplete or out of date; verify prices, availability and buy links before relying on them. The description states the server is read-only, so it should not change any data.

Installation

In SourceWeft

  1. Open ittems product directory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.ittems%2Fcatalog/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ittems-product-directory": {
      "type": "http",
      "url": "https://ittems.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.3LatestOct 15, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.