Conversation
Learn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three technical notes submitted for review before wider distribution. We want to ensure factual accuracy and welcome corrections, amendments, or discussion from spec editors and CG participants.
webmcp-technical-note-1.md -- How a Browser Hack Became a Proposed Web Standard
Reconstructs the WebMCP chronology from Alex Nahas's MCP-B through the Google-Microsoft joint proposal to the Chrome 146 early preview. Documents sources, timelines, and raises process questions about the relationship between implementation and community group deliberation.
webmcp-technical-note-2.md -- What to Test, What to Watch, What to Tell the Standards Body
Practical guide for evaluating the Chrome 146 early preview. Covers use cases, benefits, seven identified risks (prompt injection, consent model gaps, cross-site tool chaining, and others), eight concrete testing areas, and guidance on communicating findings to the CG.
webmcp-technical-note-3.md -- WebMCP Is Not an MCP Server
Addresses the README's framing that WebMCP pages "can be thought of as MCP servers." Documents five architectural dimensions where this analogy breaks down (transport, execution context, authentication, trust direction, operational mode) and explains why the distinction matters for security review and standards evaluation. Includes a suggested clarification for the specification text.
Request: Please review for factual accuracy. Merge these notes or respond with amendment requests. we want the community group's input before wider distribution. Thank you!