MCP GSC AI Agent Carrier Class Fleet

Last 30 days

Uptime

100%

Response time

206 ms typical, 206 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "mcp-gsc-ai-agent-carrier-class-fleet": {
      "type": "http",
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}

11 tools

• list_fleets

  The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points. Headline: 32,597 LIVE AI Agents — the 32,500+ AI Agent program: 19,597 Carriers on the fleet roots and 14 sovereign nodes, 3,000 on the APP surfaces, 10,000 AI Orderability (AIO) Agent

• get_fleet

  Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.

• resolve_carrier

  (fleet, slot) → the canonical Card URL. Validates the slot against the fleet's real range; the Card itself is the source of truth — fetch it to confirm the Carrier.

• find_carriers

  SM-ECO-10060 member code → the serving surface: a resident sovereign endpoint where one exists, otherwise the fleet root covering that member's region. Category and capability addressing ship with the sovereign Carrier set and will answer here as they go live.

• list_jurisdictions

  Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.

• resolve_jurisdiction

  Member code → residency status, serving endpoint, and Azure region.

• get_residency_receipt

  How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.

• get_fleet_stats

  Canon numbers: 32,597 LIVE AI Agents (32,500+ AI Agent program: 22,597 Carriers + 10,000 AIO Agents) across eighteen resident jurisdictions. Monthly transaction volume is published at gsc-radar.ai — the source of record.

• get_carrier_doctrine

  The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.

• how_to_transact

  Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.

• ask_elyssah

  Ask GSC's AI assistant elyssah a question about GSC, its AI Agents for Beauty & Personal Care brands, the numbers of record, the AI investment market per the analysts, management or coverage. Returns the same JSON the human desk gets: answer {q, a, id, anchor, door} served byte f

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks