MCP GSC AI Agent Carrier Class Fleet
BPC Sustainable Carrier Agents - Low Token Zero Inference
Should I use this
Quality & Safety
Findings (5)
- HIGHTool poisoning patterns detected
- MEDIUMTool description contains URL to non-standard domainin ask_elyssah
- LOWTool 'list_fleets' description lacks action verbin list_fleets
- LOWTool 'resolve_jurisdiction' description lacks action verbin resolve_jurisdiction
- LOWTool 'how_to_transact' description lacks action verbin how_to_transact
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"gsc-fleet-mcp": {
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}Remote endpoints
https://mcp.gsc-fleet.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (11)
🟢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) Agents on the ten gsc-marketplace.ai hosts.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_fleet(fleet)
Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.
Input Schema
{
"type": "object",
"properties": {
"fleet": {
"type": "string",
"enum": [
"global",
"apac",
"latam"
],
"description": "Fleet key"
}
},
"required": [
"fleet"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢resolve_carrier(fleet, slot)
(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.
Input Schema
{
"type": "object",
"properties": {
"fleet": {
"type": "string",
"enum": [
"global",
"apac",
"latam"
],
"description": "Fleet key"
},
"slot": {
"type": "string",
"pattern": "^\\d{4}$",
"description": "Four-digit slot number, e.g. 0001"
}
},
"required": [
"fleet",
"slot"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡find_carriers(node, category)
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.
Input Schema
{
"type": "object",
"properties": {
"node": {
"type": "string",
"maxLength": 4,
"description": "SM-ECO-10060 member code, e.g. UK, KR, BR"
},
"category": {
"type": "string",
"maxLength": 64,
"description": "Optional SPARKS category (answers as the sovereign set ships)"
}
},
"required": [
"node"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_jurisdictions
Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪resolve_jurisdiction(code)
Member code → residency status, serving endpoint, and Azure region.
Input Schema
{
"type": "object",
"properties": {
"code": {
"type": "string",
"maxLength": 4,
"description": "Member code, e.g. CH"
}
},
"required": [
"code"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_residency_receipt
How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢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.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_carrier_doctrine
The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪how_to_transact
Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪ask_elyssah(q, prev)
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 for byte from GSC's record (no model in the answer path), shelf (up to 3 related pairs on record), suggested links, and sig — the estate keyring signature (kid gsc-cards-2026-08) over {id, a, ts}, verifiable at https://gsc-registry.ai/keyring.json. Pass prev = the id of the last answer for one-turn context. Not investment advice.
Input Schema
{
"type": "object",
"properties": {
"q": {
"type": "string",
"minLength": 1,
"maxLength": 300,
"description": "The question, plain words, up to 300 characters"
},
"prev": {
"type": "string",
"maxLength": 40,
"description": "id of the last answer shown (one-turn context, ranking only)"
}
},
"required": [
"q"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence