{
  "ok": true,
  "serverInfo": {
    "name": "metadata-tool-mcp-skills",
    "version": "0.5.3"
  },
  "endpoint": "http://mcporase.ddns.net/mcp",
  "restAdapter": {
    "skills": "http://mcporase.ddns.net/api/skills",
    "skillCallTemplate": "http://mcporase.ddns.net/api/skills/{toolName}",
    "toolCallAliasTemplate": "http://mcporase.ddns.net/api/tools/{toolName}/call",
    "openApi": "http://mcporase.ddns.net/openapi.json",
    "note": "Use the REST adapter from Fusion AI Studio External REST tools when native MCP tools cannot be created."
  },
  "authentication": {
    "type": "none",
    "mode": "none",
    "note": "Authentication is disabled by MCP_AUTH_MODE=none or MCP_AUTH_DISABLED=1.",
    "valueFormats": [],
    "tokenEnv": ""
  },
  "designCompatibility": {
    "transport": [
      "stdio",
      "http-json-rpc"
    ],
    "httpEndpoint": "/mcp",
    "restAdapterEndpoint": "/api/skills/{toolName}",
    "openApiEndpoint": "/openapi.json",
    "healthEndpoint": "/health",
    "manifestEndpoint": "/.well-known/mcp.json",
    "authentication": {
      "type": "none",
      "mode": "none",
      "note": "Authentication is disabled by MCP_AUTH_MODE=none or MCP_AUTH_DISABLED=1."
    },
    "directives": [
      "This server is a public skill registry by default. Set MCP_AUTH_TOKEN or MCP_AUTH_MODE=token to require authentication.",
      "When token mode is enabled, HTTP MCP JSON-RPC requests require either Authorization: Bearer <token> or an API key header containing the token.",
      "Accepted API key headers: x-api-key, api-key, apikey, x-api-token.",
      "OAuth2 client_credentials is available at /oauth/token and returns a Bearer access token.",
      "No deployment token is hardcoded; configure MCP_AUTH_TOKEN and MCP_OAUTH_CLIENT_SECRET per environment when authentication is required.",
      "Credentials for Unity, Infinity, BigQuery, OpenAI and Responsys stay in the client-side Metadata Tool connection resolver, not in this public registry.",
      "Fusion AI Studio can consume tools through the REST adapter endpoints when native MCP tool creation is unavailable.",
      "Tool outputs must not expose credentials, OAuth tokens, passwords, tenant secrets or private keys.",
      "Write tools preserve dry-run and explicit confirmation guardrails.",
      "The same server remains compatible with local stdio MCP clients and OCI-hosted HTTP clients.",
      "Large CSV datasets use the streamed upload API; they are never sent as MCP JSON arguments."
    ]
  }
}