Skip to main content
Glama
deenesjakoruzh
greencore-solutions

MCP GSC AI Agent Carrier Class Fleet

Official
by greencore-solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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

Related MCP server: wellknown-mcp

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.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • DefenseOps Aerospace MCP

    jdbruh18
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides aerospace fleet telemetry monitoring, Mil-Spec RAG search, fleet maintenance queries, sandboxed mission log exports, and tactical alert dispatching.
    MIT

  • wellknown-mcp

    sanemavcil
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to discover, resolve, verify, and monitor AI agents and MCP servers from the Wellknown live index, including observed liveness, reliability, and ownership claims.
    33 npm
    MIT

  • agent-mailbox

    00cyre
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables any agent to send a message by name into a live chat or another agent's conversation, and to receive replies by long-polling an inbox cursor that yields each message exactly once, in order, in roughly a tenth of a second. Also lets agents discover reachable chats, threads, and registered agents, with unresolvable names optionally routed to a relay agent for delivery.
    0
    MIT

  • MCP Harbor

    youyouhe
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables agents and projects to register identities, publish and discover contract manifests (berths), resolve dependencies and check compatibility, and subscribe to or broadcast contract-change notifications over MCP tools and resources. It also supports isolated agent-to-agent messaging and an admin overview of participants, berths, subscriptions, and audit history.
    -