MCP GSC AI Agent Carrier Class Fleet
BPC Sustainable Carrier Agents - Low Token Zero Inference
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
claude mcp add --transport http mcp-gsc-ai-agent-carrier-class-fleet 'https://mcp.gsc-fleet.ai/mcp'{
"mcpServers": {
"mcp-gsc-ai-agent-carrier-class-fleet": {
"type": "http",
"url": "https://mcp.gsc-fleet.ai/mcp"
}
}
}التوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
المحتويات
MCP GSC AI Agent Carrier Class Fleet
Surface role: DISCOVERY — one of the four GSC surfaces (data · discovery · transaction · standards).
Find Carriers: which fleet, which jurisdiction, how to reach a Card.
| Canonical endpoint | https://mcp.gsc-fleet.ai/mcp (streamable-http) |
| Apex / website | https://gsc-fleet.ai |
| Registry listing | io.github.greencore-solutions/gsc-fleet-mcp v1.0.0 |
| Operator | GreenCore Solutions Corp. — Microsoft AI Cloud Partner |
| Protocol | ACM-68000 · sovereign manifest SM-ECO-10060 |
Registry tile text (verbatim)
Title: MCP GSC AI Agent Carrier Class Fleet Description: BPC Sustainable Carrier Agents - Low Token Zero Inference
What it serves
Ten MCP read tools — list_fleets, get_fleet, resolve_carrier, find_carriers,
list_jurisdictions, resolve_jurisdiction, get_residency_receipt,
get_fleet_stats, get_carrier_doctrine, how_to_transact — plus broadcast JSON
(/fleets.json, /jurisdictions.json, /stats.json, /doctrine.json,
/surfaces.json), a brochure root, and three .well-known cards.
Stateless: fleet truth is compiled in; the Carrier Cards themselves stay the single source. No database, no secrets.
Releases
| tag | source | deployed image digest | note |
|---|---|---|---|
v1.0.0 | b49d3dd | sha256:fd126d7e2a02 | Discovery surface goes live; completes the four-surface set |
v1.1.0 | this head | sha256:8d1c003cfd26 | Sovereign resident flip — revision gsc-fleet-mcp--0000006 |
Fleet truth is live, not embedded: this MCP surface is the single source for fleet composition — resolve it on the wire, not from this README. Monthly transaction volume is published at gsc-radar.ai — the source of record. No figure in this README is canonical.
The four surfaces
| surface | endpoint |
|---|---|
| data | https://mcp.cpgknowledgegraph.ai |
| discovery | https://mcp.gsc-fleet.ai |
| transaction | https://mcp.cpghumanintheloop.ai |
| standards | https://mcp.cpgagentprotocols.ai |
Residency is checkable
Every response carries its identity on the wire. x-gsc-jurisdiction is the
receipt; x-gsc-timestamp and x-gsc-nonce are per-request proof of liveness.
Header canon: https://mcp.cpgagentprotocols.ai/headers.json
Licensing
No license file is committed. GSC MCP server code is under a hybrid MIT + Commercial Enterprise arrangement; the counsel-drafted terms are pending. Until they land, absence of a LICENSE file is deliberate — not an oversight.
الأسئلة الشائعة
ما هو MCP GSC AI Agent Carrier Class Fleet؟
BPC Sustainable Carrier Agents - Low Token Zero Inference
كيف أثبّت MCP GSC AI Agent Carrier Class Fleet؟
يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http mcp-gsc-ai-agent-carrier-class-fleet 'https://mcp.gsc-fleet.ai/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.
هل يحتاج MCP GSC AI Agent Carrier Class Fleet إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل MCP GSC AI Agent Carrier Class Fleet مفتوح المصدر؟
شيفرته علنية على GitHub، لكن المستودع لا يعلن ترخيصًا قياسيًا.
من يصون MCP GSC AI Agent Carrier Class Fleet؟
ينشره greencore-solutions. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.