INDIVIDUAL MCP TOOL
get_residency_receipt
How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
LIVE ENDPOINT
https://mcp.gsc-fleet.ai/mcp
Connect to this endpoint to inspect the live schema for get_residency_receipt and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
list_fleets— The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points.get_fleet— Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.resolve_carrier— (fleet, slot) → the canonical Card URL.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.list_jurisdictions— Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region.resolve_jurisdiction— Member code → residency status, serving endpoint, and Azure region.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.get_carrier_doctrine— The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.