ChefBear MCP server
com.chef-bear/chefbearchef-bear.comstreamable-httpv1.4.1Scanned
Save, find, read and share your ChefBear restaurant menus and pick dishes that suit your tastes.
12 tools: 3 can delete or cancel things, 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
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 ChefBear MCP server can do
The ChefBear MCP server is published by chef-bear.com, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (3 tools: share_menu, revoke_menu_share and update_taste_profile) and create or change data (3 tools: import_menu, save_menu and recommend_dishes). 6 tools only read.
3 tools bring in text other people can write (import_menu, share_menu and get_shared_menu).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.4.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.
12 tools
Deletes or cancels 3Claude Code: deny
update_taste_profileUse this when the user asks you to remember, change or forget something about their own food tastes in ChefBear (for example "remember I'm allergic to peanuts", "add that I don't e…No findings
Why it is in this group
- The name "update_taste_profile" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Use this when the user asks you to remember, change or forget something about their own food tastes in ChefBear (for example "remember I'm allergic to peanuts", "add that I don't eat cilantro" or "I'm vegetarian now, update it"), when they say yes after you offered to save a food taste they mentioned in this conversation, or when they confirm which dish they picked or turned down from one of their saved ChefBear menus. Adds or removes likes, dislikes, allergies and diets, sets or clears taste levels from 1 to 5, and records picks and rejections by menuId and the dish's id from get_menu. Record only what the user said about themselves in this conversation, and only what they asked for or agreed to: never guess an allergy, diet or preference, and don't record a choice they didn't confirm. Repeating the same requestId with the same changes applies them once. Returns the updated profile. Needs the "Update your taste profile" permission.
Annotations the server declares
- title: Update your taste profile
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
recommend_dishesUse this when the user asks what to order from one of their saved ChefBear menus and their tastes, dislikes, allergies or diets matter.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 Use this when the user asks what to order from one of their saved ChefBear menus and their tastes, dislikes, allergies or diets matter. Ranks the menu's dishes against the user's saved taste profile (when this connection may read it) plus any preferences you pass from the conversation, and lists dishes whose printed text mentions a stated allergy or dislike as excluded, with the reason. It matches the menu's text only and does not decide diets, so check the picks against the user's diets and suggest confirming allergens and ingredients with the restaurant. Read-only; does not use the recognition allowance.
Annotations the server declares
- title: Recommend dishes from a menu
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
connection_statusUse this once right after ChefBear is connected, or when the user asks whether ChefBear is connected or what it may do.No findings
Why it is in this group
- The name "connection_status" says "status": a word for reading.
Description, as the server wrote it Use this once right after ChefBear is connected, or when the user asks whether ChefBear is connected or what it may do. Returns only this connection's own permissions (scopes) and app name, with no account or menu data. For an account that has not used the ChefBear app yet, it also says how many menu recognitions are left today and where to get the app.
Annotations the server declares
- title: Check the connection
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_import_statusUse this after import_menu to see whether the menu is ready.No findings
Why it is in this group
- The name "get_import_status" says "get": a word for reading.
Description, as the server wrote it Use this after import_menu to see whether the menu is ready. Returns pending, ready (with the menuId and a private ChefBear link to the menu) or failed with a reason; while the import is still running it waits up to about 10 seconds for it to finish before answering. Check at most twice in a row; if it is still pending, tell the user and check again on their next message. Read-only; does not use the recognition allowance.
Annotations the server declares
- title: Check menu import
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_taste_profileUse this when the user asks what ChefBear knows about their food tastes, or when choosing dishes for them would go better with the likes, dislikes, allergies and diets they saved i…No findings
Why it is in this group
- The name "get_taste_profile" says "get": a word for reading.
Description, as the server wrote it Use this when the user asks what ChefBear knows about their food tastes, or when choosing dishes for them would go better with the likes, dislikes, allergies and diets they saved in ChefBear. Returns the user's saved taste profile: likes, dislikes, allergies, diets, taste levels from 1 to 5 (spicy, oily, sweet, meat, adventure), their food personality from the ChefBear quiz, and dishes they recently picked or turned down from their saved menus. Read-only. The entries are the user's own statements, not medical facts, so still suggest confirming allergens and ingredients with the restaurant. Needs the "See your taste profile" permission, which is granted separately from menu access; without it, ask the user about their tastes instead.
Annotations the server declares
- title: Read your taste profile
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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 21, 2026, 19:21 UTC, unchanged since Nov 7, 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
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://chef-bear.com/.well-known/oauth-protected-resource/api/menu-sharing/mcp
- Authorization servers
- https://chef-bear.com
- 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 6 tools that change things (3 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://chef-bear.com/api/menu-sharing/mcp: tools/list returned 12 tools to an anonymous client, including share_menu (destructive), revoke_menu_share (destructive), update_taste_profile (destructive), import_menu (write), save_menu (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:connection_statusOnly readsdescription
- Changed:get_menuOnly readsdescription
- Changed:import_menuChanges thingsinputSchema
- Changed:update_taste_profileDeletes or cancelsdescription
Install
Pinned to version 1.4.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http chefbear https://chef-bear.com/api/menu-sharing/mcpclaude mcp add --transport http chefbear https://chef-bear.com/api/menu-sharing/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__chefbear__get_import_status",
"mcp__chefbear__get_menu",
"mcp__chefbear__connection_status",
"mcp__chefbear__list_menus",
"mcp__chefbear__get_shared_menu",
"mcp__chefbear__get_taste_profile"
],
"ask": [
"mcp__chefbear__import_menu",
"mcp__chefbear__save_menu",
"mcp__chefbear__recommend_dishes"
],
"deny": [
"mcp__chefbear__share_menu",
"mcp__chefbear__revoke_menu_share",
"mcp__chefbear__update_taste_profile"
]
}
}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 chefbear. Review it before you use it.
Capability tags behind 3 rules
- mcp__chefbear__import_menu untrusted-input
- mcp__chefbear__share_menu untrusted-input
- mcp__chefbear__get_shared_menu 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/com.chef-bear/chefbear/verify?hash=17200751aec778f9e5729d319b56a567dfa77f20d84b93be2af171ace5fe038f" | jq -e '.changed == false'Pinned hash 17200751aec7, from Nov 20, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.chef-bear/chefbear/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.chef-bear/chefbear)Source: MCP Registry. Synced Nov 6, 2026, 18:17 UTC.
ChefBear MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ChefBear MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ChefBear MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: share_menu, revoke_menu_share and update_taste_profile.
Can the ChefBear 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 ChefBear MCP server have?
- 12 tools: 3 destructive, 3 write, 6 read. share_menu, revoke_menu_share, update_taste_profile, import_menu, save_menu, recommend_dishes, get_import_status, get_menu and 4 more.
Does the ChefBear MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ChefBear MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ChefBear MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.