io.github.greencore-solutionsPublished by GitHub account greencore-solutionsv1.6.1Updated Oct 24, 2026
BPC Sustainable Carrier Agents - Low Token Zero Inference
A remote discovery server for GSC's AI Agent Carrier fleet, letting an assistant look up fleets, jurisdictions, carrier cards and residency claims.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.greencore-solutions%2Fgsc-fleet-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"gsc-ai-agent-carrier-class-fleet": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}Surface role: DISCOVERY — one of the four GSC surfaces (data · discovery · transaction · standards).
Find Carriers: which fleet, which jurisdiction, how to reach a Card.
Title: MCP GSC AI Agent Carrier Class Fleet Description: BPC Sustainable Carrier Agents - Low Token Zero Inference
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.
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.
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
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.
Source: README.md at commit 8e4b5e3
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.
Takes no parameters.
Get one fleet
Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.
fleetrequiredResolve 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.
slotrequiredfleetrequiredFind 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.
noderequiredcategoryThe sovereign deployment map
Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.
Takes no parameters.
Resolve one jurisdiction
Member code → residency status, serving endpoint, and Azure region.
coderequiredThe residency receipt
How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
The four GSC surfaces
Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
Takes no parameters.
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.
qrequiredprev90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.