# recipebooq (remote · recipebooq.com)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- remote · `recipebooq.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-recipebooq-recipebooq/api-mcp.md), [page](https://verifymcp.io/servers/com-recipebooq-recipebooq/api-mcp)

## Channel facts

- Endpoint: `https://recipebooq.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1689 tokens (~120/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the recipebooq MCP server?

recipebooq is a hosted endpoint at https://recipebooq.com/api/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-recipebooq-recipebooq": {
      "url": "https://recipebooq.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-recipebooq-recipebooq": {
      "type": "http",
      "url": "https://recipebooq.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-recipebooq-recipebooq]
url = "https://recipebooq.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-recipebooq-recipebooq": {
      "type": "remote",
      "url": "https://recipebooq.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-recipebooq-recipebooq --url 'https://recipebooq.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-recipebooq-recipebooq:
    url: "https://recipebooq.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-recipebooq-recipebooq": {
      "Transport": "http",
      "Url": "https://recipebooq.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-recipebooq-recipebooq -t streamable-http -u 'https://recipebooq.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-recipebooq-recipebooq": {
      "type": "http",
      "url": "https://recipebooq.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 80, 0)

- [security] Tool “emit_app” rewrote its description, which is the text the model reads
- [security] Tool “emit_screen” rewrote its description, which is the text the model reads
- [security] Tool “verify_app” rewrote its description, which is the text the model reads
- [cosmetic] “verify_app” added an optional parameter “toolchain”
- [cosmetic] “add_screen” reworded the description of “compositionId”
- [cosmetic] “install_component” reworded the description of “slug”

### 2026-09-22 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 76, +6)

- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “add_screen” rewrote its description, which is the text the model reads
- [security] Tool “check_snippet” rewrote its description, which is the text the model reads
- [security] Tool “emit_app” rewrote its description, which is the text the model reads
- [security] Tool “emit_screen” rewrote its description, which is the text the model reads
- [security] Tool “find_component” rewrote its description, which is the text the model reads
- [security] Tool “get_component” rewrote its description, which is the text the model reads
- [security] Tool “get_provider_tree” rewrote its description, which is the text the model reads
- [security] Tool “get_rules” rewrote its description, which is the text the model reads
- [security] Tool “get_step” rewrote its description, which is the text the model reads
- [security] Tool “get_theme_tokens” rewrote its description, which is the text the model reads
- [security] Tool “install_component” rewrote its description, which is the text the model reads
- [security] Tool “list_components” rewrote its description, which is the text the model reads
- [security] Tool “update_components” rewrote its description, which is the text the model reads
- [security] Tool “verify_app” rewrote its description, which is the text the model reads
- [functional] Server version: 0.1.0 → 0.2.0
- [cosmetic] Tool “add_screen” changed its title: Add a screen to an exported app
- [cosmetic] Tool “check_snippet” changed its title: Check a snippet for blank-render bugs
- [cosmetic] Tool “emit_app” changed its title: Emit an app
- [cosmetic] Tool “emit_screen” changed its title: Emit a single screen
- [cosmetic] Tool “find_component” changed its title: Find a component for a UI need
- [cosmetic] Tool “get_component” changed its title: Get a component
- [cosmetic] Tool “get_provider_tree” changed its title: Get the provider tree
- [cosmetic] Tool “get_rules” changed its title: Get runtime rules
- [cosmetic] Tool “get_step” changed its title: Expand a recipe step
- [cosmetic] Tool “get_theme_tokens” changed its title: Get theme tokens
- [cosmetic] Tool “install_component” changed its title: Install a component
- [cosmetic] Tool “list_components” changed its title: List components
- [cosmetic] Tool “update_components” changed its title: Update exported components
- [cosmetic] Tool “verify_app” changed its title: Verify an emitted app

### 2026-09-14 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (14)

### `list_components` (~67 tokens)

List components

Lists the shipped @recipebooq/ui components: slug, purpose, category, and which render the real iOS system control versus our own component. Cheap, and a good first call. Optional filters: category and tech.

Input parameters:

- `category` (string)
- `tech` (string)

### `get_component` (~76 tokens)

Get a component

Everything needed to write a correct call site for one component: props with types, defaults and value domains, platform applicability, dependencies, and the runtime rules that apply to it. The rules matter as much as the props: correct props that break a rule still render a blank screen.

Input parameters:

- `slug` (string, required): e.g. "button"

### `find_component` (~69 tokens)

Find a component for a UI need

Takes a UI need in plain language and returns ranked components, including an explicit answer when this catalog deliberately does not ship something and the OS's own control is the right choice. Useful before building a UI control by hand.

Input parameters:

- `need` (string, required): e.g. "a progress bar for an upload"

### `get_rules` (~71 tokens)

Get runtime rules

The runtime rules for this catalog: the mistakes that make native Liquid Glass render blank with no warning, no error and no red box. Pass a slug to scope them to one component. Relevant before writing animation or layout code around a glass component.

Input parameters:

- `slug` (string): optional — omit for catalog-wide rules

### `get_provider_tree` (~62 tokens)

Get the provider tree

The exact app-root provider nesting these components require, in the order that works. Getting it wrong fails at runtime, not at compile time. Pass the components in use to see which providers each one needs.

Input parameters:

- `components` (array): optional slugs in use

### `get_theme_tokens` (~41 tokens)

Get theme tokens

The theme system: which hooks to call, and the spacing, radius and typography scales. Token names rather than hex values are what let a retheme propagate.

### `check_snippet` (~75 tokens)

Check a snippet for blank-render bugs

Takes TSX that uses these components and returns the glass-safety problems in it: animated opacity, the flex:1 collapse, the clipped lens, the conditional mount. Read-only, it never touches the repo. A heuristic text scan, not a structural guarantee.

Input parameters:

- `code` (string, required): the TSX snippet to check

### `emit_app` (~157 tokens)

Emit an app

PAID. Turns a recipebooq canvas into a working Expo app: navigation, providers, tab bar, screens and the components they need. Returns a recipe to apply to the current project: the exact files with target paths, the dependency install line, and ordered steps. Files marked `skeleton` or `component` are hand-written and device-verified, and verify_app reports any that were changed. Needs the share code from the App Builder's "Send app to agent" button.

Input parameters:

- `appId` (string, required): the share code, e.g. "34ca4babb2"
- `override` (boolean): emit even when screens are flagged as not ready. Ask the customer first; the flags exist for a reason.

### `add_screen` (~195 tokens)

Add a screen to an exported app

PAID. Adds one new screen to an app that was already exported: the screen file, the route that mounts it, the exact line to register it, and how to navigate to it. Reads the .recipebooq/files.json manifest to work out the route tree and never reads or rewrites existing source, so the one edit to an existing file comes back as a line to add rather than a file to overwrite.

Input parameters:

- `componentName` (string): React component name, e.g. "InvoiceDetail". Defaults to GeneratedScreen.
- `compositionId` (string, required): share code for the new screen, from the App Builder
- `manifest` (object, required): the parsed .recipebooq/files.json from the project root
- `tab` (string): nest it in this tab's stack so the tab bar stays visible. Omit to put it at the root, where it covers the tab bar (right for a modal).

### `update_components` (~134 tokens)

Update exported components

PAID. Reports what has changed in the recipebooq-supplied files since export and returns only what moved. Reads the .recipebooq/files.json the export wrote into the project, so no share code is needed and it works months later. Never touches the customer's own screens, and flags the rare change that needs a code edit rather than a re-copy. This is how the components and app shell we supplied stay current as iOS and Android move.

Input parameters:

- `manifest` (object, required): the parsed contents of .recipebooq/files.json from the project root (the whole object, or just its `files` array)

### `verify_app` (~221 tokens)

Verify an emitted app

PAID. Checks that an emitted app was applied correctly, before it is built. Takes what was written (file paths with byte sizes, package.json dependencies, project config, build toolchain) and returns what is missing, which copy-verbatim files were altered, which packages are absent, whether the config merge expo-router needs was done, and whether the installed Xcode can build this project at all. Catches the ways a long recipe goes wrong, each of which fails silently or points somewhere else.

Input parameters:

- `appId` (string, required): the share code you passed to emit_app
- `config` (object)
- `dependencies` (array): the keys of package.json's dependencies
- `files` (array, required): what you actually wrote: { path, bytes } per file, path relative to the project root. `bytes` must be the file's size in BYTES on disk (what `wc -c` reports), not its character count — the two differ…
- `toolchain` (object)

### `get_step` (~117 tokens)

Expand a recipe step

FREE. Expands one step of an emit_app recipe: the full instruction, why it matters, how to know it worked, and what to do when it did not. emit_app returns steps in short form to stay inside the response budget, so this carries the detail for any step that needs it. Needs the same share code and the step's id.

Input parameters:

- `appId` (string, required): the share code you passed to emit_app
- `stepId` (string, required): the step id, e.g. "configure" or "write"

### `emit_screen` (~127 tokens)

Emit a single screen

PAID. Turns one composed screen into a TSX file for an app that already exists, with its own navigator and routes. Returns the complete file inline, the components to install first, and how to mount it. For a whole app with navigation and a tab bar, emit_app is the matching tool. Needs the share code from the App Builder.

Input parameters:

- `componentName` (string): React component name for the file, e.g. "CheckoutScreen". Defaults to GeneratedScreen.
- `compositionId` (string, required): the share code, e.g. "34ca4babb2"

### `install_component` (~121 tokens)

Install a component

PAID. Adds one component to an existing project. Returns the transitive registry closure in dependency-first install order, the single `expo install` line for the whole closure, every file with its exact target path, the provider nesting it needs, and its runtime rules. It replaces fetching /r/*.json by hand: a component is a closure, not a file, and the ways to get that wrong all fail silently. Foundation components need no licence key.

Input parameters:

- `slug` (string, required): the component slug, e.g. "button" or "bottom-sheet"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-recipebooq-recipebooq/api-mcp#diagnostics

## Score history

- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 70
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64

## Common questions

### What is the recipebooq MCP server?

recipebooq is an MCP server listed in the public MCP registry as com.recipebooq/recipebooq. Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android. This page covers its hosted endpoint (https://recipebooq.com/api/mcp).

### Is the recipebooq MCP server safe to use?

recipebooq scores 80 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 recipebooq MCP server expose?

recipebooq exposes 14 tools: list_components, get_component, find_component, get_rules, get_provider_tree, and 9 more. Their descriptions and schemas cost roughly 1,533 tokens of context every time the server is loaded.

### Does the recipebooq MCP server require authentication?

No. We connected to recipebooq without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the recipebooq MCP server still maintained?

recipebooq is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://recipebooq.com/api/mcp
- Website: https://recipebooq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-recipebooq-recipebooq/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-recipebooq-recipebooq/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-recipebooq-recipebooq/api-mcp