MCP GSC AI Agent Carrier Class Fleet

BPC Sustainable Carrier Agents - Low Token Zero Inference

使うべきか

品質と安全性

B
説明の品質
90%
スキーマの完全性
62%
命名の品質
93%
ポイズニングのリスク
80%
権限の一致
100%
プロトコルへの準拠
100%

検出事項(5)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainask_elyssah 内
  • LOWTool 'list_fleets' description lacks action verblist_fleets 内
  • LOWTool 'resolve_jurisdiction' description lacks action verbresolve_jurisdiction 内
  • LOWTool 'how_to_transact' description lacks action verbhow_to_transact 内

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,198トークン数(ツール定義)
~499 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 0.94%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

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

できること

ツール一覧

ツール(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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

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

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

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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.

入力スキーマ

{
  "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#"
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 11 件
検証済みバージョンは記録されていませんツール 11 件
検証済みバージョンは記録されていませんツール 11 件