fucking with AI on websitesThere is a new toy to play with to break AI scrapers!
You might know of MCP, or "model context protocol". Well, people have now made WebMCP so that you can expose MCP functions directly from your site using just a small library.
Well, I'm thinking that I just put this on my website, but then fill it up with exclusively garbage functions that tell the user their AI is broken, that it's becoming depressed or other fun things that should put them in a frenzy about what's happening to their poor, poor LLM. In addition to that I should make sure there is never actually anything of-use in there either.
fucking with AI on websites@star MCP is basically just a really, really stupid API. it's literally just the website gives a list of functions that have some kind of name and the LLM "calls them" by just deadass typing them out verbatim (iiiii think?)
I could make functions for common things like "summarize blogpost" or something that looks innocent but then give it absolute garbage data
re: fucking with AI on websites@alexia MCP itself is a protocol for the agent and MCP server to communicate
how the agent makes the model actually call the MCPs differs between implementations, but it typically uses the model's tool calling capabilities, which use text with special formatting (which the model is trained to follow; it's usually XML/JSON-like)
so yes, the model calls them by outputting the exact name (i'm not sure how else it could work?) and parameters in a specific structured format
the model is provided with the MCP's parameters and their descriptions in a different, usually structured, format. most of the time, the full info about all "connected" MCPs is always fed into the model (which can use a lot of tokens), but some implementations only give the model what's necessary.
