MCP GSC AI Agent Carrier Class Fleet
RemoteAbout MCP GSC AI Agent Carrier Class Fleet
A stateless discovery MCP server for BPC sustainable carrier fleets, intended for clients that need to identify fleets, jurisdictions, and carrier contact routes. It provides read tools and residency evidence in response headers.
Key features
- 01Look up fleets and carriers
- 02Resolve carrier and jurisdiction details
- 03Read fleet statistics and doctrine
- 04Check residency and response liveness
Use cases
- 01Find carriers for a jurisdiction
- 02Check fleet composition before a transaction
- 03Verify residency details from response headers
MCP support
Exposes ten read tools and broadcast JSON endpoints for fleet, jurisdiction, statistics, doctrine, and surface data. Responses include jurisdiction, timestamp, and nonce headers.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.gsc-fleet.ai/mcpclaude mcp add --transport http greencore-solutions-gsc-fleet https://mcp.gsc-fleet.ai/mcp{"mcpServers":{"greencore-solutions-gsc-fleet":{"type":"http","url":"https://mcp.gsc-fleet.ai/mcp"}}}Open in Cursor{"servers":{"greencore-solutions-gsc-fleet":{"type":"http","url":"https://mcp.gsc-fleet.ai/mcp"}}}Open in VS Code{"mcpServers":{"greencore-solutions-gsc-fleet":{"type":"http","url":"https://mcp.gsc-fleet.ai/mcp"}}}{"mcpServers":{"greencore-solutions-gsc-fleet":{"serverUrl":"https://mcp.gsc-fleet.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
11This tool takes no parameters.
Details
From the project READMEMCP 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.