# Swervie (remote · us-central1-swervie-prod.cloudfunctions.net)

Cross-retailer product catalog: one scored answer per product with live prices and buy links.

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

## Components

- remote · `us-central1-swervie-prod.cloudfunctions.net`: 72/100 (this document), [markdown](https://verifymcp.io/servers/swervie-swervie/us-central1-swervie-prod.md), [page](https://verifymcp.io/servers/swervie-swervie/us-central1-swervie-prod)

## Channel facts

- Endpoint: `https://us-central1-swervie-prod.cloudfunctions.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2007 tokens (~286/item across 7 items; 5 tools + 2 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**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Swervie MCP server?

Swervie is a hosted endpoint at https://us-central1-swervie-prod.cloudfunctions.net/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 swervie-swervie 'https://us-central1-swervie-prod.cloudfunctions.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "swervie-swervie": {
      "url": "https://us-central1-swervie-prod.cloudfunctions.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "swervie-swervie": {
      "type": "http",
      "url": "https://us-central1-swervie-prod.cloudfunctions.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.swervie-swervie]
url = "https://us-central1-swervie-prod.cloudfunctions.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "swervie-swervie": {
      "type": "remote",
      "url": "https://us-central1-swervie-prod.cloudfunctions.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add swervie-swervie --url 'https://us-central1-swervie-prod.cloudfunctions.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  swervie-swervie:
    url: "https://us-central1-swervie-prod.cloudfunctions.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "swervie-swervie": {
      "Transport": "http",
      "Url": "https://us-central1-swervie-prod.cloudfunctions.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add swervie-swervie -t streamable-http -u 'https://us-central1-swervie-prod.cloudfunctions.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "swervie-swervie": {
      "type": "http",
      "url": "https://us-central1-swervie-prod.cloudfunctions.net/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-05 (score 72, 0)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-d87ba062.html → ui://swervie/results-5716f8fb.html

### 2026-11-04 (score 72, +1)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-a4b603f3.html → ui://swervie/results-d87ba062.html

### 2026-11-03 (score 71, 0)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-cf24175d.html → ui://swervie/results-a4b603f3.html

### 2026-11-01 (score 71, +1)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-b5de9b81.html → ui://swervie/results-cf24175d.html

### 2026-10-31 (score 70, 0)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-be1bd13a.html → ui://swervie/results-b5de9b81.html

### 2026-10-30 (score 70, +1)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-ad8720dd.html → ui://swervie/results-be1bd13a.html

### 2026-10-29 (score 69, 0)

- [security] Resource “swervie-results” now points somewhere else: ui://swervie/results-f8662e18.html → ui://swervie/results-ad8720dd.html
- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 69)

First indexed and scored.

## MCP tools (5)

### `find_category` (~140 tokens)

Find a product category

Find the Swervie product category that matches a shopping intent and return its filter contract: every filterable specification with its type, units, allowed values, and importance, plus budget, mid, and premium price bands.

Input parameters:

- `query` (string, required)
- `user_signature` (string): Optional opaque, stable, pseudonymous user id: the shopper's own rate-limit quota and click attribution. Format: 'sv1-' + the first 24 hex characters of SHA-256('swervie/v1|' + normalized identifier)…

### `browse_category` (~325 tokens)

Browse a category shelf

Return a category's consolidated, ranked shelf: one row per product, with duplicate seller listings already collapsed. Each row carries price, price_band, buy_url and buy_seller (the retailer behind the link), image_url, star ratings, and the category's required and top-weighted spec values. card_specs gives the specs every product card shows, in display order. Filters are hard: a row missing the attribute is excluded. Preferences are soft: rows that measure well on them rank higher and none are excluded (for example Rated Noise, prefer low, or a pet-hair rating, prefer high). Sort by value (default), quality, or price_asc. A filter on the Price dimension applies min/max to the live offer price in cents. Responses that carry buy_url links also carry a disclosure field: the commission disclosure for those links.

Input parameters:

- `category` (string, required)
- `cursor` (string)
- `filters` (array)
- `limit` (integer)
- `preferences` (array): Soft preferences: rows that measure well on a dimension rank higher, and none are excluded. Each row reports preference_boost.
- `sort` (string)
- `user_signature` (string): Optional opaque, stable, pseudonymous user id: the shopper's own rate-limit quota and click attribution. Format: 'sv1-' + the first 24 hex characters of SHA-256('swervie/v1|' + normalized identifier)…

### `search_products` (~442 tokens)

Search products

Answer one free-text shopping query, such as 'TVs under $500 with 120hz refresh rate', 'quiet dishwasher for a small kitchen', 'robot vacuum for pet hair under $600', or 'Sony WH-1000XM5 lowest price'. A query naming one specific product resolves to that product (interpretation.mode 'product'): products[0] holds every seller offer, and shelf_context gives its shelf rank and higher-scoring alternatives. 'A vs B' returns both products with specs in one shared order (mode 'comparison'). Otherwise the category is resolved, hard constraints such as price and specs become filters, and soft wishes such as 'quiet' or 'for pet hair' become ranking preferences that exclude nothing; interpretation.preferences lists them with reasons, and each row's preference_boost shows the effect. The interpretation object records how the query was read: method (deterministic parser or query-understanding model), fit_note (a one-line judgment of the category fit), and match_quality. 'strong' means the shelf plainly fits. 'partial' means either rows are served with some shopper words unexplained (listed in unparsed_tokens and unsupported_terms), or no rows are served because the closest shelf was only a medium-confidence fit (named in interpretation.llm_category). 'weak' and 'none' return no rows and queue the request as demand (queued_for_creation for a missing category, queued_product_request for a missing product). card_specs gives the specs every product card shows, in display order. Responses that carry buy_url links also carry a disclosure field: the commission disclosure for those links.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `query` (string, required)
- `sort` (string)
- `user_signature` (string): Optional opaque, stable, pseudonymous user id: the shopper's own rate-limit quota and click attribution. Format: 'sv1-' + the first 24 hex characters of SHA-256('swervie/v1|' + normalized identifier)…

### `lookup_product` (~386 tokens)

Look up a specific product

Look up one specific product by name or identifier: a product name such as 'Sony WH-1000XM5' or 'Ninja AF101 air fryer', an ASIN, a UPC/EAN/GTIN, or brand plus model number. match reports the result: 'exact' (identifier hit), 'likely' (one clear name match; interpretation.runner_up names the next best), 'ambiguous' (several fit; rows lists the candidates, best first), or 'none' (not carried; the miss is recorded as demand). On exact or likely, products[0] is the full detail (all specs, review-derived ratings with evidence quotes, every seller offer with buy_url), and shelf_context gives its rank on its category shelf by value and quality, its variants (colorways, sizes), and up to three higher-scoring alternatives in the same price band. A product with no live price or image is still returned, flagged under readiness; its price is not current. Responses that carry buy_url links also carry a disclosure field: the commission disclosure for those links.

Input parameters:

- `brand` (string)
- `category` (string): Restrict the name match to one Swervie category (exact name).
- `identifiers` (object): Known identifiers. mpn/model_number need brand to resolve.
- `query` (string): The product's name as the shopper said it: brand, model, name. May contain an ASIN or barcode.
- `user_signature` (string): Optional opaque, stable, pseudonymous user id: the shopper's own rate-limit quota and click attribution. Format: 'sv1-' + the first 24 hex characters of SHA-256('swervie/v1|' + normalized identifier)…

### `get_products` (~214 tokens)

Get product details

Full detail for up to 25 products: all specifications in the category's standard order (card_specs first), review-derived ratings with verbatim evidence quotes, every seller offer with price and buy_url, and attribute_provenance recording where each spec value came from (manufacturer page, retailer listing, spec table). ids accepts product ids and shelf row ids alike: a group row's id resolves to the product the row is named after (its top_pick_id), and resolved_groups reports each substitution. Responses that carry buy_url links also carry a disclosure field: the commission disclosure for those links.

Input parameters:

- `ids` (array, required)
- `user_signature` (string): Optional opaque, stable, pseudonymous user id: the shopper's own rate-limit quota and click attribution. Format: 'sv1-' + the first 24 hex characters of SHA-256('swervie/v1|' + normalized identifier)…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/swervie-swervie/us-central1-swervie-prod#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69

## Common questions

### What is the Swervie MCP server?

Swervie is an MCP server listed in the public MCP registry as io.github.Swervie/swervie. Cross-retailer product catalog: one scored answer per product with live prices and buy links. This page covers its hosted endpoint (https://us-central1-swervie-prod.cloudfunctions.net/mcp).

### Is the Swervie MCP server safe to use?

Swervie scores 72 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 Swervie MCP server expose?

Swervie exposes 5 tools: find_category, browse_category, search_products, lookup_product, get_products. Their descriptions and schemas cost roughly 1,507 tokens of context every time the server is loaded.

### Does the Swervie MCP server require authentication?

No. We connected to Swervie without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Swervie MCP server still maintained?

Swervie is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://us-central1-swervie-prod.cloudfunctions.net/mcp
- Repository: https://github.com/Swervie/swervie-mcp
- Website: https://swervie.xyz/developers
- Changelog RSS feed: https://verifymcp.io/servers/swervie-swervie/us-central1-swervie-prod.xml
- Changelog JSON feed: https://verifymcp.io/servers/swervie-swervie/us-central1-swervie-prod.json
- HTML version of this page: https://verifymcp.io/servers/swervie-swervie/us-central1-swervie-prod