MCP GSC AI Agent Carrier Class Fleet

BPC Sustainable Carrier Agents - Low Token Zero Inference

Sollte ich dies verwenden

Qualität und Sicherheit

B
Qualität der Beschreibung
90%
Vollständigkeit des Schemas
62%
Qualität der Benennung
93%
Risiko der Vergiftung
80%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Befunde (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

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,198Tokens (Tool-Definitionen)
~499 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.94% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "gsc-fleet-mcp": {
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}

Remote-Endpunkte

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

Was es kann

Tool-Inventar

Tools (11)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢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.

Eingabe-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.

Eingabe-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.

Eingabe-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.

Eingabe-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.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪resolve_jurisdiction(code)

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

Eingabe-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.

Eingabe-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.

Eingabe-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.

Eingabe-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.

Eingabe-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.

Eingabe-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

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet11 Tools
verifiziertVersion nicht aufgezeichnet11 Tools