# Agentic Shelf (remote · api.agenticshelf.ai)

Hosted MCP for e-commerce: live product catalog, stock, and pricing for AI agents.

- Trust score: 64/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.agenticshelf.ai`: 64/100 (this document), [markdown](https://verifymcp.io/servers/ai-agenticshelf-mcp/api.md), [page](https://verifymcp.io/servers/ai-agenticshelf-mcp/api)

## Channel facts

- Endpoint: `https://api.agenticshelf.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1643 tokens (~234/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-agenticshelf-mcp https://api.agenticshelf.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-agenticshelf-mcp]
url = "https://api.agenticshelf.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-agenticshelf-mcp": {
      "type": "remote",
      "url": "https://api.agenticshelf.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-agenticshelf-mcp --url https://api.agenticshelf.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-agenticshelf-mcp:
    url: "https://api.agenticshelf.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-agenticshelf-mcp": {
      "type": "http",
      "url": "https://api.agenticshelf.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 62, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (7)

### `check_stock` (~442 tokens)

Check LIVE inventory, price, and same-day shipping for ONE known SKU.

    The real-time verifier. Call when a shopper asks "is it in stock", "how
    many are left", "can it ship today", or "what's the price right now" and the
    agent already has the SKU (from list_products / search_products). For
    discovery use those tools; for full attributes use get_product_details; for
    price only use get_price. Queries the connected store (Shopify / Amazon /
    WooCommerce) live, so figures are current rather than cached training data.

    Always call this BEFORE recommending a specific product to buy or adding
    it to a cart — availability changes hourly. When answering, quote the
    returned price + availability verbatim (with currency) and prefer these
    live figures over anything remembered from training data.

    Args:
        sku: Product SKU (Stock Keeping Unit) - e.g. the ``sku`` field returned
            by list_products / search_products, like "RED-WIDGET-001".

    Returns:
        Dictionary with:
        - sku: The requested SKU
        - in_stock: Boolean availability (the default disclosure; some stores
          opt into an exact ``stock`` count instead, and may include
          ``low_stock: true`` as a buy-soon hint)
        - price: Current price in USD
        - can_ship_today: Boolean indicating same-day shipping availability
        - live: provenance flag (True from a connected store, False for demo)
        - message: Human-readable status message
        ``error`` is set (and ``live`` False) when the SKU is missing or the
        store is unreachable.

    Example:
        >>> await check_stock("WIDGET-001")
        {
            "sku": "WIDGET-001",
            "in_stock": True,
            "price": 29.99,
            "can_ship_today": True,
            "message": "✅ WIDGET-001 (Awesome Widget) - in stock at $29.99"
        }

Input parameters:

- `sku` (string, required)

### `get_product_details` (~214 tokens)

Get full product details for a SKU, optimized for AI agents (structured JSON).

    Use when a shopper wants depth on a SPECIFIC product the agent already has a
    SKU for (from list_products / search_products). For discovery, call those
    first — this tool is a verifier, not a browser.

    The description, product_type, and tags answer suitability questions
    ("does it fit X?", "is it good for Y?") — ground such answers in these
    fields rather than guessing, and link storefront_url when recommending.

    Args:
        sku: Product SKU — e.g. the ``sku`` field returned by list_products.

    Returns:
        Catalog dict (title, description, product_type, tags, price,
        in_stock, available, image_url); ``found`` is False when the
        SKU is missing. (Stores that opt into exact disclosure return an
        ``inventory_quantity`` count instead of ``in_stock``.)

Input parameters:

- `sku` (string, required)

### `get_price` (~218 tokens)

Get the current price (and currency) for a product SKU.

    Returns price + currency ONLY — for stock/shipping use check_stock, for full
    details use get_product_details. Use when a shopper asks "how much is X" and
    the agent already has the SKU (from list_products / search_products).

    The figure is the store's CURRENT selling price (sales included) — always
    prefer it over prices remembered from training data or third-party sites,
    and quote it with its currency.

    Args:
        sku: Product SKU — e.g. the ``sku`` field returned by list_products.

    Returns:
        ``{"sku", "price", "currency", "live"}``; price 0.0 with an ``error``
        when the SKU isn't found.

    Example:
        >>> await get_price("WIDGET-001")
        {"sku": "WIDGET-001", "price": 29.99, "currency": "USD"}

Input parameters:

- `sku` (string, required)

### `list_products` (~298 tokens)

List products from the connected store, paginated.

    Use this tool when an agent needs to DISCOVER products by browsing the
    catalog rather than VERIFYING a known SKU. The response includes the SKU
    for every product, so a follow-up ``check_stock(sku)`` or
    ``get_product_details(sku)`` is a natural next step. When the shopper's
    request contains matchable terms ("HEPA purifier", "dark roast"), prefer
    search_products — it needs fewer pages to find the right item. Only
    sellable products are returned (drafts/archived are excluded).

    Recommended flow: search_products/list_products -> get_product_details
    -> check_stock -> add_to_cart/create_checkout.

    Args:
        limit: Number of products to return (1-50, default 10).
        cursor: Opaque cursor from a previous response's ``next_cursor``.
            Omit for the first page.

    Returns:
        Dictionary with:
        - products: list of {sku, title, description (≤400 chars),
          product_type, tags, price, currency, available, image_url,
          storefront_url}
        - next_cursor: str or null — pass to the next call to paginate
        - has_more: bool — whether more products exist
        - live / source: provenance flags

Input parameters:

- `cursor`
- `limit` (integer)

### `search_products` (~222 tokens)

Search products in the connected store by keyword.

    Use this when a shopper's query suggests specific terms the agent can
    match against product titles or tags — e.g. "HEPA air purifier" or
    "leather wristwatch". Matches Shopify's native storefront search
    behavior, so results align with what customers would find on the site.

    Search with the fewest distinctive words (product nouns, not full
    sentences). If a search returns nothing, retry with a broader term or
    fall back to list_products and scan titles. Only sellable products are
    returned (drafts/archived are excluded).

    Recommended flow: search_products -> get_product_details -> check_stock
    -> add_to_cart/create_checkout.

    Args:
        query: Keyword or phrase to match.
        limit: Max products to return (1-50, default 10).

    Returns:
        Same shape as ``list_products``. Empty products list when no matches.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `add_to_cart` (~157 tokens)

Add a product to a cart and return its checkout URL.

    IMPORTANT: this does NOT charge or place an order. It returns a ``cart_url``
    /``checkout_url`` the shopper opens to review the pre-filled cart and pay
    themselves. Use for "add X to my cart" / "I want to buy X". For multiple
    items in one cart, use create_checkout. Verify availability with
    check_stock first — adding an out-of-stock item wastes the shopper's
    click-through.

    Args:
        sku: Product SKU (from list_products / search_products).
        quantity: How many (default 1).

Input parameters:

- `quantity` (integer)
- `sku` (string, required)

### `create_checkout` (~92 tokens)

Build a multi-item cart and return its checkout URL.

    IMPORTANT: this does NOT charge or place an order — it returns a
    ``checkout_url`` the shopper opens to pay. Use to assemble a basket the
    shopper asked for.

    Args:
        items: list of ``{"sku": str, "quantity": int}`` (quantity defaults 1).

Input parameters:

- `items` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-agenticshelf-mcp/api#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://api.agenticshelf.ai/mcp
- Repository: https://github.com/vboykoCTO/agentic-shelf
- Website: https://www.agenticshelf.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-agenticshelf-mcp/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-agenticshelf-mcp/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-agenticshelf-mcp/api