eCommerce

studio1beauty.com

Provides access to Studio 1 Beauty's product catalog with hair-care enrichment, hair-profile matching, availability checks, and store facts for e-commerce applications.

1 endpoint5 known toolsFirst detected August 23, 2026Last detected August 23, 2026

ENDPOINT 1

https://vi.studio1beauty.com/mcp

No auth detected

MCP server metadata

Name: studio-1-beauty-vi
Version: 1.1.0

Capabilities

tools

Server instructions

Read-only, enriched catalog access for Studio 1 Beauty — professional hair care from salon brands. Each product carries hair-care enrichment (hair types, concern tags, key ingredients, a Vi summary) beyond vanilla commerce data. match_products_to_hair scores products against a real hair profile using the same scoring rubric Vi itself uses (scores are computed, never invented). GLOW Bucks = store credit: customers earn a flat 10% back on every order — no tiers — credited 30 days after the order; redemption at checkout is coming "at launch" and is not yet live. No photo analysis. Checkout/cart writes are handled by Shopify Universal Commerce Protocol, not by these tools.

Known tools 5

search_products

Search the Studio 1 Beauty catalog and return matching products WITH hair-care enrichment (hair_types, hair_concerns, key_ingredients, ingredients_full, benefits, best_for, porosity, is_color_safe, is_sulfate_free, vi_summary), price, availability, GLOW Bucks earned, and a safety block (sensitivity_safe / pregnancy_safe / free_from).

Inferred read-only

get_product

Fetch a single Studio 1 Beauty product by its handle, with full hair-care enrichment, the same tri-state safety block as search_products, all variants (size/price/availability), and GLOW Bucks earned.

Inferred read-only

match_products_to_hair

Score catalog products against a real hair profile — scored by Studio 1’s patent-pending hair-match methodology, the SAME rubric Vi itself uses (porosity, ingredients, damage — weighted; scores computed, never invented).

Inferred read-only

check_availability

Live buyability for up to 20 products at once, by handle — product-level availability plus every variant with its price, availability and quantity where the catalog reports one.

Inferred read-only

get_store_facts

Canonical Studio 1 Beauty facts for agents: shipping ($150 free threshold; otherwise calculated at checkout — no flat rate), 30-day returns, GLOW Bucks store credit (10% back), heritage since 1976, contact.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.studio-1-beauty-vi]
url = "https://vi.studio1beauty.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "studio-1-beauty-vi": {
      "type": "http",
      "url": "https://vi.studio1beauty.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: studio-1-beauty-vi
Remote MCP URL: https://vi.studio1beauty.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "studio-1-beauty-vi": {
      "url": "https://vi.studio1beauty.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "studio-1-beauty-vi": {
      "type": "http",
      "url": "https://vi.studio1beauty.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "studio-1-beauty-vi",
  "transport": "streamable-http",
  "url": "https://vi.studio1beauty.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for studio1beauty.com was fetched 2026-08-25T17:29:58.130Z.

Trust status Trusted

studio1beauty.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.