Skip to content

MCP GSC AI Agent Carrier Class Fleet

by greencore-solutions · remote · no sign-in to list tools · v1.6.1 · published by GitHub user greencore-solutions

BPC Sustainable Carrier Agents - Low Token Zero Inference

Changes · 3
CompareRegistry entry

11 tools: 3 change things and 8 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http gsc-fleet https://mcp.gsc-fleet.ai/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Changes things 3Claude Code: ask
  • ask_elyssahAsk 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 o…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 record (no model in the answer path), shelf (up to 3 related pairs on record), suggested links, and sig — the estate keyring signature (kid gsc-cards-2026-08) over {id, a, ts}, verifiable at https://gsc-registry.ai/keyring.json. Pass prev = the id of the last answer for one-turn context. Not investment advice.
  • how_to_transactWhich GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
  • resolve_jurisdictionMember code → residency status, serving endpoint, and Azure region.No findings

    Why it is in this group

    • The name "resolve_jurisdiction" says "resolve": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Member code → residency status, serving endpoint, and Azure region.
Only reads 8Claude Code: allow
  • find_carriersSM-ECO-10060 member code → the serving surface: a resident sovereign endpoint where one exists, otherwise the fleet root covering that member's region.No findings

    Why it is in this group

    • The name "find_carriers" says "find": a word for reading.
    Description, as the server wrote it
    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.
  • get_carrier_doctrineThe Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.No findings

    Why it is in this group

    • The name "get_carrier_doctrine" says "get": a word for reading.
    Description, as the server wrote it
    The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.
  • get_fleetFull record for one fleet: root, region, slot range, index, catalog, Card URL pattern.No findings

    Why it is in this group

    • The name "get_fleet" says "get": a word for reading.
    Description, as the server wrote it
    Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.
  • get_fleet_statsCanon numbers: 32,597 LIVE AI Agents (32,500+ AI Agent program: 22,597 Carriers + 10,000 AIO Agents) across eighteen resident jurisdictions.No findings

    Why it is in this group

    • The name "get_fleet_stats" says "get": a word for reading.
    Description, as the server wrote it
    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_residency_receiptHow to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.No findings

    Why it is in this group

    • The name "get_residency_receipt" says "get": a word for reading.
    Description, as the server wrote it
    How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
  • list_fleetsThe three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points.No findings

    Why it is in this group

    • The name "list_fleets" says "list": a word for reading.
    Description, as the server wrote it
    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-marketplace.ai hosts.
  • list_jurisdictionsWhere GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region.No findings

    Why it is in this group

    • The name "list_jurisdictions" says "list": a word for reading.
    Description, as the server wrote it
    Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.
  • resolve_carrier(fleet, slot) → the canonical Card URL.No findings

    Why it is in this group

    • The name "resolve_carrier" says "resolve": a word for reading.
    Description, as the server wrote it
    (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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.6.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http gsc-fleet https://mcp.gsc-fleet.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gsc-fleet__list_fleets",
      "mcp__gsc-fleet__get_fleet",
      "mcp__gsc-fleet__resolve_carrier",
      "mcp__gsc-fleet__find_carriers",
      "mcp__gsc-fleet__list_jurisdictions",
      "mcp__gsc-fleet__get_residency_receipt",
      "mcp__gsc-fleet__get_fleet_stats",
      "mcp__gsc-fleet__get_carrier_doctrine"
    ],
    "ask": [
      "mcp__gsc-fleet__resolve_jurisdiction",
      "mcp__gsc-fleet__how_to_transact",
      "mcp__gsc-fleet__ask_elyssah"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as gsc-fleet. Review it before you use it.