MCP GSC AI Agent Carrier Class Fleet

io.github.greencore-solutions由 GitHub 帳號 greencore-solutions 發布v1.6.1更新於 Oct 24, 2026

BPC Sustainable Carrier Agents - Low Token Zero Inference

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取商業與電商

概覽

AI 產生的概覽

GSC AI Agent Carrier 艦隊的遠端探索伺服器,讓助理查詢艦隊、司法管轄區、Carrier 卡片與駐留聲明。

可以做什麼
列出並檢視各艦隊,包括區域、槽位範圍,以及各艦隊根與主權節點群的目錄資訊,並讀取已發布的艦隊統計與 Carrier 準則文本。將艦隊與槽位解析為標準的 Carrier 卡片網址,或把成員代碼對應到為其提供服務的入口或端點。列出 Carrier 駐留的十八個司法管轄區,並把成員代碼解析為駐留狀態、服務端點與 Azure 區域。說明如何透過回應標頭驗證駐留聲明,以及資料、探索、交易與標準四類用途分別該用哪個 GSC 入口。向 GSC 的助理提問有關 GSC、其美妝與個人護理品牌代理及已發布數字的問題。
適用情境
當你需要定位某個 GSC Carrier、確認某成員代碼由哪個艦隊或管轄區服務,或在依賴某項駐留聲明前了解如何驗證時適用。也適合詢問 GSC 已發布的代理數量與定位。
執行需求
遠端 streamable-HTTP 端點;未宣告任何套件、環境變數或標頭,也未宣告身分驗證。需要能連線到 GSC 端點的網路。
安裝前請注意
此伺服器只做唯讀探索,但其數字是 GSC 對自家代理艦隊的宣傳說法;README 聲明其中任何數字都不是權威資料,艦隊實況應以線上解析為準。授權尚未確定:未提交授權檔案,條款被描述為待定。向內建助理提出的問題會傳送到 GSC 的服務。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 MCP GSC AI Agent Carrier Class Fleet,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.greencore-solutions%2Fgsc-fleet-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "gsc-ai-agent-carrier-class-fleet": {
      "type": "http",
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}

README

MCP GSC AI Agent Carrier Class Fleet

Surface role: DISCOVERY — one of the four GSC surfaces (data · discovery · transaction · standards).

Find Carriers: which fleet, which jurisdiction, how to reach a Card.

Canonical endpointhttps://mcp.gsc-fleet.ai/mcp (streamable-http)
Apex / websitehttps://gsc-fleet.ai
Registry listingio.github.greencore-solutions/gsc-fleet-mcp v1.0.0
OperatorGreenCore Solutions Corp. — Microsoft AI Cloud Partner
ProtocolACM-68000 · sovereign manifest SM-ECO-10060

Registry tile text (verbatim)

Title: MCP GSC AI Agent Carrier Class Fleet Description: BPC Sustainable Carrier Agents - Low Token Zero Inference

What it serves

Ten MCP read tools — list_fleets, get_fleet, resolve_carrier, find_carriers, list_jurisdictions, resolve_jurisdiction, get_residency_receipt, get_fleet_stats, get_carrier_doctrine, how_to_transact — plus broadcast JSON (/fleets.json, /jurisdictions.json, /stats.json, /doctrine.json, /surfaces.json), a brochure root, and three .well-known cards.

Stateless: fleet truth is compiled in; the Carrier Cards themselves stay the single source. No database, no secrets.

Releases

tagsourcedeployed image digestnote
v1.0.0b49d3ddsha256:fd126d7e2a02Discovery surface goes live; completes the four-surface set
v1.1.0this headsha256:8d1c003cfd26Sovereign resident flip — revision gsc-fleet-mcp--0000006

Fleet truth is live, not embedded: this MCP surface is the single source for fleet composition — resolve it on the wire, not from this README. Monthly transaction volume is published at gsc-radar.ai — the source of record. No figure in this README is canonical.

The four surfaces

surfaceendpoint
datahttps://mcp.cpgknowledgegraph.ai
discoveryhttps://mcp.gsc-fleet.ai
transactionhttps://mcp.cpghumanintheloop.ai
standardshttps://mcp.cpgagentprotocols.ai

Residency is checkable

Every response carries its identity on the wire. x-gsc-jurisdiction is the receipt; x-gsc-timestamp and x-gsc-nonce are per-request proof of liveness. Header canon: https://mcp.cpgagentprotocols.ai/headers.json

Licensing

No license file is committed. GSC MCP server code is under a hybrid MIT + Commercial Enterprise arrangement; the counsel-drafted terms are pending. Until they land, absence of a LICENSE file is deliberate — not an oversight.

來源:README.md,提交 8e4b5e3

工具

11

list_fleets

List the GSC Carrier 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.

無需輸入參數。

get_fleet

Get one fleet

Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.

輸入參數fleet必填

resolve_carrier

Resolve a Carrier Card URL

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

輸入參數slot必填fleet必填

find_carriers

Find Carriers for a jurisdiction

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.

輸入參數node必填category

list_jurisdictions

The sovereign deployment map

Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.

無需輸入參數。

resolve_jurisdiction

Resolve one jurisdiction

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

輸入參數code必填

get_residency_receipt

The residency receipt

How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.

無需輸入參數。

get_fleet_stats

Fleet statistics

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_carrier_doctrine

What a Carrier is

The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.

無需輸入參數。

how_to_transact

The four GSC surfaces

Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.

無需輸入參數。

ask_elyssah

Ask elyssah — GSC's AI assistant

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.

輸入參數q必填prev

版本歷史

2
  1. v1.6.1最新Sep 17, 2026
  2. v1.0.0Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。