recipebooq

by recipebooq.com · remote · no sign-in to list tools · v0.2.0 · published by com.recipebooq

Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.

Changes · 8

Compare Registry entry

11 tools: 8 change things and 3 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone0Claude Code: ask
Changes things8Claude Code: ask: see these tools
Only reads3Claude Code: allow: see these tools

4 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http recipebooq https://recipebooq.com/api/mcp

Findings

Matches of fixed checks, with the text they matched.

4 warn

Warncheck_snippet
The server marks "check_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
What this check looks for
Warnadd_screen
The server marks "add_screen" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "add_screen" says "add": a word for a change.
What this check looks for
Warninstall_component
The server marks "install_component" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "install_component" says "install": a word for a change.
What this check looks for
Warnupdate_components
The server marks "update_components" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "update_components" says "update": a word for a change.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Changes things 8Creates or changes something that can be changed back.Claude Code: ask

add_screenNeeds a subscription.1 finding
Why it is in this group
- The name "add_screen" says "add": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "add_screen" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "add_screen" says "add": a word for a change.
  What this check looks for
Description, as the server wrote it
Needs a subscription. Adds one screen designed in the Designer to a project. With the project's .opointo/files.json it returns the screen file, the route that mounts it and the one line to register it, and never rewrites existing files. Without it, a self-contained screen file for any Expo app.
Annotations the server declares
- title: Add a screen to an app
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_snippetScans TSX that uses these components for the mistakes that render nothing with no error: animated opacity on glass, the flex: 1 collapse, a clipped lens, a conditionally mounted su…1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "check_snippet" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
  What this check looks for
Description, as the server wrote it
Scans TSX that uses these components for the mistakes that render nothing with no error: animated opacity on glass, the flex: 1 collapse, a clipped lens, a conditionally mounted surface. A read-only text scan, not a guarantee; verify_app checks a whole emitted project.
Annotations the server declares
- title: Check code for blank-render bugs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
emit_appNeeds a subscription.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
Needs a subscription. Turns a design from the Designer into a working Expo app: navigation, providers, tab bar, screens and the components they use. Returns a recipe for the current project: every file with its target path, one install line and ordered steps with a check each. Pass `step` for one step in full, which does not count against the daily allowance.
Annotations the server declares
- title: Build an app from a design
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
install_componentNeeds a subscription, except for the free foundation components.1 finding
Why it is in this group
- The name "install_component" says "install": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "install_component" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "install_component" says "install": a word for a change.
  What this check looks for
Description, as the server wrote it
Needs a subscription, except for the free foundation components. Adds one component to an existing project: the files it and its dependencies need in install order with exact target paths, the single expo install line, the providers it needs and its runtime rules. A backend recipe's id, such as "supabase", adds that integration: its files and the per-app wiring an export writes.
Annotations the server declares
- title: Install a component
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
propose_appYour agent can design an app with you: send an app in opointo's design format (the AppSpec emit_app builds from) and get back a link that opens it in the Designer as a new, unsaved…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.
Description, as the server wrote it
Your agent can design an app with you: send an app in opointo's design format (the AppSpec emit_app builds from) and get back a link that opens it in the Designer as a new, unsaved design. The person sees every screen, changes what they like, and hands it back for emit_app. into: the code in the person's line; it lands in their open design. dryRun checks without making a link; format: true returns the format and every block, "photos" the sample photos, or with app: { version: 1 } a short plan's.
Annotations the server declares
- title: Propose an app design
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_screenYour agent can design a single screen with you: send one screen in opointo's design format (the Composition add_screen builds from) and get back a link that opens it in the Designe…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.
Description, as the server wrote it
Your agent can design a single screen with you: send one screen in opointo's design format (the Composition add_screen builds from) and get back a link that opens it in the Designer as a new, unsaved design the person can change. into: as propose_app's. dryRun checks without making a link; format: true returns the format. For a whole app, use propose_app.
Annotations the server declares
- title: Propose a screen design
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
update_componentsNeeds a subscription.1 finding
Why it is in this group
- The name "update_components" says "update": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "update_components" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "update_components" says "update": a word for a change.
  What this check looks for
Description, as the server wrote it
Needs a subscription. Reads the project's .opointo/files.json and returns only the opointo-supplied files that changed since export, so it works months later with no share code. Never touches the customer's own screens, and flags the rare change that needs a code edit rather than a copy.
Annotations the server declares
- title: Update supplied components
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_appNeeds a subscription.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
Needs a subscription. Checks an emitted app before it is built: missing files, altered verbatim files, absent packages, the expo-router config merge, whether the installed Xcode can build it, and whether a change needs a new native build.
Annotations the server declares
- title: Verify an emitted app
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Only reads 3Looks things up and changes nothing.Claude Code: allow

find_componentFinds the component for a UI need described in plain words, ranked, and says when this catalog ships nothing on purpose because the phone's own control is the right choice.No findings
Why it is in this group
- The name "find_component" says "find": a word for reading.
Description, as the server wrote it
Finds the component for a UI need described in plain words, ranked, and says when this catalog ships nothing on purpose because the phone's own control is the right choice. Omit `need` to list every component with its purpose and whether it renders the real system control.
Annotations the server declares
- title: Find a component
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_app_setupHow an app is set up so these components work and follow its theme, one topic at a time: the app-root providers in the order that works, the theme hooks and token scales, or the ru…No findings
Why it is in this group
- The name "get_app_setup" says "get": a word for reading.
Description, as the server wrote it
How an app is set up so these components work and follow its theme, one topic at a time: the app-root providers in the order that works, the theme hooks and token scales, or the rules that hold across the whole catalog. An app built by emit_app already has all three wired.
Annotations the server declares
- title: Get the app setup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_componentEverything needed to write a correct call site for one component: props with types, defaults and allowed values, what draws on iOS and on Android, the providers it needs at the app…No findings
Why it is in this group
- The name "get_component" says "get": a word for reading.
Description, as the server wrote it
Everything needed to write a correct call site for one component: props with types, defaults and allowed values, what draws on iOS and on Android, the providers it needs at the app root, its dependencies, and the runtime rules that stop it rendering blank.
Annotations the server declares
- title: Get a component
- 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.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http recipebooq https://recipebooq.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__recipebooq__find_component",
      "mcp__recipebooq__get_component",
      "mcp__recipebooq__get_app_setup"
    ],
    "ask": [
      "mcp__recipebooq__check_snippet",
      "mcp__recipebooq__emit_app",
      "mcp__recipebooq__add_screen",
      "mcp__recipebooq__install_component",
      "mcp__recipebooq__update_components",
      "mcp__recipebooq__verify_app",
      "mcp__recipebooq__propose_app",
      "mcp__recipebooq__propose_screen"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as recipebooq. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.recipebooq/recipebooq/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

8 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry. Synced Oct 21, 2026, 18:01 UTC.

For agents: Markdown · JSON · report this listing