QAmcp

Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.

Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions

NewYour score can change any day. QAmcp Monitor keeps testing your server and emails you when it breaks. Free for 1 server.See what Monitor does →

Directory / ChefBear

ChefBear

Q: Is ChefBear MCP server safe?

QAmcp's test on 6 Nov 2026: None of the hidden-instruction wordings we know were found in its 12 tool descriptions. Its error messages showed no secrets or internal details. 7 of its 12 tools are labeled read-only; the others may change or send things. Overall it scored 84/100 on 6 Nov 2026. A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

by chef-bear.com · https://chef-bear.com/api/menu-sharing/mcp

Save, find, read and share your ChefBear restaurant menus and pick dishes that suit your tastes.

12 tools✓ no account neededPricing: not listed

Visit website

84 /100

PASS · WITH NOTES

Partial: 9 of 11 checks · 6 Nov 2026

Test it now for current results

At a glance

Runs where: On their server. What you send to it goes to them.
What you need: Nothing: it answered without a login
Tools: 12 tools
Its own safety labels: 7 read-only, 3 labeled as deleting or destroying, 2 labeled as changing things
Memory it takes: About 4,700 tokens of your AI's memory, just for its tool descriptions

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 6 Nov 2026.

Is ChefBear MCP server safe?

None of the hidden-instruction wordings we know were found in its 12 tool descriptions.
Its error messages showed no secrets or internal details.
7 of its 12 tools are labeled read-only; the others may change or send things.
Overall it scored 84/100 on 6 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

Its source code and packages.
What a tool quietly does behind the scenes, such as writing a file or calling another service.
Instructions hidden inside live tool answers. We only look for those in tool descriptions.
Hidden instructions worded in a way our list doesn't know yet.
Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.

What it can do

12 tools, in the server's own words.

import_menu

Use this when the user wants a restaurant menu saved to their ChefBear account from photos they provide: to keep it, get it as a structured menu in their langu…

get_import_statusread-only

Use this after import_menu to see whether the menu is ready.

get_menuread-only

Use this when the user wants help with one of their saved ChefBear menus: what to order, what a dish on it is, prices, or dishes that fit their tastes, budget …

share_menu

Use this only when the user explicitly asks to share one of their ChefBear menus or wants a link other people can open.

revoke_menu_share

Use this when the user asks to stop sharing a menu or to turn off its public link.

connection_statusread-only

Use this once right after ChefBear is connected, or when the user asks whether ChefBear is connected or what it may do.

list_menusread-only

Use this when the user refers to a menu they saved or scanned in ChefBear without giving its link or menuId (for example "the menu I scanned last night" or "my…

get_shared_menuread-only

Use this when the user gives a ChefBear share link (https://chef-bear.com/m/…), whether someone sent it to them or they just created it, and wants to know what…

save_menu

Use this when the user asks to save a restaurant menu to their ChefBear account and you can already read its dishes, for example from a menu photo or text in t…

get_taste_profileread-only

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 a…

update_taste_profile

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"…

recommend_dishesread-only

Use this when the user asks what to order from one of their saved ChefBear menus and their tastes, dislikes, allergies or diets matter.

Test results

Safe mode: only tools labeled read-only were run. How the test works

!
Ready for the newest MCP version
1 warning
- !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
note
!
Every tool is described
1 warning
- !import_menu: Inputs with no description: files
note
✓
ConnectsConnected in 663 ms
pass
✓
Lists its toolsFound 12 tools
pass
✓
Tools are labeled safe or dangerousEvery tool has a safety label
pass
✓
No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
pass
✓
Fast enough
All good
- ✓Connecting took 663 ms
- ✓Listing tools took 62 ms
pass
✓
No secrets leakedChecked 16 error messages: no secrets or internal details
pass
✓
Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
pass
–
Tools work with good inputs
Not tested
- –get_import_status: Needs you to sign in, so it was not tested (not counted against the server)
- –get_menu: Needs you to sign in, so it was not tested (not counted against the server)
- –connection_status: Needs you to sign in, so it was not tested (not counted against the server)
- –list_menus: Needs you to sign in, so it was not tested (not counted against the server)
- –get_shared_menu: Needs you to sign in, so it was not tested (not counted against the server)
- –get_taste_profile: Needs you to sign in, so it was not tested (not counted against the server)
- –recommend_dishes: Needs you to sign in, so it was not tested (not counted against the server)
- –import_menu: Not run: labeled as changing data
- and 4 more
not tested
–
Bad inputs give a clean error
Not tested
- –get_import_status: Needs you to sign in, so bad inputs were not tested
- –get_menu: Needs you to sign in, so bad inputs were not tested
- –list_menus: Needs you to sign in, so bad inputs were not tested
- –get_shared_menu: Needs you to sign in, so bad inputs were not tested
- –recommend_dishes: Needs you to sign in, so bad inputs were not tested
not tested
–
Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)
not tested

Test it yourself

Free and open source. Same checks, same score.

npx qamcp-cli https://chef-bear.com/api/menu-sharing/mcp

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

[![QAmcp score](https://qamcp.dev/s/com-chef-bear-chefbear.svg)](https://qamcp.dev/s/com-chef-bear-chefbear.html)

Score over time

6 Nov 202684

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use ChefBear, signed in with GitHub, one per person. Reviews never change the score.

Is this your server? Get an alert the moment it breaks.

QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.

Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works