RMCP.DEV
← Registry

Content Tools

world.food

Provides tools to search, retrieve, and explore recipes, their revision history, traditional sides, and similar cross-country dishes from world.food.

1 endpoint15 known toolsFirst detected October 6, 2026Last detected October 6, 2026

ENDPOINT 1

https://world.food/api/mcp

No auth detected

MCP server metadata

Name
world-food
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

world.food is a collaborative recipe platform ("Wikipedia for food"). Search and read recipes freely. To create, edit, or fork recipes you need a world.food account token sent as an "Authorization: Bearer <token>" header (get one from POST /api/auth/token). Every write is a public, attributed revision — search before creating, prefer forks over duplicates, and write clear edit summaries. Full API docs: https://world.food/api/docs

Known tools 15

search_recipes

Search recipes on world.food by text query, country, tags, or difficulty.

Inferred read-only
get_recipe

Get a full recipe (metadata + content) by country slug and dish slug, e.g.

Inferred read-only
get_recipe_history

Get the public revision history of a recipe (Wikipedia-style).

Inferred read-only
get_recipe_sides

Get stored traditional accompaniments and linked side recipes, or mains that name this side.

Inferred read-only
get_similar_recipes

Get precomputed, cross-country dishes similar to a recipe.

Inferred read-only
list_ingredient_recipes

All published recipes with exact ingredient membership, sorted by views then quality score (NULL score is zero).

Inferred read-only
get_ingredient_graph

One hop of the ingredient graph around a canonical ingredient key (folded English singular, e.g.

Inferred read-only
list_recipe_variants

Published user variants of a recipe — deltas (ingredient/step changes, tips) that readers layered on the original or on one of its regional variations, composed on the recipe page with ?variant=u/<slug>.

Inferred read-only
create_recipe_variant

Publish YOUR version of an existing recipe as a delta on its page — the same dish with a few changes — instead of a copy.

Potential side effects
check_duplicate

Advisory duplicate check before creation.

Inferred read-only
create_recipe

Create a new recipe.

Potential side effects
attach_video_source

Attach a social video as an "as seen on" source to an existing recipe.

Inferred read-only
update_recipe

Edit a recipe — creates a new public revision attributed to your account.

Potential side effects
import_from_video

Extract a structured recipe DRAFT from a social cooking video URL (YouTube/Shorts work best; TikTok/Facebook are best-effort; Instagram is not supported).

Inferred read-only
fork_recipe

Fork a recipe into your own variation ("variation": same dish, your twist) or a new dish inspired by it ("new-dish").

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.world-food]
url = "https://world.food/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "world-food": {
      "type": "http",
      "url": "https://world.food/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: world-food
Remote MCP URL: https://world.food/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "world-food": {
      "url": "https://world.food/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "world-food": {
      "type": "http",
      "url": "https://world.food/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "world-food",
  "transport": "streamable-http",
  "url": "https://world.food/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.