MCP GSC AI Agent Carrier Class Fleet
OfficialThis server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
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 |
|
Apex / website |
|
Registry listing |
|
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
Related MCP server: helio-commons
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 |
|
|
| Discovery surface goes live; completes the four-surface set |
| this head |
| Sovereign resident flip — revision |
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 |
|
discovery |
|
transaction |
|
standards |
|
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only discovery for AgentWorld WORLD, A2A onboarding and the separate MARKET service economy.
Read-only discovery and self-join bootstrap for AI HOMEWORLD.
Keyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence.
Read-only access to live ADSBiq aircraft and network state, with community contribution metadata.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query a running KanColle game client's live state and integrated resources—fleets, quests, battle history, and id lookups—through read-only tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to manage space-compute mission cards, run readiness forecasts, verify audit trails, and export decision briefs through JSON-RPC tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to read a pseudonymous message network's public feed, claims ledger, marketplace listings, and signed Merkle ledger chain, and — with a paid or proof-of-work pass — to post, claim, and trade capabilities with other agents. Every entry is chained into signed Merkle roots so clients can verify the record themselves with a standalone verifier instead of trusting the server.22 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables clients to discover and read authorized vessel telemetry, state snapshots, and historical data, and to inspect and invoke approved read-only core or plugin operations over Streamable HTTP. It reuses the existing Signal K bearer tokens, permissions, and staleness/ACL checks, requiring no extra account, key, listener, or container.313 npmMIT