# MCP GSC AI Agent Carrier Class Fleet (remote · mcp.gsc-fleet.ai)

BPC Sustainable Carrier Agents - Low Token Zero Inference

- Trust score: 61/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.gsc-fleet.ai`: 61/100 (this document), [markdown](https://verifymcp.io/servers/greencore-solutions-gsc-fleet-mcp/mcp.md), [page](https://verifymcp.io/servers/greencore-solutions-gsc-fleet-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.gsc-fleet.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 46/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 489 tokens (~48/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http greencore-solutions-gsc-fleet-mcp https://mcp.gsc-fleet.ai/mcp
```

### Codex

```toml
[mcp_servers.greencore-solutions-gsc-fleet-mcp]
url = "https://mcp.gsc-fleet.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "greencore-solutions-gsc-fleet-mcp": {
      "type": "remote",
      "url": "https://mcp.gsc-fleet.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add greencore-solutions-gsc-fleet-mcp --url https://mcp.gsc-fleet.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  greencore-solutions-gsc-fleet-mcp:
    url: "https://mcp.gsc-fleet.ai/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 60, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (10)

### `list_fleets` (~47 tokens)

List the GSC Carrier Fleets

The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points. Headline: 10,597 LIVE across nine sovereign jurisdictions.

### `get_fleet` (~39 tokens)

Get one fleet

Full record for one fleet: root, region, slot range, index, catalog, Card URL pattern.

Input parameters:

- `fleet` (string, required): Fleet key

### `resolve_carrier` (~74 tokens)

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.

Input parameters:

- `fleet` (string, required): Fleet key
- `slot` (string, required): Four-digit slot number, e.g. 0001

### `find_carriers` (~102 tokens)

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.

Input parameters:

- `category` (string): Optional SPARKS category (answers as the sovereign set ships)
- `node` (string, required): SM-ECO-10060 member code, e.g. UK, KR, BR

### `list_jurisdictions` (~37 tokens)

The sovereign deployment map

Where GSC Carriers are resident — all nine jurisdictions, each with its serving Azure region. Residency is the checkable claim.

### `resolve_jurisdiction` (~37 tokens)

Resolve one jurisdiction

Member code → residency status, serving endpoint, and Azure region.

Input parameters:

- `code` (string, required): Member code, e.g. CH

### `get_residency_receipt` (~35 tokens)

The 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` (~46 tokens)

Fleet statistics

Canon fleet numbers: 10,597 LIVE across nine sovereign jurisdictions, 9.5M agentic inbound signals per month, 1.5M human visits per month.

### `get_carrier_doctrine` (~39 tokens)

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.

### `how_to_transact` (~33 tokens)

The four GSC surfaces

Which GSC surface an agent uses for data, discovery, transaction, and standards — with the endpoint for each.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/greencore-solutions-gsc-fleet-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 56

## Links

- Remote endpoint: https://mcp.gsc-fleet.ai/mcp
- Repository: https://github.com/greencore-solutions/gsc-fleet-mcp
- Website: https://gsc-fleet.ai/
- Changelog RSS feed: https://verifymcp.io/servers/greencore-solutions-gsc-fleet-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/greencore-solutions-gsc-fleet-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/greencore-solutions-gsc-fleet-mcp/mcp