mcp server
MCP GSC AI Agent Carrier Class Fleet
BPC Sustainable Carrier Agents - Low Token Zero Inference
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Most recent push to the repository was 2026-07-20.
What this server can do
10 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
find_carriers(node, category)- SM-ECO-10060 member code → the serving surface: a resident sovereign endpoint where one exists, otherwise the fleet root covering that member's region. Category and capability addressing ship with the sovereign Carrier set and will answer here as they go live. Required: node.
get_carrier_doctrine- The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.
get_fleet(fleet)- Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern. Required: fleet.
get_fleet_stats- Canon fleet numbers: 10,597 LIVE across nine sovereign jurisdictions, 9.5M agentic inbound signals per month, 1.5M human visits per month.
get_residency_receipt- How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
how_to_transact- Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
list_fleets- The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points. Headline: 10,597 LIVE across nine sovereign jurisdictions.
list_jurisdictions- Where GSC Carriers are resident — all nine jurisdictions, each with its serving Azure region. Residency is the checkable claim.
resolve_carrier(slot, fleet)- (fleet, slot) → the canonical Card URL. Validates the slot against the fleet's real range; the Card itself is the source of truth — fetch it to confirm the Carrier. Required: fleet, slot.
resolve_jurisdiction(code)- Member code → residency status, serving endpoint, and Azure region. Required: code.
Last successful function declaration observed on . Source: https://mcp.gsc-fleet.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.gsc-fleet.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-20 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-19 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-19 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 10 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.gsc-fleet.ai | |
| mcp endpoint status | ok | The server listed 10 functions when asked. | as of probe | mcp.gsc-fleet.ai |
Where to get it
Related, by what their authors tagged them
-
MCP CPG Agent Protocols
— last commit 2026-07-20, shares acm-68000, bpc, sm-eco-10060
BPC Agentic Commerce Signals
-
MCP CPG Human in the Loop (HITL)
— last commit 2026-07-20, shares acm-68000, bpc
Navigator for BPC Agentic Procurement
-
MCPfinder - MCP Server Discovery
— last commit 2026-07-01, shares discovery
Your AI discovers and installs MCP servers across Official Registry, Glama, and Smithery.
-
io.github.cinderwright-ai/cinderwright-api
— last commit 2026-08-02, shares discovery
Cross-protocol agent payments hub. x402, MPP, L402/Lightning. 1551 services indexed.
-
elisym
— last commit 2026-07-30, shares discovery
AI agent discovery, marketplace, messaging, and payments on Nostr - no platform, no middleman
-
MINT Protocol — Universal Work Attestation
— last commit 2026-07-19, shares discovery
Trust stack for AI agents: identity, attest, verify, rate, recommend, discover — on Solana.
These share tags the maintainers applied themselves, such as acm-68000, bpc, sm-eco-10060, discovery. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
Also from greencore-solutions
-
MCP CPG Knowledge Graph
— repository gone
BPC Agentic Commerce Infra
How the author describes it
Topics the maintainer set on GitHub: acm-68000, bpc, carrier-fleet, discovery, mcp, sm-eco-10060.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json