mcpbeat

PuroAir MCP Server

ai.agenticshelf/puroair
answering

PuroAir is answering right now. Last checked moments ago. It exposes 7 tools.

Breathe with Confidence. Live MCP catalog for PuroAir HEPA air purifiers - stock, pricing, details.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
318 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add puroair --transport http https://api.agenticshelf.ai/m/puroair/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "puroair": {
      "url": "https://api.agenticshelf.ai/m/puroair/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.puroair]
url = "https://api.agenticshelf.ai/m/puroair/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "puroair": {
      "url": "https://api.agenticshelf.ai/m/puroair/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "puroair": {
      "url": "https://api.agenticshelf.ai/m/puroair/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

products
list_products
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
search_products
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.
cart
add_to_cart
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).
checkout
create_checkout
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).
price
get_price
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"}
product
get_product_details
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``.)
stock
check_stock
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" }

Endpoints

URLTransportStateLatencyChecked
https://api.agenticshelf.ai/m/puroair/mcp streamable-http answering 342 ms 0 min ago

PuroAir — questions

Answers built from our own checks of this server.

What can PuroAir do?
It exposes 7 tools, read directly from the server on our last check. Among them: add_to_cart, check_stock, create_checkout, get_price, get_product_details, list_products and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is PuroAir working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 318 ms. The bar chart above shows every period we have measured.
How do I connect PuroAir?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PuroAir need an API key?
No. PuroAir completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PuroAir?
It answers our handshake in 318 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.