MCPサーバー

MCP GSC AI Agent Carrier Class Fleet

io.github.greencore-solutions/gsc-fleet-mcp

このMCPでできること

Provides discovery and metadata tools for GSC carrier agents, fleets, jurisdictions, residency, and agent-to-agent transaction surfaces.

ask_elyssah
Ask elyssah — GSC's AI assistant
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.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['q'], 'properties': {'q': {'type': 'string', 'maxLength': 300, 'minLength': 1, 'description': 'The question, plain words, up to 300 characters'}, 'prev': {'type': 'string', 'maxLength': 40, 'description': 'id of the last answer shown (one-turn context, ranking only)'}}}
find_carriers
Find Carriers for a jurisdiction
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.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['node'], 'properties': {'node': {'type': 'string', 'maxLength': 4, 'description': 'SM-ECO-10060 member code, e.g. UK, KR, BR'}, 'category': {'type': 'string', 'maxLength': 64, 'description': 'Optional SPARKS category (answers as the sovereign set ships)'}}}
get_carrier_doctrine
What a Carrier is
The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
get_fleet
Get one fleet
Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fleet'], 'properties': {'fleet': {'enum': ['global', 'apac', 'latam'], 'type': 'string', 'description': 'Fleet key'}}}
get_fleet_stats
Fleet statistics
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.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
get_residency_receipt
The residency receipt
How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
how_to_transact
The four GSC surfaces
Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
list_fleets
List the GSC Carrier 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-marketplace.ai hosts.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
list_jurisdictions
The sovereign deployment map
Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
resolve_carrier
Resolve a Carrier Card URL
(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.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['fleet', 'slot'], 'properties': {'slot': {'type': 'string', 'pattern': '^\\d{4}$', 'description': 'Four-digit slot number, e.g. 0001'}, 'fleet': {'enum': ['global', 'apac', 'latam'], 'type': 'string', 'description': 'Fleet key'}}}
resolve_jurisdiction
Resolve one jurisdiction
Member code → residency status, serving endpoint, and Azure region.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['code'], 'properties': {'code': {'type': 'string', 'maxLength': 4, 'description': 'Member code, e.g. CH'}}}
変更
ask_elyssah
2026年9月19日2:42
変更
resolve_jurisdiction
2026年9月19日2:42
変更
find_carriers
2026年9月19日2:42
変更
resolve_carrier
2026年9月19日2:42
変更
get_fleet
2026年9月19日2:42
追加
ask_elyssah
2026年9月17日12:42
追加
how_to_transact
2026年9月17日12:42
追加
get_carrier_doctrine
2026年9月17日12:42
追加
get_fleet_stats
2026年9月17日12:42
追加
get_residency_receipt
2026年9月17日12:42
追加
resolve_jurisdiction
2026年9月17日12:42
追加
list_jurisdictions
2026年9月17日12:42
追加
find_carriers
2026年9月17日12:42
追加
resolve_carrier
2026年9月17日12:42
追加
get_fleet
2026年9月17日12:42
追加
list_fleets
2026年9月17日12:42