Connect GSC Carrier Fleet — discovery and your agent gets 10 tools, among them find_carriers, get_carrier_doctrine, get_fleet. It answers at https://mcp.gsc-fleet.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 7 of 7 times since 8 September 2026; the last check, on 18 October 2026, succeeded.
The discovery surface of the GSC AI Agent program: 32,597 LIVE AI Agents (22,597 Carriers + 10,000 AIO Agents) across eighteen resident jurisdictions, resolved by fleet, jurisdiction and carrier over MCP (streamable-http). AIO Agents resolve on mcp.gsc-marketplace.ai. Operated by GreenCore Solutions Corp.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 h Inputs: node, category |
get_carrier_doctrine | The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's. |
get_fleet | Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern. Inputs: fleet |
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_residency_receipt | How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove. |
how_to_transact | Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each. |
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 surf |
list_jurisdictions | Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim. |
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. Inputs: fleet, slot |
resolve_jurisdiction | Member code → residency status, serving endpoint, and Azure region. Inputs: code |
Every block below points at https://mcp.gsc-fleet.ai/mcp. Pick your client and copy.
claude mcp add --transport http gsc-carrier-fleet-discovery https://mcp.gsc-fleet.ai/mcp
{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.gsc-fleet.ai/mcp"]
}
}
}{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}{
"servers": {
"gsc-carrier-fleet-discovery": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}{
"context_servers": {
"gsc-carrier-fleet-discovery": {
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"serverUrl": "https://mcp.gsc-fleet.ai/mcp"
}
}
}{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}name: GSC Carrier Fleet — discovery
version: 0.0.1
schema: v1
mcpServers:
- name: GSC Carrier Fleet — discovery
type: streamable-http
url: https://mcp.gsc-fleet.ai/mcp{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"httpUrl": "https://mcp.gsc-fleet.ai/mcp"
}
}
}{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}{
"mcpServers": {
"gsc-carrier-fleet-discovery": {
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.gsc-fleet.ai%2Fmcp&type=streamable_http&id=gsc-carrier-fleet-discovery&name=GSC%20Carrier%20Fleet%20%E2%80%94%20discovery
It answered our last check on 18 October 2026 in 496 ms. Over 7 checks since 8 September 2026 it answered 7. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by gsc-fleet.ai and served from mcp.gsc-fleet.ai, the vendor's own domain: https://mcp.gsc-fleet.ai/mcp.
10, as returned by the server's own tools/list on 8 September 2026: find_carriers, get_carrier_doctrine, get_fleet, get_fleet_stats, get_residency_receipt, how_to_transact, list_fleets, list_jurisdictions, and 2 more.
It answered our last check on 18 October 2026 in 496 ms. Over 7 checks since 8 September 2026 it answered 7.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.gsc-fleet.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: mcp.gsc-fleet.ai. Endpoint host: mcp.gsc-fleet.ai. ARD identifier: urn:air:mcp.gsc-fleet.ai:fleet:discovery-mcp.
First indexed 8 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.