MCP GSC AI Agent Carrier Class Fleet
Server Details
BPC Sustainable Carrier Agents - Low Token Zero Inference
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- greencore-solutions/gsc-fleet-mcp
- GitHub Stars
- 0
- Server Listing
- MCP GSC AI Agent Carrier Class Fleet
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes, but find_carriers and resolve_jurisdiction both accept a member code and return serving endpoints, creating a potential selection ambiguity. Additionally, ask_elyssah can answer questions about record numbers that overlap with get_fleet_stats, though the descriptions help clarify boundaries.
The vast majority follow a consistent verb_noun pattern (ask_, find_, get_, list_, resolve_), with clear and predictable naming. The outlier is how_to_transact, which breaks the pattern and reads more like a help topic than an action, slightly reducing overall consistency.
Eleven tools is well within the ideal range for a domain-specific server. Each tool addresses a distinct facet of the GSC Carrier fleet surface—querying, resolving, listing, verifying, and transacting—without feeling bloated or redundant. The count is well-scoped for the server's stated purpose.
The surface covers the full lifecycle of interacting with GSC's fleet information: discovery (list_fleets, list_jurisdictions), lookup (get_fleet, get_fleet_stats), resolution (resolve_carrier, resolve_jurisdiction, find_carriers), verification (get_residency_receipt), guidance (get_carrier_doctrine, how_to_transact), and conversational access (ask_elyssah). No significant gaps are apparent for an informational/query-oriented server.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
BPC Agentic Commerce Signals
Navigator for BPC Agentic Procurement
LLM Orchestration Agent 2
CPG sourcing for AI Agents with x402: BPC brands, agent IM, Trading Desk. GreenCore Solutions Corp.
Related MCP Servers
- AlicenseAqualityBmaintenanceNeuro-symbolic deterministic context pruning middleware. Reduces tokens by 60%, drops local CPU TTFT by 62%, and prevents IP leakage via formal SPARQL contracts.23MIT
- AlicenseNot gradedqualityBmaintenanceThe Zero-Trust Security & Privacy Gateway for AI Agents2Apache 2.0
- AlicenseAqualityBmaintenanceIn-memory polyglot AST pruning and deterministic context firewall for coding agents, eliminating up to 72.4% token bloat with zero telemetry egress.65166 PyPI8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to cut token usage by locally pruning, encoding, and summarizing MCP tool responses, with lossless recovery of original data when needed.47 npm1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.