Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Spoonacular

NPM · @PIPEWORX/MCP-SPOONACULAR · 2 COMPONENTS

Spoonacular MCP.

+3 this week 80 Trust /100

Last scanned (9 hours ago)

Scores higher than 65% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-spoonacular). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1209 tokens (~67/item across 18 items; 18 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Package version: 0.2.0 → 0.2.1 functional
  • 4 Nov 26 +3
    • Stability: unverified → 0.20 ▲ functional
  • 3 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 77

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-spoonacular@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-spoonacular
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-spoonacular/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692357400
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c4785a98a48e605fbbea52c8d51b5dd7b02ab3c8289030e71734cd7cf83aecfada3e964b3d976c759170c65e065fe534db8aae1bddf12648f8201567c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~1,156 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
convert_amount ~92

Convert a cooking measurement amount for a specific ingredient between units using Spoonacular. Requires `ingredientName`, `sourceAmount`, `sourceUnit`, and `targetUnit`. Returns the converted amount and unit (e.g. 1 cup flour → 125 grams).

NameTypeReqDescription
ingredientNamestringyes–
sourceAmountnumberyes–
sourceUnitstringyes–
targetUnitstringyes–

No output schema declared.

No examples provided.

ingredient_information ~73

Fetch details for a Spoonacular ingredient by numeric `id`. Returns name, category, possible units, and nutrition data for the given `amount` and `unit`. Use `ingredient_search` to get the id first.

NameTypeReqDescription
amountnumber––
idnumberyes–
unitstring––

No output schema declared.

No examples provided.

ingredient_search ~40

Ingredient search.

NameTypeReqDescription
intolerancesstring––
numbernumber––
querystringyes–
sortstring––

No output schema declared.

No examples provided.

meal_plan_generate ~100

Generate a Spoonacular meal plan for a given `timeFrame` ("day" or "week") matching `targetCalories`, `diet` (e.g. vegetarian/vegan/paleo), and comma-separated `exclude` ingredients. Returns meals with recipe ids, titles, images, and nutrition summary.

NameTypeReqDescription
dietstring––
excludestring––
targetCaloriesnumber––
timeFramestring––

No output schema declared.

No examples provided.

meal_plan_week ~74

Generate a Spoonacular 7-day meal plan matching `targetCalories`, `diet`, and comma-separated `exclude` ingredients. Returns meals per day with recipe ids, titles, images, and per-day nutrition totals.

NameTypeReqDescription
dietstring––
excludestring––
targetCaloriesnumber––

No output schema declared.

No examples provided.

product_information ~46

Fetch details for a branded grocery product by Spoonacular numeric `id`. Returns product title, UPC, brand, ingredients, nutrition facts, and image URL.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

product_search ~50

Branded product search.

NameTypeReqDescription
maxCaloriesnumber––
minCaloriesnumber––
numbernumber––
offsetnumber––
querystringyes–

No output schema declared.

No examples provided.

recipe_information ~68

Fetch full details for a Spoonacular recipe by numeric `id`. Returns title, ingredients, instructions, cuisines, diets, ready time, servings, source URL, and optionally full nutrition data if `includeNutrition` is true.

NameTypeReqDescription
idnumberyes–
includeNutritionboolean––

No output schema declared.

No examples provided.

recipe_ingredients ~49

Fetch the ingredient list for a Spoonacular recipe by `id`. Returns each ingredient's name, amount, unit, image URL, and estimated cost in US cents.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

recipe_nutrition ~54

Fetch the full nutrition breakdown for a Spoonacular recipe by `id`. Returns calories, macros (protein/fat/carbs), and detailed per-nutrient values including percent daily values.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

recipe_price_breakdown ~48

Fetch the estimated ingredient cost breakdown for a Spoonacular recipe by `id`. Returns per-ingredient price in US cents and the total estimated cost per serving.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

recipe_random ~66

Fetch one or more random Spoonacular recipes, optionally filtered by comma-separated `tags` (e.g. "vegetarian,dessert") and `number` of results. Returns full recipe details including ingredients and instructions.

NameTypeReqDescription
numbernumber––
tagsstring––

No output schema declared.

No examples provided.

recipe_search ~57

Search Spoonacular recipes with complex filters passed as query params (query keyword, cuisine, diet, intolerances, includeIngredients, excludeIngredients, maxReadyTime, sort, etc.). Returns recipe id, title, image, and ready-in minutes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recipe_similar ~56

Fetch Spoonacular recipes similar to a given recipe by `id`. Returns up to `number` similar recipes with title, image URL, ready time, and servings.

NameTypeReqDescription
idnumberyes–
numbernumber––

No output schema declared.

No examples provided.

recipe_summary ~49

Fetch a short human-readable summary paragraph for a Spoonacular recipe by `id`. Returns the recipe title and a 1-2 sentence description of ingredients and preparation style.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

recipe_taste ~70

Fetch taste profile scores for a Spoonacular recipe by `id`. Returns numeric scores for sweetness, saltiness, sourness, bitterness, savoriness, fattiness, and spiciness. Optionally normalize scores 0–100.

NameTypeReqDescription
idnumberyes–
normalizeboolean––

No output schema declared.

No examples provided.

wine_pairing ~73

Fetch wine pairing suggestions for a `food` dish or ingredient (e.g. "salmon", "pasta primavera") with optional `maxPrice` filter. Returns paired wine types and specific product recommendations with name, price, and description.

NameTypeReqDescription
foodstringyes–
maxPricenumber––

No output schema declared.

No examples provided.

wine_recommendation ~91

Fetch specific wine product recommendations for a wine type name (e.g. "merlot", "chardonnay") with optional `minRating`, `price` target, and `number` of results. Returns product name, price, average rating, and description.

NameTypeReqDescription
minRatingnumber––
numbernumber––
pricestring––
winestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Spoonacular MCP server?

Spoonacular runs locally as an npm package, launched with npx -y @pipeworx/mcp-spoonacular. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-spoonacular

# add to Claude Code
claude mcp add pipeworx-io-spoonacular -- npx -y @pipeworx/mcp-spoonacular
Common questions

What is the Spoonacular MCP server?

Spoonacular is an MCP server listed in the public MCP registry as io.github.pipeworx-io/spoonacular. Spoonacular MCP. This page covers its npm package (@pipeworx/mcp-spoonacular).

Is the Spoonacular MCP server safe to use?

Spoonacular scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Spoonacular MCP server expose?

Spoonacular exposes 18 tools: recipe_search, recipe_information, recipe_random, recipe_summary, recipe_similar, and 13 more. Their descriptions and schemas cost roughly 1,156 tokens of context every time the server is loaded.

Is the Spoonacular MCP server still maintained?

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

What licence is the Spoonacular MCP server under?

Spoonacular declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.