MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge)

Independentpositioncore entry

Verified 2026-10-13. Status as of 2026-10-13. All entries.

Seams: S3S4

Status

WebKit position issue #670 closed 2026-06-11 as "position: oppose"; Mozilla #1412 closed 2026-08-05 as "position: neutral". Chrome early preview 2026-02-10; Edge blog of 2026-09-21: implementation "is ready for testing".

Relevance

WebMCP lets a page expose tools to browsing agents; Chrome describes it as "a standard way for exposing structured tools, ensuring AI agents can perform actions on your site with increased speed, reliability, and precision". The WebKit reviewer wrote on 2026-06-03 "WebKit is opposed to this proposal due to the following concerns:", among them that "it has no consent or reversibility model for consequential actions". The Mozilla reviewer proposed a neutral position, writing that "in an adversarial setting there is a risk that sites will provide tools that do not match the experience of a user on the page". PayPal's blog of 2026-09-16 says it is "extending WebMCP support through the PayPal JavaScript SDK" for Store Sync merchants; the agent can search, prepare the cart and initiate checkout, and "The buyer is then handed off to PayPal to sign in, choose or confirm a funding source, review the transaction, and approve payment." PayPal reports, as its own results of a small sandbox benchmark: "Approximately 4.6 times less costly in model-inference usage", "Approximately twice as fast at the median", and "three structured tool calls via WebMCP instead of more than 30 interface-interaction steps" (self-reported).

Shopify's developer changelog of 2026-09-28 says "Browser agents can now read and update Shopify checkouts using WebMCP tools for checkout", with get_checkout, update_checkout and complete_checkout ("Submit checkout after buyer confirmation"); the tools "don't expose a new API or require merchant configuration". The Checkout WebMCP documentation says "Before you call complete_checkout, show the buyer the current order and total, and get their permission to place it.

WBA and ready_for_complete don't grant it."

Committed next

Boundary

The positions concern WebMCP and not MCP: the Mozilla reviewer's text says "There is no MCP here."

Sources

Overlaps

WebMCP (Draft Community Group Report, Web Machine Learning CG), Model Context Protocol (MCP), core specification, W3C Agentic Web Working Group (draft charter)

Neighbours in the map

Neighbours of Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (5)Share a seam (19)W3C Agentic Web Working Group (draft charter) (W3C, core)W3C Agentic Web Working… W3C TPAC 2026 breakouts on agents (Dublin, 2026-10-26/30) (W3C, core)W3C TPAC 2026 breakouts… WebMCP (Draft Community Group Report, Web Machine Learning CG) (W3C, context)WebMCP Model Context Protocol (MCP), core specification (Linux Foundation, context)Model Context Protocol Shopify, MCP surfaces for buyer agents, developers and merchants (Industry, context)Shopify IETF Web Bot Auth (webbotauth WG) (IETF, core)IETF Web Bot Auth S3 IETF agentproto (Agent Communication Protocols WG) (IETF, core)IETF agentproto S3 x402 (Linux Foundation, core)x402 S3 S4 OpenID Foundation AuthZEN Working Group (agent authorization drafts AARP and COAZ) (Independent, context)OpenID Foundation AuthZ… S3 Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… S3 S4 KYAPay (Skyfire) (Industry, core)KYAPay S3 Mastercard Agent Pay (Industry, core)Mastercard Agent Pay S3 Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… S3 S4 Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta (Industry, core)Personal Agent Protocol S3 S4 Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… S3 S4 Visa Trusted Agent Protocol (TAP) (Industry, core)Visa Trusted Agent Prot… S3 IETF vcon (Virtualized Conversations WG) (IETF, core)IETF vcon S4 Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe) (IETF, context)Payment HTTP Authentica… S4 AAIF Agentic Commerce Working Group (AAIF, core)AAIF Agentic Commerce W… S4 EMILIA Protocol (individual drafts and open-source gate) (Independent, context)EMILIA Protocol S4 Agent Payments Protocol (AP2) (Industry, core)Agent Payments Protocol S4 EMV Agentic Payments Framework for Specifications (draft for public feedback) (Industry, core)EMV Agentic Payments Fr… S4 FIDO Alliance agentic authentication and payments work (Industry, context)FIDO Alliance agentic a… S4 Verifiable Intent (Industry, core)Verifiable Intent S4 Browser vendor positions on…

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13: the Chrome and Edge pages and the issues of WebKit and Mozilla, whose quoted sentences (the Chrome description, the Edge sentence "is ready for testing", and the WebKit and Mozilla statements) were found again in the current texts; the state and labels of both issues (closed 2026-06-11 "position: oppose" and closed 2026-08-05 "position: neutral", unchanged).
Not read
Safari or Apple pages outside the issue, Chrome Status, other Mozilla pages, other vendors, implementation documentation.