Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Swervie

REMOTE · US-CENTRAL1-SWERVIE-PROD.CLOUDFUNCTIONS.NET

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

+3 this week 72 Trust /100

Last scanned (19 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability70
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Resource “swervie-results” now points somewhere else: ui://swervie/results-a4b603f3.html → ui://swervie/results-d87ba062.html security
  • 3 Nov 26 0
    • Resource “swervie-results” now points somewhere else: ui://swervie/results-cf24175d.html → ui://swervie/results-a4b603f3.html security
  • 1 Nov 26 +1
    • Resource “swervie-results” now points somewhere else: ui://swervie/results-b5de9b81.html → ui://swervie/results-cf24175d.html security
  • 31 Oct 26 0
    • Resource “swervie-results” now points somewhere else: ui://swervie/results-be1bd13a.html → ui://swervie/results-b5de9b81.html security
  • 30 Oct 26 +1
    • Resource “swervie-results” now points somewhere else: ui://swervie/results-ad8720dd.html → ui://swervie/results-be1bd13a.html security
  • 29 Oct 26 0
    • Resource “swervie-results” now points somewhere else: ui://swervie/results-f8662e18.html → ui://swervie/results-ad8720dd.html security
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://us-central1-swervie-prod.cloudfunctions.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=misc.google.com CN=WR2,O=Google Trust Services,C=US 7 Oct 2026 30 Dec 2026 ECDSA 256 SHA256-RSA d7114d20d626e8ea1224a33dd4c58644
SANs: misc.google.com, *.actions.google.com, *.baseline.google.com, *.developer.google.com, *.developers.google.com, *.ewoq.google.com, *.arvr.google.com, *.eu.aiapp.cloud.goog, *.eu.aiapp.cloud-staging.goog, *.eu.aiapp.cloud-test.goog, *.firebase.google.com, *.ggp.google.com and 394 more
CN=WR2,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a07c4cded100ad9d66a5107b98
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of us-central1-swervie-prod.cloudfunctions.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
cloudfunctions.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://us-central1-swervie-prod.cloudfunctions.net/mcp Verified 200
http (plaintext) http://us-central1-swervie-prod.cloudfunctions.net/mcp HTTPS enforced 302 https://us-central1-swervie-prod.cloudfunctions.net/mcp
MCP tools · 5 exposed · ~1,507 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
browse_category ~325

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.

NameTypeReqDescription
categorystringyes–
cursorstring––
filtersarray––
limitinteger––
preferencesarray–Soft preferences: rows that measure well on a dimension rank higher, and none are excluded. Each row reports preference_boost.
sortstring––
user_signaturestring–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)…

No output schema declared.

No examples provided.

find_category ~140

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.

NameTypeReqDescription
querystringyes–
user_signaturestring–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)…

No output schema declared.

No examples provided.

get_products ~214

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.

NameTypeReqDescription
idsarrayyes–
user_signaturestring–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)…

No output schema declared.

No examples provided.

lookup_product ~386

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.

NameTypeReqDescription
brandstring––
categorystring–Restrict the name match to one Swervie category (exact name).
identifiersobject–Known identifiers. mpn/model_number need brand to resolve.
querystring–The product's name as the shopper said it: brand, model, name. May contain an ASIN or barcode.
user_signaturestring–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)…

No output schema declared.

No examples provided.

search_products ~442

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.

NameTypeReqDescription
cursorstring––
limitinteger––
querystringyes–
sortstring––
user_signaturestring–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)…

No output schema declared.

No examples provided.

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.

remote · us-central1-swervie-prod.cloudfunctions.net

# add to Claude Code
claude mcp add --transport http swervie-swervie 'https://us-central1-swervie-prod.cloudfunctions.net/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.