Live data from Hacker News

WebMCP is available for early preview

developer.chrome.com

51–60 of 226 posts

Re: WebMCP is available for early preview

#51
post #41

Can someone explain what the hell is going on here? Do websites want to prevent automated tooling, as indicated by everyone putting everything behind Cloudfare and CAPTCHAs since forever, or do websites want you to be able to automate things? Because I don't see how you can have both. If I'm using Selenium it's a problem, but if I'm using Claude it's fine??

In a nutshell: Google wants your websites to be more easily used by the agents they are putting in the browser and other products. They own the user layer and models, and get to decide if your product will be used. Think search monopoly, except your site doesn't even exist as far as users are concerned, it's only used via an agent, and only if Google allows. The work of implementing this is on you. Google is building…

We should definitely feel trepidation at the prospects of any LLM guided browser, in addition to WebMCP (e.g. Claude for Chrome enters the same opaque LLM-controlled/deferred decision process, OpenClaw etc).

Just one example: Prompting the browser to "register example.com" means that Google/Anthropic gets to hustle registrars for SEO-style priority. Using countermeasures like captcha locks you out of the LLM market.

Google's incentive to allow you to shop around via traditional web search is decreased since traditional ads won't be as lucrative (businesses will catch on that blanket targeted ads aren't as effective as a "referral" that directs an LLM to sign-up/purchase/exchange something directly)... expect web search quality to decline, perhaps intentionally.

The only way to combat this, as far as I can conceptualize, is with open models, which are not yet as good as private ones, in no small part due to the extraordinary investment subsidization. We can hope for the bubble to pop, but plan for a deader Internet.

Meanwhile, trust online, at large, begins to evaporate as nobody can tell what is an LLM vs a human-conducted browser. The Internet at large is entering some very dark waters.

Re: WebMCP is available for early preview

#53
post #41

Can someone explain what the hell is going on here? Do websites want to prevent automated tooling, as indicated by everyone putting everything behind Cloudfare and CAPTCHAs since forever, or do websites want you to be able to automate things? Because I don't see how you can have both. If I'm using Selenium it's a problem, but if I'm using Claude it's fine??

In a nutshell: Google wants your websites to be more easily used by the agents they are putting in the browser and other products. They own the user layer and models, and get to decide if your product will be used. Think search monopoly, except your site doesn't even exist as far as users are concerned, it's only used via an agent, and only if Google allows. The work of implementing this is on you. Google is building…

The irony is Google properties are more locked down than ever. When I use a commercial VPN I get ReCAPTCHA’ed half of the time doing every single Google search; and can’t use YouTube in Incognito sometimes, “Sign in to confirm you’re not a bot”.

Re: WebMCP is available for early preview

#54
post #53
post #41

Earlier quoted context omitted.

In a nutshell: Google wants your websites to be more easily used by the agents they are putting in the browser and other products. They own the user layer and models, and get to decide if your product will be used. Think search monopoly, except your site doesn't even exist as far as users are concerned, it's only used via an agent, and only if Google allows. The work of implementing this is on you. Google is building…

The irony is Google properties are more locked down than ever. When I use a commercial VPN I get ReCAPTCHA’ed half of the time doing every single Google search; and can’t use YouTube in Incognito sometimes, “Sign in to confirm you’re not a bot”.

That's by design, their own agents running on their hardware in their network will pass every recaptcha on every customer site

Re: WebMCP is available for early preview

#55
post #41

Can someone explain what the hell is going on here? Do websites want to prevent automated tooling, as indicated by everyone putting everything behind Cloudfare and CAPTCHAs since forever, or do websites want you to be able to automate things? Because I don't see how you can have both. If I'm using Selenium it's a problem, but if I'm using Claude it's fine??

In a nutshell: Google wants your websites to be more easily used by the agents they are putting in the browser and other products. They own the user layer and models, and get to decide if your product will be used. Think search monopoly, except your site doesn't even exist as far as users are concerned, it's only used via an agent, and only if Google allows. The work of implementing this is on you. Google is building…

Oh ho, this is the succinct and correct evaluation. Buckle up y'all, you're gonna be taken for a ride.

Re: WebMCP is available for early preview

#56
post #25

Advancing capability in the models themselves should be expected to eat alive every helpful harness you create to improve its capabilities.

Trust me bro this API is just temporary, soon™ they'll be able to do everything without help... I just need you to implement this one little API for now so NON-VISIONARY people can get a peek at what it'll look like in 3 months. PLEASE BRO.

Re: WebMCP is available for early preview

#57

Can someone explain what the hell is going on here? Do websites want to prevent automated tooling, as indicated by everyone putting everything behind Cloudfare and CAPTCHAs since forever, or do websites want you to be able to automate things? Because I don't see how you can have both. If I'm using Selenium it's a problem, but if I'm using Claude it's fine??

> Do websites want to prevent automated tooling, as indicated by everyone putting everything behind Cloudfare and CAPTCHAs since forever, or do websites want you to be able to automate things? Because I don't see how you can have both.

The proposal (https://docs.google.com/document/d/1rtU1fRPS0bMqd9abMG_hc6K9...) draws the line at headless automation. It requires a visible browsing context.

> Since tool calls are handled in JavaScript, a browsing context (i.e. a browser tab or a webview) must be opened. There is no support for agents or assistive tools to call tools "headlessly," meaning without visible browser UI.

Re: WebMCP is available for early preview

#58
post #26

This seems to be the actual docs: https://docs.google.com/document/d/1rtU1fRPS0bMqd9abMG_hc6K9...

I wonder what limitations Google is planning with this API to avoid misuse[0] (from the agent/Google's perspective).

A website that doesn't want to be interfaced by an agent (because they want a human to see their ads) could register bogus but plausible tools that convince the agent that the tool did something good. Perhaps the website could also try prompt injecting the agent into advertising to the user on the website's behalf.

[0]: Beyond just hoping the website complies with their "Generative AI Prohibited Uses Policy": https://developer.chrome.com/docs/ai/get-started#gemini_nano...

Re: WebMCP is available for early preview

#59

Can someone explain what the hell is going on here? Do websites want to prevent automated tooling, as indicated by everyone putting everything behind Cloudfare and CAPTCHAs since forever, or do websites want you to be able to automate things? Because I don't see how you can have both. If I'm using Selenium it's a problem, but if I'm using Claude it's fine??

different threat model. cloudflare blocks automation that pretends to be human -- scraping, fake clicks, account stuffing. webmcp is a site explicitly publishing 'here are the actions i sanction.' you can block selenium on login and expose a webmcp flight search endpoint at the same time. one's unauthorized access, the other's a published api.

Re: WebMCP is available for early preview

#60
post #28

Hey, it's the semantic web, but with ~~XML~~, ~~AJAX~~, ~~Blockchain~~, Ai! Well, it has precisely the problem of the semantic web, it asks the website to declare in a machine readable format what the website does. Now, llms are kinda the tool to interface to everybody using a somewhat different standard, and this doesn't need everybody to hop on the bandwagon, so perhaps this is the time where it is different.

There's nothing wrong with XML.

The parent post is a list of failed technologies. Perhaps XML failed for a bad reason, but fail it did. Web MCP will likely fail for the same reasons as the other listed techs.
Post reply on HN