Ask your AI tool about your own site.

What MCP is, if you have not met it

A shared way for an AI assistant to talk to a service that is not itself. Your assistant already knows how to hold a conversation; what it does not have is your data. MCP is the socket that hands it over, and because it is a standard rather than something we invented, one address works in every tool that speaks it.

You connect it once. From then on the assistant can read your audits when you ask, in whatever tool you were already using.

Things worth asking it

You do not have to think of the question. Each of these comes written out in full on your account page, ready to copy, and appears in the slash-command menu of any tool that lists prompts.

• Start here

  You have just connected your AI tool and want to know what it can see.

• What should I fix first?

  You have an audit and a limited amount of time.

• Did my fixes actually work?

  You changed things after an audit and ran a new one.

• Prove that finding

  A finding looks wrong and you want to check it before acting.

• Can AI assistants see me at all?

  You want to know whether ChatGPT or Claude can describe your business.

• Which of my sites is in the worst shape?

  You look after more than one site.

• Write the brief for whoever fixes it

  Somebody else does the work: a developer, an agency, a freelancer.

• The monthly check-inStarts an audit

  Once a month, to catch things that slipped without you noticing.

What it can do

Five tools, not fifty. Each one answers something the report already answers, in a shape an assistant can act on.

• list_auditsRead only

  List the SEO audits on this account, newest first, with the site, the date, the status and the score. Use this first to find the audit you want, then read it with get_audit.

• get_auditRead only

  Read one audit in full: the score for each segment, and every check that did not pass with the exact fix for it. Takes a site address such as example.com, or an audit id from list_audits. Defaults to the most recent audit of that site.

• compare_auditsRead only

  Compare the two most recent audits of a site and say exactly what changed: which checks now pass, which now fail, which were asked for the first time, and which stopped applying. Use this to answer whether a fix worked.

• get_audit_evidenceRead only

  The request log behind an audit: every address we asked the site for, what it answered, and how long it took. Use this to check a claim rather than trusting it.

• run_auditStarts an audit

  Start a new SEO audit of a website. This is the only tool here that changes anything: it costs money, takes a few minutes, and the report is not ready when this returns. Ask the person before calling it. Use list_audits afterwards to see when it has finished.

What it will not do

No tool here returns a traffic or ranking forecast, because no such number can be derived from what a page sends, and the report has never carried one. An assistant asked for one will say so rather than invent it.

Only one tool changes anything, and it is the one that starts an audit. Nothing here can edit your site, delete an audit, or share one on your behalf.

A key reads one account: the one that made it. There is no tool that takes an account as an argument, because there is no way to name somebody else’s. Keys are revocable, and revoking one takes effect on the next request.