Bot Appétit
REMOTE · BOTAPPETIT.AI
Can a machine consume this page? AEO, SEO and performance scans. Page scans need no account.
Available components
Last scanned (15 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1988 tokens (~142/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +2
- DNSSEC: fail → pass ▲ security
- 3 Nov 26 0
- Tool “site_scan_status” rewrote its description, which is the text the model reads security
- Tool “start_site_scan” rewrote its description, which is the text the model reads security
- Schema quality: 128 → 142 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://botappetit.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=botappetit.ai | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7bafd55c3ef97a3a133b574a467ed40d |
| SANs: botappetit.ai, *.botappetit.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of botappetit.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| botappetit.ai. | DS published | 2371 | 13 | Verified |
| botappetit.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://botappetit.ai/mcp | Verified | 200 | |
| http (plaintext) | http://botappetit.ai/mcp | HTTPS enforced | 301 | https://botappetit.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_check Explain a check ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A check id from list_checks or from a report, such as "llms-txt". |
No output schema declared.
No examples provided.
get_report Get a stored report ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The scan id: the last part of a report link on botappetit.ai/r/<id>, or `scan_id` from scan_page. |
No output schema declared.
No examples provided.
leaderboard The leaderboard ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category id such as "software" or "news". Leave out for the top sites of every category. |
| limit | integer | – | How many sites to return per category (default 10 for one category, 5 for all). |
No output schema declared.
No examples provided.
list_checks List the checks ~86
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?
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only checks in this category id, such as "aeo". Leave out for all of them. |
No output schema declared.
No examples provided.
list_sites List the person's sites ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
page_history Get a page’s history ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The exact page, such as https://example.com/pricing. `/a` and `/a/` are different pages. |
No output schema declared.
No examples provided.
request_site_scan Ask for a whole-site scan ~130
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 instead, which is free and needs no account.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | – | The site the person wants scanned, if you know it. It is used only to word the steps. |
No output schema declared.
No examples provided.
scan_page Scan a page ~173
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 and say it came from Bot Appétit by Milk Moon Studio.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | 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. |
| url | string | yes | The page to check, such as https://example.com/pricing. A bare domain works. |
No output schema declared.
No examples provided.
set_pins Pin or unpin pages ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | The site, as list_sites gives it. |
| pin | array | – | Page addresses to pin. They must be on the site (or its www/apex twin). |
| unpin | array | – | Page addresses to stop pinning. |
No output schema declared.
No examples provided.
set_rescan_settings Set monthly re-scans ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| boolean | – | Email the person the result of each monthly re-scan. Leave out to keep the current setting. | |
| rescan | boolean | – | Re-scan this account's sites automatically each month. Leave out to keep the current setting. |
No output schema declared.
No examples provided.
share_site_scan Share a site scan ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | "create" makes an unlisted link anyone holding it can open; "stop" turns it off so the link stops working. |
| job_id | string | yes | The site scan to share or stop sharing. |
No output schema declared.
No examples provided.
site_history Read one site over time ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | The site, as list_sites gives it: for example www.example.com. An address is accepted too. |
No output schema declared.
No examples provided.
site_scan_status Read a site scan ~200
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 and nine in ten finish within about 5 and a half minutes; a site of ten pages or fewer usually finishes in under half a minute. Do not poll: the first answer asks for one check after 30 seconds, and if the scan is still running the next answer says how long to wait. Read check_again_after_seconds in the answer and wait that long before the next check.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id start_site_scan returned, or one from list_sites or site_history. |
No output schema declared.
No examples provided.
start_site_scan Start a whole-site scan ~229
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 within about 5 and a half minutes; a site of ten pages or fewer usually finishes in under half a minute. Do not poll: the first answer asks for one check after 30 seconds, and if the scan is still running the next answer says how long to wait. Read check_again_after_seconds in the answer and wait that long before the next check. The result is private to their account until they choose to share it. For one page, use scan_page, which needs no account.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
How do I install the Bot Appétit MCP server?
Bot Appétit is a hosted endpoint at https://botappetit.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · botappetit.ai
claude mcp add --transport http ai-botappetit-bot-appetit 'https://botappetit.ai/mcp'
What is the Bot Appétit MCP server?
Bot Appétit is an MCP server listed in the public MCP registry as ai.botappetit/bot-appetit. Can a machine consume this page? AEO, SEO and performance scans. Page scans need no account. This page covers its hosted endpoint (https://botappetit.ai/mcp).
Is the Bot Appétit MCP server safe to use?
Bot Appétit scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Bot Appétit MCP server expose?
Bot Appétit exposes 14 tools: scan_page, get_report, page_history, list_checks, explain_check, and 9 more. Their descriptions and schemas cost roughly 1,788 tokens of context every time the server is loaded.
Does the Bot Appétit MCP server require authentication?
No. We connected to Bot Appétit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bot Appétit MCP server still maintained?
Bot Appétit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Bot Appétit MCP server?
VerifyMCP ran 12 checks on Bot Appétit, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Bot Appétit: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.