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 分

    请在仓库或注册中心条目中声明许可证。