MCP GSC AI Agent Carrier Class Fleet
BPC Sustainable Carrier Agents - Low Token Zero Inference
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
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
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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.
Questions fréquentes
Qu'est-ce que MCP GSC AI Agent Carrier Class Fleet ?
BPC Sustainable Carrier Agents - Low Token Zero Inference
Comment installer MCP GSC AI Agent Carrier Class Fleet ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http mcp-gsc-ai-agent-carrier-class-fleet 'https://mcp.gsc-fleet.ai/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour MCP GSC AI Agent Carrier Class Fleet ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
MCP GSC AI Agent Carrier Class Fleet est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient MCP GSC AI Agent Carrier Class Fleet ?
Il est publié par greencore-solutions. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.