MCP GSC AI Agent Carrier Class Fleet

BPC Sustainable Carrier Agents - Low Token Zero Inference

사용해야 할까요

품질 및 안전성

B
설명 품질
90%
스키마 완전성
62%
이름 품질
93%
오염 위험
80%
권한 일치
100%
프로토콜 준수
100%

발견 사항 (5)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainask_elyssah에서
  • LOWTool 'list_fleets' description lacks action verblist_fleets에서
  • LOWTool 'resolve_jurisdiction' description lacks action verbresolve_jurisdiction에서
  • LOWTool 'how_to_transact' description lacks action verbhow_to_transact에서

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~1,198토큰 (도구 정의)
~499 B일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 0.94%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

{
  "mcpServers": {
    "gsc-fleet-mcp": {
      "url": "https://mcp.gsc-fleet.ai/mcp"
    }
  }
}

원격 엔드포인트

https://mcp.gsc-fleet.ai/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (11)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢list_fleets

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.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_fleet(fleet)

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

입력 스키마

{
  "type": "object",
  "properties": {
    "fleet": {
      "type": "string",
      "enum": [
        "global",
        "apac",
        "latam"
      ],
      "description": "Fleet key"
    }
  },
  "required": [
    "fleet"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢resolve_carrier(fleet, slot)

(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.

입력 스키마

{
  "type": "object",
  "properties": {
    "fleet": {
      "type": "string",
      "enum": [
        "global",
        "apac",
        "latam"
      ],
      "description": "Fleet key"
    },
    "slot": {
      "type": "string",
      "pattern": "^\\d{4}$",
      "description": "Four-digit slot number, e.g. 0001"
    }
  },
  "required": [
    "fleet",
    "slot"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡find_carriers(node, category)

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "node": {
      "type": "string",
      "maxLength": 4,
      "description": "SM-ECO-10060 member code, e.g. UK, KR, BR"
    },
    "category": {
      "type": "string",
      "maxLength": 64,
      "description": "Optional SPARKS category (answers as the sovereign set ships)"
    }
  },
  "required": [
    "node"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_jurisdictions

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

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪resolve_jurisdiction(code)

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

입력 스키마

{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "maxLength": 4,
      "description": "Member code, e.g. CH"
    }
  },
  "required": [
    "code"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_residency_receipt

How to verify a GSC surface's residency claim on the wire — which headers to read and what they prove.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_fleet_stats

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.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_carrier_doctrine

The Carrier AI Agent class and the sell-side positioning — prefabricated, static, zero inference; buyer-side compute stays the buyer's.

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪how_to_transact

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

입력 스키마

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪ask_elyssah(q, prev)

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "The question, plain words, up to 300 characters"
    },
    "prev": {
      "type": "string",
      "maxLength": 40,
      "description": "id of the last answer shown (one-turn context, ranking only)"
    }
  },
  "required": [
    "q"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 11개
검증됨버전이 기록되지 않음도구 11개