Unverified50% confidenceFactExact time
WebMCP does not have an independent client and server architecture and operates on the client side (within a specific web application in the browser)
1
Sources
50%
Confidence
Long-term
Relevance
10/5/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedA limitation of WebMCP is that the application must be open in the user's browser for the relevant tools to be available, making it inherently bound to the web application73% similarUnverifiedA cross-environment compatible WebGPU library can run the same WebGPU code in both browser and headless Node.js environments.69% similarUnverifiedJavaScript in the browser cannot create raw TCP/UDP sockets; all network communication must go through high-level APIs such as WebSocket, Fetch, and WebRTC.68% similarUnverifiedWeb Components require no build tools or runtime dependencies and run directly in modern browsers67% similarUnverified浏览器中的 JavaScript 拥有完整的 Web API 生态，而 Node.js 作为服务端运行时，天然不包含任何与 UI 或浏览器窗口相关的接口66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/978468API
curl https://kongchang.com/api/v1/knowledge/claims/978468MCP
get_claim(id=978468)