Connect-MCP

MCP GSC AI Agent Carrier Class Fleet

io.github.greencore-solutions/gsc-fleet-mcp · v1.6.1

BPC Sustainable Carrier Agents - Low Token Zero Inference

MCPremoteno credentialsCloud & DevOps

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 11 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 95/100

What it does: 11 tools · 9 read, 0 write · Developer tools, Cloud & DevOps

Test call list_fleets: worked (1,052 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: 0
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://mcp.gsc-fleet.ai/mcp

Tools

11 tools listed at last check
  • 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 the fleet roots and 14 sovereign nodes, 3,000 on the APP surfaces, 10,000 AI Orderability (AIO) Agents on the ten gsc-mar
  • get_fleet Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.
  • resolve_carrier (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.
  • find_carriers 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.
  • list_jurisdictions Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.
  • resolve_jurisdiction Member code → residency status, serving endpoint, and Azure region.
  • get_residency_receipt How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
  • 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 at gsc-radar.ai — the source of record.
  • get_carrier_doctrine The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.
  • how_to_transact Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
  • ask_elyssah Ask GSC's AI assistant elyssah a question about GSC, its AI Agents for Beauty & Personal Care brands, the numbers of record, the AI investment market per the analysts, management or coverage. Returns the same JSON the human desk gets: answer {q, a, id, anchor, door} served byte for byte from GSC's r

Badge

Connect-MCP badge for io.github.greencore-solutions/gsc-fleet-mcp

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.greencore-solutions/gsc-fleet-mcp.svg)](https://clawy.uk/mcp/s/io.github.greencore-solutions/gsc-fleet-mcp)

Repository · Website