Bot Appétit MCP server
ai.botappetit/bot-appetitbotappetit.aistreamable-httpv1.0.1Scanned
Can a machine consume this page? AEO, SEO and performance scans. Page scans need no account.
14 tools: 3 can delete or cancel things, 4 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 3
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Bot Appétit MCP server can do
The Bot Appétit MCP server is published by botappetit.ai, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (3 tools: set_pins, set_rescan_settings and share_site_scan) and create or change data (4 tools: scan_page, request_site_scan, leaderboard and start_site_scan). 7 tools only read.
4 tools bring in text other people can write (scan_page, page_history, start_site_scan and 1 more); 3 tools can send data out of your system (scan_page, page_history and request_site_scan).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 3Claude Code: deny
set_pinsPin or unpin pages on one of the signed-in person's sites.No findings
Why it is in this group
- The name "set_pins" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Pin or unpin pages
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
set_rescan_settingsTurn the signed-in person's monthly re-scans of their sites on or off, and the email of each result on or off.No findings
Why it is in this group
- The name "set_rescan_settings" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Set monthly re-scans
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
Changes things 4Claude Code: ask
leaderboardThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: The leaderboard
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
request_site_scanA 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.Can send data out1 finding
Why it is in this group
- The name "request_site_scan" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "request_site_scan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "request_site_scan" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Ask for a whole-site scan
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
scan_pageCheck one web page for AEO, SEO and performance: can a machine consume it?Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- title: Scan a page
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
start_site_scanStart 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.Reads text others writeNo findings
Why it is in this group
- The name "start_site_scan" says "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Start a whole-site scan
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 7Show 7 read-only tools
explain_checkExplain one Bot Appétit check: what it looks at, why it matters for machines reading a page, and what good looks like.No findings
Why it is in this group
- The name "explain_check" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain a check
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_reportGet a stored Bot Appétit report by scan id, the same report a person sees at botappetit.ai/r/<id>.No findings
Why it is in this group
- The name "get_report" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a stored report
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_checksList every check Bot Appétit runs on a page, grouped by category, with the id of each.No findings
Why it is in this group
- The name "list_checks" says "list": a word for reading.
Description, as the server wrote it 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?
Annotations the server declares
- title: List the checks
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_sitesList 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.No findings
Why it is in this group
- The name "list_sites" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List the person's sites
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
page_historyList 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.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a page’s history
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
site_historyRead 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 updat…No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read one site over time
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
site_scan_statusRead 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…No findings
Why it is in this group
- The name "site_scan_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a site scan
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://botappetit.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://clerk.botappetit.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (3 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://botappetit.ai/mcp: tools/list returned 14 tools to an anonymous client, including set_pins (destructive), set_rescan_settings (destructive), share_site_scan (destructive), scan_page (write), request_site_scan (write) and 2 more
Posture changes
- Nov 10, 2026
- Dynamic client registration: no to yes
Findings
Matches of fixed checks, with the text they matched.
The server marks "request_site_scan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "request_site_scan" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 added, 7 changed.+7 added~7 changedView diff
- Added:list_sitesOnly reads
- Added:set_pinsDeletes or cancels
- Added:set_rescan_settingsDeletes or cancels
- Added:share_site_scanDeletes or cancels
- Added:site_historyOnly reads
- Added:site_scan_statusOnly reads
- Added:start_site_scanChanges things
- Changed:explain_checkOnly readsannotations
- Changed:get_reportOnly readsannotations
- Changed:leaderboardChanges thingsannotations
- Changed:list_checksOnly readsannotations
- Changed:page_historyOnly readsannotations
- Changed:request_site_scanChanges thingsdescriptionannotations
- Changed:scan_pageChanges thingsdescriptionannotations
PostureRemote posture changed. Dynamic client registration: no -> yes.View diff
- Dynamic client registration: no to yes
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http bot-appetit https://botappetit.ai/mcpclaude mcp add --transport http bot-appetit https://botappetit.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bot-appetit__get_report",
"mcp__bot-appetit__list_checks",
"mcp__bot-appetit__explain_check",
"mcp__bot-appetit__site_scan_status",
"mcp__bot-appetit__list_sites",
"mcp__bot-appetit__site_history"
],
"ask": [
"mcp__bot-appetit__scan_page",
"mcp__bot-appetit__page_history",
"mcp__bot-appetit__request_site_scan",
"mcp__bot-appetit__leaderboard",
"mcp__bot-appetit__start_site_scan"
],
"deny": [
"mcp__bot-appetit__set_pins",
"mcp__bot-appetit__set_rescan_settings",
"mcp__bot-appetit__share_site_scan"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bot-appetit. Review it before you use it.
Capability tags behind 5 rules
- mcp__bot-appetit__scan_page untrusted-input, outbound
- mcp__bot-appetit__page_history untrusted-input, outbound
- mcp__bot-appetit__request_site_scan outbound
- mcp__bot-appetit__start_site_scan untrusted-input
- mcp__bot-appetit__share_site_scan untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.botappetit/bot-appetit/verify?hash=be1e89872333531c479a2af30cbfe6bdf229eea89d5cb9a88480be4b907388f3" | jq -e '.changed == false'Pinned hash be1e89872333, from Nov 16, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.botappetit/bot-appetit/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.botappetit/bot-appetit)Source: MCP Registry. Synced Nov 2, 2026, 18:17 UTC.
Bot Appétit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Bot Appétit MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Bot Appétit MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: set_pins, set_rescan_settings and share_site_scan.
Can the Bot Appétit MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Bot Appétit MCP server have?
- 14 tools: 3 destructive, 4 write, 7 read. set_pins, set_rescan_settings, share_site_scan, scan_page, request_site_scan, leaderboard, start_site_scan, get_report and 6 more.
Does the Bot Appétit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Bot Appétit MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_page, page_history and request_site_scan.
Has the Bot Appétit MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.