eCommerce

cantonfashion.com

An MCP server for Canton Fashion that answers buyer questions, provides contact and quote-request details, and submits buyer inquiries on their behalf.

1 endpoint3 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://mcp.cantonfashion.com/mcp

No auth detected

MCP server metadata

Name: Canton Fashion MCP
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 3

answer_question

Answer a buyer question about Canton Fashion.

Inferred read-only

get_contact

Get Canton Fashion's contact details and how to request a quote.

Inferred read-only

submit_inquiry

Submit a buyer's inquiry to Canton Fashion on their behalf.

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.canton-fashion-mcp]
url = "https://mcp.cantonfashion.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "canton-fashion-mcp": {
      "type": "http",
      "url": "https://mcp.cantonfashion.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: canton-fashion-mcp
Remote MCP URL: https://mcp.cantonfashion.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": {
    "canton-fashion-mcp": {
      "url": "https://mcp.cantonfashion.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "canton-fashion-mcp": {
      "type": "http",
      "url": "https://mcp.cantonfashion.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "canton-fashion-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.cantonfashion.com/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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