Expired70% confidenceFactExact time
WebMCP 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.
4
Sources
70%
Confidence
Medium-term (~90 days)
Relevance
7/2/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 9/30/2026(expired)
Sources
Related Claims
UnverifiedWebMCP provides two ways for web pages to expose tool capabilities: a declarative API and an imperative API.84% similarVerifiedWebMCP's imperative API registers custom tools via the registerTool function, supporting parameters such as name, description, schema, and execute.79% similarUnverifiedThe declarative API only requires adding a tool name attribute to a standard HTML form, allowing the form to become an AI-callable tool without refactoring code.79% similarUnverifiedThe input schema of WebMCP's imperative API defines parameters in JSON Schema format.77% similarVerifiedWebMCP uses JSON Schema to describe tool parameter structures, employing the same mechanism as OpenAI's Function Calling and Anthropic's Tool Use technologies.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/47868API
curl https://kongchang.com/api/v1/knowledge/claims/47868MCP
get_claim(id=47868)