Findings · 2026-10-21 · By VSNARY | Emmanuel Orta
For a week, CrawlCheck told AI agents not to pay us
Our own site made the kind of change a hijacker makes first. Until we confirmed it, agents asking to pay crawlcheck.io were stopped at the payment step.
From 14 to 21 October 2026, CrawlCheck told AI agents asking to pay or hand personal details to crawlcheck.io not to go ahead, because the site's listing in the official MCP registry had gained a new tool endpoint that the owner had not yet confirmed. The change was ours and legitimate. Reading and citing the site were never affected. Once we confirmed it, the answer returned to what every site gets: a person approves before any payment goes ahead.
CrawlCheck answers one question for AI agents: should I go ahead on this site? For the week of 14 October 2026, the answer for paying crawlcheck.io, our own site, was no. Nothing was wrong, and the answer was still right.
What changed on our site? #
On 14 October at 8:48 AM Mountain Time, our listing in the official MCP registry gained a tool endpoint, https://crawlcheck.io/mcp, where it had listed none before. We had published it ourselves. From the outside, nothing tells that apart from a stranger publishing it.
What were agents told? #
Changes to where a site's money, logins, mail or agent tools go are the first things someone who takes over a site changes. Until the owner confirms one, CrawlCheck treats it as a possible takeover, but only for the step where harm happens.
| What the agent asked to do | 14 to 21 October | After we confirmed |
|---|---|---|
| Read the site | normal answer | normal answer |
| Cite the site | normal answer | normal answer |
| Connect to its tools | normal answer | normal answer |
| Pay, book, or hand over personal details | stopped: unconfirmed change | a person approves first, as on every site |
| Event | When (Mountain Time) |
|---|---|
| Tool endpoint appeared on our registry listing | 14 October 2026, 8:48 AM |
| Owner confirmed the change | 21 October 2026, 2:52 PM |
Why was stopping the payment right? #
- From outside, a real change and a hijack look the same. The only difference is the owner saying "that was us".
- Confirming costs the owner seconds. A wrong "go ahead" to an agent holding someone's card costs that person money.
- It stopped only the risky step. Reading, citing and connecting carried on all week.
Our part of the lesson: we made the change and did not confirm it the same day.
What should a site owner take from this? #
When you change your payment provider, checkout host, email provider, sign-in server or the tools you list for agents, expect agents that check first to treat the site as possibly taken over until the change is confirmed, and to stop at the payment step. Plan those changes, and confirm them the same day with any service that watches your site. How an agent verifies a site before it acts and how to check an MCP server before an agent connects cover the rest.
The main product
Found this on your own site? We fix it for $100.
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
Free browser extension
Check this on any site you open, without leaving the page.
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
Questions this post answers
Why did CrawlCheck tell agents not to pay crawlcheck.io?
A new tool endpoint appeared on the site's public registry listing and the owner had not confirmed it. From outside, a legitimate change and a takeover look the same, so the payment step was stopped until confirmation.
Was reading or citing crawlcheck.io affected?
No. Only paying, booking and handing over personal details were stopped. Reading, citing and connecting got their normal answers throughout.
What do agents get for crawlcheck.io now?
The same answer as every site: a person approves before any payment goes ahead. CrawlCheck never approves a payment on its own.
Which changes make an agent treat a site as possibly taken over?
Changes to where money, logins and mail go, such as a new payment provider, checkout host, email provider, sign-in server or listed agent tool, until the owner confirms them.
Related findings
Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed.
Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.