Unverified50% confidenceFactExact time
WebMCP capabilities are still at an early stage of browser-vendor implementation and standardization, and interface naming and enablement methods differ across browsers, which is why Playwright labels it an experimental API.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/17/2026
First Seen
Valid until: 1/15/2027
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 application75% similarUnverifiedWebMCP does not have an independent client and server architecture and operates on the client side (within a specific web application in the browser)72% similarUnverifiedModern browser extensions primarily follow the WebExtensions API standard, which was led by Mozilla, and has been adopted by mainstream browsers including Chrome, Firefox, and Edge.71% similarUnverifiedBrowser MCP typically calls headless browser frameworks such as Playwright or Puppeteer at the underlying level.71% similarUnverifiedOpenCut 的 Web 架构技术底层依赖于 WebAssembly、WebCodecs 和 WebGL 等现代 Web API71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053906API
curl https://kongchang.com/api/v1/knowledge/claims/1053906MCP
get_claim(id=1053906)