# Ivory River — Agent Commerce (remote · mcp.ivoryriver.store)

Search, configure, quote, recommend gaming PCs and components. Hands user to in-browser checkout.

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

## Components

- remote · `mcp.ivoryriver.store`: 55/100 (this document), [markdown](https://verifymcp.io/servers/store-ivoryriver-agent-commerce/mcp.md), [page](https://verifymcp.io/servers/store-ivoryriver-agent-commerce/mcp)

## Channel facts

- Endpoint: `https://mcp.ivoryriver.store/sse`
- Transports: `sse`
- Auth: `none`
- Version: `0.1.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**: 46/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 8 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 check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 766 tokens (~95/item across 8 items; 8 tools + 0 resources), lean.
  - 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**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **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 store-ivoryriver-agent-commerce https://mcp.ivoryriver.store/sse
```

### Codex

```toml
[mcp_servers.store-ivoryriver-agent-commerce]
url = "https://mcp.ivoryriver.store/sse"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "store-ivoryriver-agent-commerce": {
      "type": "remote",
      "url": "https://mcp.ivoryriver.store/sse",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add store-ivoryriver-agent-commerce --url https://mcp.ivoryriver.store/sse --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  store-ivoryriver-agent-commerce:
    url: "https://mcp.ivoryriver.store/sse"
```

### Other

```json
{
  "mcpServers": {
    "store-ivoryriver-agent-commerce": {
      "type": "http",
      "url": "https://mcp.ivoryriver.store/sse"
    }
  }
}
```

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 55, +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 54, +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 53, −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 55, −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 56, +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-28 (score 55, +1)

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

### 2026-07-27 (score 54, 0)

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

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

First indexed and scored.

## MCP tools (8)

### `search_products` (~85 tokens)

Search the Ivory River catalog with semantic + keyword hybrid ranking. Use for natural-language queries like "rtx 5090 laptop under $3000" or "case for AM5 build with tempered glass".

Input parameters:

- `in_stock` (boolean): Whether to exclude out-of-stock items. Default true.
- `limit` (integer)
- `query` (string, required): Free-text search query.

### `get_product` (~61 tokens)

Get full detail for a single product by ID. Includes price, stock, attributes, and (for BYOPC builds) a configurator summary.

Input parameters:

- `fields` (string): Optional comma-separated field projection.
- `id` (integer, required): WooCommerce product ID.

### `list_builds` (~54 tokens)

List the four BYOPC tiers (Squire, Knight, DragonSlayer, Archangel) with their base prices and aggregate component summaries. Use this to overview what custom-build options exist before drilling into a specific tier.

### `list_build_options` (~97 tokens)

Pull the full configurator schema for a single BYOPC tier: every field (Processor, Motherboard, GPU, RAM, Storage, etc.) with all child product options including price, stock, and IDs. Use this to see what selections are available before quoting.

Input parameters:

- `tier_id` (integer, required): BYOPC tier product ID. 378 Squire, 459 Knight, 371 DragonSlayer, 460 Archangel.

### `quote_build` (~92 tokens)

Itemize a configured BYOPC build: returns line totals + grand total + pairwise compatibility check. Empty selections are valid -- the server auto-fills the cheapest in-stock option for any required field.

Input parameters:

- `selections` (object): Object mapping field_id (string) → child_product_id (integer). E.g. {"123": 456, "789": 101}.
- `tier_id` (integer, required)

### `check_compatibility` (~63 tokens)

Pairwise socket / DDR / form-factor compatibility check between two products. Returns { compatible, reason }. Use before recommending a CPU + motherboard pairing or RAM + motherboard.

Input parameters:

- `product_id_1` (integer, required)
- `product_id_2` (integer, required)

### `recommend_build` (~99 tokens)

Recommend BYOPC desktop tiers, optionally filtered by budget. `use_case` is informational (echoed in metadata) and helps the agent reason; the result is sorted by total ascending. For laptop recommendations, call search_products with category="laptops" instead.

Input parameters:

- `budget` (number): USD ceiling. Builds with total > budget are dropped.
- `use_case` (string): Free-form e.g. "competitive FPS gaming", "video editing".

### `get_aivy_handoff_link` (~215 tokens)

Build the URL the agent hands to the user to finalize a recommendation. Lands the user on ivoryriver.store with the chat widget auto-opened, the agent's recommendation pre-staged, and quick-reply chips: [Yes, add to cart] [Show me the breakdown] [Modify components]. Use this AFTER you've recommended a build (via recommend_build / list_build_options / quote_build) and the user wants to proceed. The user always finishes the purchase in the browser; you never check out.

Input parameters:

- `agent_name` (string): How the agent should be named in the handoff greeting (e.g. "Claude Desktop", "Cursor", "your AI assistant"). Cosmetic; defaults to "your AI assistant".
- `context` (string): Optional one-line summary of what the user originally asked (e.g. "streaming + 4K editing under $2K"). Shown to the chat backend so Aivy understands the original ask.
- `recommendation` (object, required): The recommendation to hand off.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/store-ivoryriver-agent-commerce/mcp#diagnostics

## Score history

- 2026-08-03: 55
- 2026-08-02: 54
- 2026-08-01: 54
- 2026-07-31: 53
- 2026-07-30: 55
- 2026-07-29: 56
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 54

## Links

- Remote endpoint: https://mcp.ivoryriver.store/sse
- Website: https://ivoryriver.store/
- Changelog RSS feed: https://verifymcp.io/servers/store-ivoryriver-agent-commerce/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/store-ivoryriver-agent-commerce/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/store-ivoryriver-agent-commerce/mcp