Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Bot Appétit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Can a machine consume this page? AEO, SEO and performance scans. Page scans need no account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bot-appetit-mcp https://botappetit.ai/mcp
# 2 — ask your agent for something these tools do
# scan_page, get_report, page_history and 11 more
Bot Appétit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BOAll 1 server
botappetit1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bot-appetit-mcp https://botappetit.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Check one web page for AEO, SEO and performance: can a machine consume it? Returns the findings by check and the report link. If the exact page was scanned in the last 24 hours the stored result is returned at no cost; set fresh to scan again. A page that blocks our scanner is returned as blocked with no score, because it cannot pass. Free, no account needed. Always give the person the report link
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page to check, such as https://example.com/pricing. A bare domain works. |
| fresh | boolean | no | Set true to always run a new scan instead of returning a stored result under 24 hours old. A new scan uses the stricter new-scan rate limit. |
Get a stored Bot Appétit report by scan id, the same report a person sees at botappetit.ai/r/<id>. Costs nothing and does not scan. Use it to re-read a report you were given a link to. A page that blocked our scanner is returned as blocked, with no score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The scan id: the last part of a report link on botappetit.ai/r/<id>, or scan_id from scan_page. |
List every stored Bot Appétit scan of one exact page, newest first, with the score at the time and how it moved since the scan before. Costs nothing and does not scan. Use it to show whether a page has improved. Blocked and failed scans are listed without a score.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The exact page, such as https://example.com/pricing. /a and /a/ are different pages. |
List every check Bot Appétit runs on a page, grouped by category, with the id of each. Use the id with explain_check for what a check means and what good looks like. Every check asks one question: can a machine consume this page?
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Only checks in this category id, such as "aeo". Leave out for all of them. |
Explain one Bot Appétit check: what it looks at, why it matters for machines reading a page, and what good looks like. Use the id from list_checks or a report. Costs nothing and does not scan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A check id from list_checks or from a report, such as "llms-txt". |
A whole-site scan reads a representative sample of a site and needs a person with a Bot Appétit account, and an agent never creates one. This returns exactly what the person must do, in order: connect this agent to their account (a one-time approval in their browser), after which start_site_scan, site_scan_status, list_sites and the other account tools work. For a single page, use scan_page instea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | The site the person wants scanned, if you know it. It is used only to word the steps. |
The highest-scoring sites by category, from the latest Bot Appétit scan of each site's homepage: rank, host, score out of 100, grade and a link to the full report. Call it with no category to see the top of every category, or with a category id for that board. Only sites that were scored on the current rules are ranked; a site that blocked our scanner is never ranked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | A category id such as "software" or "news". Leave out for the top sites of every category. |
| limit | integer | no | How many sites to return per category (default 10 for one category, 5 for all). |
Start a whole-site scan for the signed-in person's account: Bot Appétit reads a representative sample of the site (not every page) and scores it. Needs the person to have authorised this connection. It returns a job_id straight away and the scan runs in the background, so read it with site_scan_status. A full scan of a large site usually takes about 2 and a half minutes and nine in ten finish with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | The site to scan: a domain such as example.com, a sitemap URL, or a list of pages on ONE site, one per line. |
Read one of the signed-in person's site scans: whether it is still running, and once it has finished the score, the checks that failed, the category scores and the pages it covered, each page with a link to its own full report. Only the account that ran the scan can read it. A scan that is still running is normal, not an error. A full scan of a large site usually takes about 2 and a half minutes a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The job_id start_site_scan returned, or one from list_sites or site_history. |
List the sites the signed-in person follows in Bot Appétit, newest activity first, each with its latest site-scan score, the change since the scan before, and the trend. Use a host from here with site_history, set_pins and the other site tools.
No parameter schema on file.
Read one of the signed-in person's sites over time: every site scan of it newest first with the score and the change since the previous scored scan (a change across a scoring update or different pinned pages is marked, not passed off as the site's own), the pinned pages, and the monthly re-scan settings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host | string | yes | The site, as list_sites gives it: for example www.example.com. An address is accepted too. |
Pin or unpin pages on one of the signed-in person's sites. Pinned pages are scanned in every site scan of that site and count toward its score; up to 25, on the site itself. Give pin and/or unpin lists. Returns each address's outcome and the pins now in place; they apply from the next scan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| host | string | yes | The site, as list_sites gives it. |
| pin | array | no | Page addresses to pin. They must be on the site (or its www/apex twin). |
| unpin | array | no | Page addresses to stop pinning. |
Turn the signed-in person's monthly re-scans of their sites on or off, and the email of each result on or off. Leave a field out to keep it as it is; call with no fields to read the current settings. The settings belong to the account, not to one site.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rescan | boolean | no | Re-scan this account's sites automatically each month. Leave out to keep the current setting. |
| boolean | no | Email the person the result of each monthly re-scan. Leave out to keep the current setting. |
Create or stop the unlisted share link for one of the signed-in person's site scans. Site scans are private by default; a link lets anyone who holds it read that one scan (not the person's other scans) and stays valid until stopped. Only create a link when the person has asked to share the scan, and tell them who can open it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The site scan to share or stop sharing. |
| action | string | yes | "create" makes an unlisted link anyone holding it can open; "stop" turns it off so the link stops working. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bot Appétit or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 3 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestbc9e93a63068d7ea0f02ac966c429f8b2dea558f18e6c3a840f68401f315c22f
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| scan_page | no tags | |
| get_report | no tags | |
| page_history | no tags | |
| list_checks | no tags | |
| explain_check | no tags | |
| request_site_scan | no tags | |
| leaderboard | no tags | |
| start_site_scan | no tags | |
| site_scan_status | no tags | |
| list_sites | no tags | |
| site_history | no tags | |
| set_pins | no tags | |
| set_rescan_settings | no tags | |
| share_site_scan | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbc9e93a63068d7ea
Scanned2026-11-03
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Bot Appétit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.