MCP GSC AI Agent Carrier Class Fleet
REMOTE · MCP.GSC-FLEET.AI · SCANNED AUG 3
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 →
Endpoint Security57
- 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 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability46
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 489 tokens (~48/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.gsc-fleet.ai
claude mcp add --transport http greencore-solutions-gsc-fleet-mcp 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": {
"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.
- 3 Aug 26 +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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 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
- 26 Jul 26 56
First indexed and scored.
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 3 Aug 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=mcp.gsc-fleet.ai | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 19 Jul 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 68cbebb82464d75a77b374d88c49448 |
| SANs: mcp.gsc-fleet.ai | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
DNSSEC insecure
Validation of mcp.gsc-fleet.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| gsc-fleet.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
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.
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 ~46
Canon fleet numbers: 10,597 LIVE across nine sovereign jurisdictions, 9.5M agentic inbound signals per month, 1.5M human visits per month.
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 ~47
The three live fleet roots — Global, APAC, LATAM — with regions, slot ranges, and entry points. Headline: 10,597 LIVE across nine sovereign jurisdictions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jurisdictions The sovereign deployment map ~37
Where GSC Carriers are resident — all nine 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.