MCP GSC AI Agent Carrier Class Fleet
io.github.greencore-solutions/gsc-fleet-mcpgreencore-solutionsstreamable-httpv1.6.1Scanned
BPC Sustainable Carrier Agents - Low Token Zero Inference
11 tools: 3 change things and 8 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the MCP GSC AI Agent Carrier Class Fleet can do
The MCP GSC AI Agent Carrier Class Fleet is published by the GitHub account greencore-solutions. It has 11 tools. It can create or change data (3 tools: resolve_jurisdiction, how_to_transact and ask_elyssah), but cannot delete data. 8 tools only read.
2 tools bring in text other people can write (get_fleet and resolve_carrier).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 5, 2026, version 1.6.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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 8Show 8 read-only tools
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.Reads text others writeNo findings
Why it is in this group
- The name "get_fleet" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
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.Reads text others writeNo findings
Why it is in this group
- The name "resolve_carrier" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Nov 13, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://mcp.gsc-fleet.ai/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://login.microsoftonline.com/54939635-2f2e-465a-8526-a907cb3c8ebd/v2.0 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 4 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://mcp.gsc-fleet.ai/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://login.microsoftonline.com/54939635-2f2e-465a-8526-a907cb3c8ebd/v2.0 to none
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/mcpclaude mcp add --transport http gsc-fleet https://mcp.gsc-fleet.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gsc-fleet. Review it before you use it.
Capability tags behind 2 rules
- mcp__gsc-fleet__get_fleet untrusted-input
- mcp__gsc-fleet__resolve_carrier untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.greencore-solutions/gsc-fleet-mcp/verify?hash=26a48c718a7a95e99f1dbce175180e2f2c7b9bf4cd6b6358405a452cc405dfae" | jq -e '.changed == false'Pinned hash 26a48c718a7a, from Nov 5, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.greencore-solutions/gsc-fleet-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.greencore-solutions/gsc-fleet-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.
MCP GSC AI Agent Carrier Class Fleet: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MCP GSC AI Agent Carrier Class Fleet safe?
- No scan can promise that. What its definitions show: 11 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MCP GSC AI Agent Carrier Class Fleet delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MCP GSC AI Agent Carrier Class Fleet do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MCP GSC AI Agent Carrier Class Fleet have?
- 11 tools: 3 write, 8 read. resolve_jurisdiction, how_to_transact, ask_elyssah, list_fleets, get_fleet, resolve_carrier, find_carriers, list_jurisdictions and 3 more.
Does the MCP GSC AI Agent Carrier Class Fleet need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the MCP GSC AI Agent Carrier Class Fleet send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MCP GSC AI Agent Carrier Class Fleet changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.