MCP GSC AI Agent Carrier Class Fleet
REMOTE · MCP.GSC-FLEET.AI · SCANNED SEP 20
BPC Sustainable Carrier Agents - Low Token Zero Inference
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 767 tokens (~69/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MCP GSC AI Agent Carrier Class Fleet server?
MCP GSC AI Agent Carrier Class Fleet is a hosted endpoint at https://mcp.gsc-fleet.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.gsc-fleet.ai
claude mcp add --transport http greencore-solutions-gsc-fleet-mcp 'https://mcp.gsc-fleet.ai/mcp'
{
"mcpServers": {
"greencore-solutions-gsc-fleet-mcp": {
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
} {
"servers": {
"greencore-solutions-gsc-fleet-mcp": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
} [mcp_servers.greencore-solutions-gsc-fleet-mcp] url = "https://mcp.gsc-fleet.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"greencore-solutions-gsc-fleet-mcp": {
"type": "remote",
"url": "https://mcp.gsc-fleet.ai/mcp",
"enabled": true
}
}
} openclaw mcp add greencore-solutions-gsc-fleet-mcp --url 'https://mcp.gsc-fleet.ai/mcp' --transport streamable-http
mcp_servers:
greencore-solutions-gsc-fleet-mcp:
url: "https://mcp.gsc-fleet.ai/mcp" {
"McpServers": {
"greencore-solutions-gsc-fleet-mcp": {
"Transport": "http",
"Url": "https://mcp.gsc-fleet.ai/mcp"
}
}
} assistant mcp add greencore-solutions-gsc-fleet-mcp -t streamable-http -u 'https://mcp.gsc-fleet.ai/mcp'
{
"mcpServers": {
"greencore-solutions-gsc-fleet-mcp": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 0
- Server version: 1.6.0 → 1.6.1 functional
- 11 Sept 26 +1
- Schema quality: 56 → 69 ▼ functional
- Server version: 1.5.1 → 1.6.0 functional
- New tool “ask_elyssah” functional
- 1 Sept 26 +2
- HSTS header: fail → pass ▲ security
- 27 Aug 26 −1
- Tool “get_fleet_stats” rewrote its description, which is the text the model reads security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +2
- DNSSEC: fail → pass ▲ security
- Stability: 0.97 → pass security
- Server version: 1.4.0 → 1.5.1 functional
- 23 Aug 26 0
- Tool “get_fleet_stats” rewrote its description, which is the text the model reads security
- Tool “list_fleets” rewrote its description, which is the text the model reads security
- Tool “list_jurisdictions” rewrote its description, which is the text the model reads security
- Schema quality: 48 → 56 ▼ functional
- Server version: 1.0.0 → 1.4.0 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.gsc-fleet.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gsc-fleet.ai | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 71694bbfebee3ada13bb3e4346bea242 |
| SANs: gsc-fleet.ai, *.gsc-fleet.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.gsc-fleet.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| gsc-fleet.ai. | present | 2371 | 13 | Verified |
| mcp.gsc-fleet.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.gsc-fleet.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.gsc-fleet.ai/mcp | HTTPS enforced | 301 | https://mcp.gsc-fleet.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_elyssah Ask elyssah — GSC's AI assistant ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prev | string | – | id of the last answer shown (one-turn context, ranking only) |
| q | string | yes | The question, plain words, up to 300 characters |
No output schema declared.
No examples provided.
find_carriers Find Carriers for a jurisdiction ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional SPARKS category (answers as the sovereign set ships) |
| node | string | yes | SM-ECO-10060 member code, e.g. UK, KR, BR |
No output schema declared.
No examples provided.
get_carrier_doctrine What a Carrier is ~39
The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fleet Get one fleet ~39
Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| fleet | string | yes | Fleet key |
No output schema declared.
No examples provided.
get_fleet_stats Fleet statistics ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_residency_receipt The residency receipt ~35
How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to_transact The four GSC surfaces ~33
Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_fleets List the GSC Carrier Fleets ~102
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jurisdictions The sovereign deployment map ~36
Where GSC Carriers are resident — eighteen jurisdictions, each with its serving Azure region. Residency is the checkable claim.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_carrier Resolve a Carrier Card URL ~74
(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.
| Name | Type | Req | Description |
|---|---|---|---|
| fleet | string | yes | Fleet key |
| slot | string | yes | Four-digit slot number, e.g. 0001 |
No output schema declared.
No examples provided.
resolve_jurisdiction Resolve one jurisdiction ~37
Member code → residency status, serving endpoint, and Azure region.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Member code, e.g. CH |
No output schema declared.
No examples provided.
What is the MCP GSC AI Agent Carrier Class Fleet server?
MCP GSC AI Agent Carrier Class Fleet is listed in the public MCP registry as io.github.greencore-solutions/gsc-fleet-mcp. BPC Sustainable Carrier Agents - Low Token Zero Inference. This page covers its hosted endpoint (https://mcp.gsc-fleet.ai/mcp).
Is the MCP GSC AI Agent Carrier Class Fleet server safe to use?
MCP GSC AI Agent Carrier Class Fleet scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP GSC AI Agent Carrier Class Fleet server expose?
MCP GSC AI Agent Carrier Class Fleet exposes 11 tools: list_fleets, get_fleet, resolve_carrier, find_carriers, list_jurisdictions, and 6 more. Their descriptions and schemas cost roughly 767 tokens of context every time the server is loaded.
Does the MCP GSC AI Agent Carrier Class Fleet server require authentication?
No. We connected to MCP GSC AI Agent Carrier Class Fleet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP GSC AI Agent Carrier Class Fleet server still maintained?
MCP GSC AI Agent Carrier Class Fleet is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.