mcpserver.lol
registry/gsc-fleet-mcp
Connection check verified live · 27h ago

gsc-fleet-mcp

BPC Sustainable Carrier Agents - Low Token Zero Inference

Tools 10
GitHub stars
Installs / wk
Licence
Transport streamable-http
Last checked 27h ago

Tools & capabilities

10 tools

Read from the running server on 27h ago.

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 addr…
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.
get_fleet_stats
Canon numbers: 32,597 LIVE AI Agents (32,500+ AI Agent program: 22,597 Carriers + 10,000 AIO Agents) across eighteen resident jurisdictions. Monthly transaction volume is published…
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: 32,597 LIVE AI Agents — the 32,500+ AI Agent program: 19,597 Carriers on t…
list_jurisdictions
Where GSC Carriers are resident — eighteen 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.
resolve_jurisdiction code*
Member code → residency status, serving endpoint, and Azure region.