Expired60% confidenceFactExact time
WebMCP provides two ways for web pages to expose tool capabilities: a declarative API and an imperative API.
2
Sources
60%
Confidence
Medium-term (~90 days)
Relevance
7/22/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 10/20/2026(expired)
Sources
Related Claims
VerifiedWebMCP provides two implementation approaches—a declarative API and an imperative API—where the declarative API is implemented by adding tool-name and tool-description attributes to HTML form elements.84% similarUnverifiedBy having web pages proactively define tool boundaries through WebMCP, AI can only call the functional interfaces explicitly authorized by the website rather than arbitrarily operating any page element, providing structural safeguards for security.76% similarVerifiedWebMCP's imperative API registers custom tools via the registerTool function, supporting parameters such as name, description, schema, and execute.76% similarUnverifiedWebMCP (Web Model Context Protocol) is a next-generation Web standard proposed to address the pain points of AI agents operating web pages.75% similarUnverified现代浏览器扩展拦截网络流量依赖WebRequest API（Chrome/Edge）或declarativeNetRequest API体系75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/585098API
curl https://kongchang.com/api/v1/knowledge/claims/585098MCP
get_claim(id=585098)