> If I asked you to build a table and gave you a Home Depot you probably would have a harder time than if I gave you a saw, a hammer and some nails. I doubt that, first and not least because Home Depot stocks lumber.
Fixed. Nice catch
MCP-B: A Protocol for AI Browser Automation
131–140 of 200 posts
Re: MCP-B: A Protocol for AI Browser Automation
#132> If I asked you to build a table and gave you a Home Depot you probably would have a harder time than if I gave you a saw, a hammer and some nails. I doubt that, first and not least because Home Depot stocks lumber.
Re: MCP-B: A Protocol for AI Browser Automation
#133I’ve haven’t used any MCP so far but as a disabled person I see use cases in accessibility for MCPs doing browser/smartphone automation. But any accessibility tool will be exploited by nefarious actors so I wonder how many main stream websites/apps would implement these MCP. Has anyone tried any MCP for improving accessibility?
> But any accessibility tool will be exploited by nefarious actors so I wonder how many main stream websites/apps would implement these MCP. How so?
So people like ticket sales sites, eBay etc. It will make it easier for those sites to have all the tickets purchased or for auctions to be sniped etc.
FWIU, these sort of sites actually (currently at least) put on measures to try and stop bots using them for these reasons.
Re: MCP-B: A Protocol for AI Browser Automation
#134Prediction: this will go the same way as RSS. Companies don't like you to be in control of how you use their data.
Indeed. Though I guess a better example would be: it'll go the same way as REST APIs (which happen to be fundamentally the same thing as MCP anyway). Remember the time when REST was the new hot thing, everyone started doing API-first design, and people thought it'll empower people by letting programs navigate services for them programmatically? Remember when "mashups" were the future? It all died before it could come…
Re: MCP-B: A Protocol for AI Browser Automation
#135Earlier quoted context omitted.
Claude's contributions graph is interesting. What is going on here? Does Claude Code commit as itself sometimes, but extremely rarely? I don't understand. https://github.com/claude
If you ask it to commit it'll sign itself as the author.
Re: MCP-B: A Protocol for AI Browser Automation
#136Earlier quoted context omitted.
> But any accessibility tool will be exploited by nefarious actors so I wonder how many main stream websites/apps would implement these MCP. How so?
Anything that makes it easier to automate will make bad actors more efficient. So people like ticket sales sites, eBay etc. It will make it easier for those sites to have all the tickets purchased or for auctions to be sniped etc. FWIU, these sort of sites actually (currently at least) put on measures to try and stop bots using them for these reasons.
“Use it, but not like that” is not a legitimate position to take.
Re: MCP-B: A Protocol for AI Browser Automation
#137Earlier quoted context omitted.
Home Depot also sells tables.
Haha, that’s pretty close to any software I’ve ever written. Suck in a ton of open source dependencies, write comparatively little, and say “look what I made!” Buying a table, adorning it with vase of fake flowers, and claiming to be a Senior Woodworking Engineer sounds about right. I’ll be a Principal after buying a new bed frame & putting a mattress on it.
It’s manufacturing all the way down.
Don’t sell yourself short.
Re: MCP-B: A Protocol for AI Browser Automation
#138Earlier quoted context omitted.
Pretty much every revolution in how we do things originates from the supplier. When websites became a thing the burden was on businesses to build them. Same with REST APIs. Same with mobile apps. As soon as there’s a competitive advantage to having the new thing, companies will respond if consumers demand it.
Am I going to start to choose products based on their compatibility with WebMCP?
Re: MCP-B: A Protocol for AI Browser Automation
#139Re: MCP-B: A Protocol for AI Browser Automation
#140From the blog post: "The Auth problem At this point, the auth issues with MCP are well known. OAuth2.1 is great, but we are basically trying to re-invent auth for agents that act on behalf of the user. This is a good long term goal, but we are quickly realizing that LLM sessions with no distinguishable credentials of their own are difficult to authorize and will require a complete re-imagining of our authorization sy…
Not sure I understand. The model has no more access than the user does. proper security implementation still lies with the website owner