io.github.teamsincetoday/recipe-commerce-mcp
NPM · RECIPE-COMMERCE-MCP
Extract shoppable ingredients from recipe content with affiliate signals.
Available components
Last scanned (8 hours ago)
Scores higher than 55% of npm servers
Category E-commerce
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 51 of 130 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 214 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 637 tokens (~212/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −3
- Stability: pass → 0.83 functional
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/recipe-commerce-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Deprecated | 1 |
| Stale | 50 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
extract_recipe_ingredients ~223
Extract structured recipe data from transcript text or YouTube URL: recipe name, ingredients with quantity and unit, equipment list, and cooking technique tags. YouTube URL transcription requires yt-dlp installed on the server — if not available the call fails; pass raw transcript text for reliable extraction in all environments. Returns ingredient list ready for match_ingredients_to_products and suggest_affiliate_products. Call this first — both downstream tools reuse its cache. Use for recipe monetization, shoppable recipe creation, and cooking content commerce. Example: recipe_id='chocolate-chip-cookies-v1', transcript='2 cups flour...' → returns {ingredients:[{name:'flour',quantity:'2',unit:'cups',category:'pantry'},...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional API key for paid access beyond the free tier |
| recipe_id | string | – | Optional recipe identifier for caching. Auto-derived from content if omitted. |
| transcript | string | yes | Raw transcript text OR a YouTube URL (e.g. https://youtube.com/watch?v=...) |
No output schema declared.
No examples provided.
match_ingredients_to_products ~221
Match recipe ingredients to purchasable products on Amazon and specialty retailers. Returns affiliate program details (Amazon Associates, ShareASale, Awin), estimated price range, estimated commission rate (2–10%), and substitution alternatives. Commission rates are benchmark estimates — not live affiliate platform data. Use this tool for ingredient-level product details and substitutions; use suggest_affiliate_products for a revenue-ranked shopping list instead. Accepts ingredient list directly or recipe_id from a prior extract_recipe_ingredients call. Use for recipe affiliate monetization and shoppable recipe generation. Example: recipe_id='chocolate-chip-cookies-v1' → returns [{name:'flour',product:'King Arthur All-Purpose Flour',program:'Amazon Associates',estimated_commission_pct:4}].
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional API key for paid access beyond the free tier |
| ingredients | array | – | Ingredient list from extract_recipe_ingredients. Provide this OR recipe_id. |
| recipe_id | string | – | Recipe ID from a prior extraction — loads ingredients from cache. |
No output schema declared.
No examples provided.
suggest_affiliate_products ~193
Generate a revenue-ranked affiliate shopping list for a recipe, sorted by estimated commission potential. Equipment ranks highest (Amazon Associates ~10% commission). Returns items sorted by affiliate score with estimated price range and commission per item. Revenue estimates are algorithmic benchmarks — not live pricing data. Use this tool for ranked shopping lists and blog monetization strategy; use match_ingredients_to_products for ingredient-level product SKUs and substitutions. Accepts ingredient list or recipe_id from extract_recipe_ingredients. Example: recipe_name='Beef Bourguignon'.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Optional API key for paid access beyond the free tier |
| ingredients | array | – | Ingredient list. Provide this OR recipe_id. |
| recipe_id | string | – | Recipe ID from a prior extraction — loads from cache. |
| recipe_name | string | yes | Recipe name (e.g. 'Beef Bourguignon', 'Chocolate Chip Cookies') |
No output schema declared.
No examples provided.
How do I install the io.github.teamsincetoday/recipe-commerce-mcp server?
io.github.teamsincetoday/recipe-commerce-mcp runs locally as an npm package, launched with npx -y recipe-commerce-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · recipe-commerce-mcp
claude mcp add teamsincetoday-recipe-commerce-mcp -- npx -y recipe-commerce-mcp
What is the io.github.teamsincetoday/recipe-commerce-mcp server?
io.github.teamsincetoday/recipe-commerce-mcp is listed in the public MCP registry as io.github.teamsincetoday/recipe-commerce-mcp. Extract shoppable ingredients from recipe content with affiliate signals. This page covers its npm package (recipe-commerce-mcp).
Is the io.github.teamsincetoday/recipe-commerce-mcp server safe to use?
io.github.teamsincetoday/recipe-commerce-mcp scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.teamsincetoday/recipe-commerce-mcp server expose?
io.github.teamsincetoday/recipe-commerce-mcp exposes 3 tools: extract_recipe_ingredients, match_ingredients_to_products, suggest_affiliate_products. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Is the io.github.teamsincetoday/recipe-commerce-mcp server still maintained?
io.github.teamsincetoday/recipe-commerce-mcp 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 io.github.teamsincetoday/recipe-commerce-mcp server under?
io.github.teamsincetoday/recipe-commerce-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.teamsincetoday/recipe-commerce-mcp server?
VerifyMCP ran 16 checks on io.github.teamsincetoday/recipe-commerce-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.