# io.github.tim777z/utopia-megastore (remote · utopia-orders.precogsecurity.workers.dev)

Tech store for AI agents: search, bundles, negotiation, payment splits, PayPal checkout.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `utopia-orders.precogsecurity.workers.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders.md), [page](https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders)

## Channel facts

- Endpoint: `https://utopia-orders.precogsecurity.workers.dev/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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 754 tokens (~107/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.tim777z/utopia-megastore MCP server?

io.github.tim777z/utopia-megastore is a hosted endpoint at https://utopia-orders.precogsecurity.workers.dev/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.

### Claude

```bash
claude mcp add --transport http tim777z-utopia-megastore 'https://utopia-orders.precogsecurity.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tim777z-utopia-megastore": {
      "url": "https://utopia-orders.precogsecurity.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tim777z-utopia-megastore": {
      "type": "http",
      "url": "https://utopia-orders.precogsecurity.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tim777z-utopia-megastore]
url = "https://utopia-orders.precogsecurity.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tim777z-utopia-megastore": {
      "type": "remote",
      "url": "https://utopia-orders.precogsecurity.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tim777z-utopia-megastore --url 'https://utopia-orders.precogsecurity.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tim777z-utopia-megastore:
    url: "https://utopia-orders.precogsecurity.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tim777z-utopia-megastore": {
      "Transport": "http",
      "Url": "https://utopia-orders.precogsecurity.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tim777z-utopia-megastore -t streamable-http -u 'https://utopia-orders.precogsecurity.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tim777z-utopia-megastore": {
      "type": "http",
      "url": "https://utopia-orders.precogsecurity.workers.dev/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-11-20 (score 71, +1)

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

### 2026-11-18 (score 70, +1)

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

### 2026-11-16 (score 69, +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-11-14 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_products” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 654 → 754
- [functional] New tool “list_sets”

### 2026-11-12 (score 67, +1)

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

### 2026-11-10 (score 66, +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-11-09 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 65)

First indexed and scored.

## MCP tools (7)

### `list_products` (~64 tokens)

List products and bundles

Return the full catalog: 15 products (id, name, price, bulk discount text, category, image, description, cj_vid, fits_with add-on ids), 4 bundles and 6 cross-subsidized sets, plus payment methods and free-shipping threshold.

### `list_sets` (~72 tokens)

List cross-subsidized sets and add-ons

Return the 6 curated sets. Each set discounts the big-ticket item while cheap fittings/add-ons keep near-retail margin, and exposes per-line bundle_price (sums to the set price) plus addon_options at set-only prices. Use this before create_checkout when a buyer wants a whole setup rather than single items.

### `search_products` (~52 tokens)

Search the catalog

Fuzzy/semantic product search over the catalog. Returns ranked matches with prices and any bundles that contain a match.

Input parameters:

- `query` (string, required): What the buyer is looking for, e.g. "charger for laptop"

### `suggest_bundle` (~91 tokens)

Build a set within a budget

Given the item ids a buyer wants and an optional budget, return the fixed bundles plus custom cross-subsidised combinations. Each custom entry gives retail, bundle price, savings and a per-line allocation so a multi-party split stays fair.

Input parameters:

- `budget` (number): Maximum total the buyer will pay in USD
- `items` (array): Product ids of interest, e.g. ["hi-res-earbuds"]

### `negotiate_price` (~89 tokens)

Negotiate a price

Propose a target total for a set of items. The server replies with the lowest price it can legally accept; the floor is supplier cost + 12% margin, and matching bundles override per-item pricing.

Input parameters:

- `budget` (number): Target total in USD
- `caller` (string): Stable identifier for the negotiating agent or buyer email
- `items` (array, required): Product ids to negotiate over

### `validate_split` (~65 tokens)

Validate a multi-agent payment split

Check that a proposed multi-recipient allocation sums exactly to the order total. Returns allocOk plus the discrepancy. Use before create_checkout when several agents share the cost.

Input parameters:

- `items` (array, required): Line items being purchased
- `split` (array, required): Each payer and what they owe

### `create_checkout` (~122 tokens)

Create an order and get a payment link

Create an order and receive a PayPal payment URL (cards, Google Pay, Apple Pay, Venmo). Nothing is charged here: the URL must be approved by whoever holds the funds. On payment capture the order is forwarded automatically to CJ Dropshipping with USPS last-mile.

Input parameters:

- `caller` (string): Identifier of the requesting agent
- `email` (string, required): Buyer email for the order receipt
- `items` (array, required): Line items to purchase
- `split` (array): Optional multi-payer allocation
- `total` (number, required): Order total in USD

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 66
- 2026-11-10: 66
- 2026-11-09: 65
- 2026-11-08: 65

## Common questions

### What is the io.github.tim777z/utopia-megastore MCP server?

io.github.tim777z/utopia-megastore is an MCP server listed in the public MCP registry as io.github.tim777z/utopia-megastore. Tech store for AI agents: search, bundles, negotiation, payment splits, PayPal checkout. This page covers its hosted endpoint (https://utopia-orders.precogsecurity.workers.dev/mcp).

### Is the io.github.tim777z/utopia-megastore MCP server safe to use?

io.github.tim777z/utopia-megastore scores 71 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 io.github.tim777z/utopia-megastore MCP server expose?

io.github.tim777z/utopia-megastore exposes 7 tools: list_products, list_sets, search_products, suggest_bundle, negotiate_price, and 2 more. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.

### Does the io.github.tim777z/utopia-megastore MCP server require authentication?

No. We connected to io.github.tim777z/utopia-megastore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.tim777z/utopia-megastore MCP server still maintained?

io.github.tim777z/utopia-megastore is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.tim777z/utopia-megastore MCP server?

VerifyMCP ran 12 checks on io.github.tim777z/utopia-megastore, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.tim777z/utopia-megastore: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://utopia-orders.precogsecurity.workers.dev/mcp
- Repository: https://github.com/tim777z/utopia-mcp
- Website: https://utopia-megastore.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders.xml
- Changelog JSON feed: https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders.json
- HTML version of this page: https://verifymcp.io/servers/tim777z-utopia-megastore/utopia-orders
