Five live MCP endpoints on the SK Telecom documentation hubs (ReadMe-provided, tools/list auth-gated); no MCP server for the SK open API gateway itself
SK Telecom does not author or operate an MCP server for its APIs. It does, however, publish every API reference on the ReadMe documentation platform, and each of the five SK open API documentation hubs exposes a live MCP endpoint at /mcp on the SK Telecom-branded hostname. Those endpoints are real — a JSON-RPC POST returns a well-formed JSON-RPC envelope — but tools/list and initialize both answer HTTP 401 {"code":-32001,"message":"Authorization required"}, and the RFC 9728 descriptor names ReadMe's own authorization server (https://dash.readme.com/oidc) as the issuer. The tool set therefore cannot be introspected anonymously, and the tools are documentation-platform tools rather than tools generated per SK Telecom API operation. No MCP server for the SK open API gateway itself (apis.openapi.sk.com) was found on the portal, in the SK Telecom GitHub organisation, or in any public MCP registry.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.