RMCP.DEV
← Registry

Cloud Services

gsc-fleet.ai

Manages and resolves carrier fleet configurations and endpoints for global cloud infrastructure.

1 endpoint10 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.gsc-fleet.ai/mcp

No auth detected

MCP server metadata

Name
gsc-fleet
Version
1.5.1
Capabilities
tools.listChanged

Known tools 10

list_fleets

The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points.

Inferred read-only
get_fleet

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

Inferred read-only
resolve_carrier

(fleet, slot) → the canonical Card URL.

Inferred read-only
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.

Inferred read-only
list_jurisdictions

Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region.

Inferred read-only
resolve_jurisdiction

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

Inferred read-only
get_residency_receipt

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

Inferred read-only
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.

Inferred read-only
get_carrier_doctrine

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

Inferred read-only
how_to_transact

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

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.gsc-fleet]
url = "https://mcp.gsc-fleet.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "gsc-fleet": {
      "type": "http",
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: gsc-fleet
Remote MCP URL: https://mcp.gsc-fleet.ai/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": {
    "gsc-fleet": {
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "gsc-fleet": {
      "type": "http",
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "gsc-fleet",
  "transport": "streamable-http",
  "url": "https://mcp.gsc-fleet.ai/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 gsc-fleet.ai was fetched 2026-07-27T15:58:22.523Z and is being refreshed.

Trust status Neutral

gsc-fleet.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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