MCP GSC AI Agent Carrier Class Fleet
BPC Sustainable Carrier Agents - Low Token Zero Inference
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http mcp-gsc-ai-agent-carrier-class-fleet 'https://mcp.gsc-fleet.ai/mcp'{
"mcpServers": {
"mcp-gsc-ai-agent-carrier-class-fleet": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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 endpoint | https://mcp.gsc-fleet.ai/mcp (streamable-http) |
| Apex / website | https://gsc-fleet.ai |
| Registry listing | io.github.greencore-solutions/gsc-fleet-mcp v1.0.0 |
| Operator | GreenCore Solutions Corp. — Microsoft AI Cloud Partner |
| Protocol | ACM-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
| tag | source | deployed image digest | note |
|---|---|---|---|
v1.0.0 | b49d3dd | sha256:fd126d7e2a02 | Discovery surface goes live; completes the four-surface set |
v1.1.0 | this head | sha256:8d1c003cfd26 | Sovereign 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
| surface | endpoint |
|---|---|
| data | https://mcp.cpgknowledgegraph.ai |
| discovery | https://mcp.gsc-fleet.ai |
| transaction | https://mcp.cpghumanintheloop.ai |
| standards | https://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.
Frequently asked questions
What is MCP GSC AI Agent Carrier Class Fleet?
BPC Sustainable Carrier Agents - Low Token Zero Inference
How do I install MCP GSC AI Agent Carrier Class Fleet?
It runs as a remote server. In Claude Code: claude mcp add --transport http mcp-gsc-ai-agent-carrier-class-fleet 'https://mcp.gsc-fleet.ai/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does MCP GSC AI Agent Carrier Class Fleet need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is MCP GSC AI Agent Carrier Class Fleet open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains MCP GSC AI Agent Carrier Class Fleet?
It is published by greencore-solutions. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.